Open
Description
Describe the bug
My understanding based on another post is there was a change made for the sake of efficiency, but I'm unable to find the code in the SDK that previously handled converting the stream to a seekable stream. I know it previously did it because a direct call to the endpoint gives back a stream that isn't seekable.
If someone could please point me to how it was done before, I'd very much appreciate it.
Expected behavior
A seekable stream is returned
How to reproduce
Try to seek a stream returned by .content
SDK Version
5.15
Latest version known to work for scenario above?
5.15
Known Workarounds
Copy the stream to a memory stream.
Debug output
Click to expand log
```</details>
### Configuration
_No response_
### Other information
_No response_