You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for reaching out. This is an unfortunate quirk of the streamwrapper customization and it doesn't look like there's a great way for us to override this.
We've documented our reasoning behind making streams opened in r unseekable by default and outline the steps needed to make a stream opened in r mode seekable.
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
When using a S3 stream wrapper and opening a file, without setting seekable, so it is unseekable, the stream meta data says it is seekable.
Expected Behavior
Stream metadata should say not seekable
Current Behavior
Stream metadata says it is seekable when it is not
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
SDK version used
3.279.1
Environment details (Version of PHP (
php -v
)? OS name and version, etc.)PHP 8.0.30 (cli) (built: Aug 3 2023 17:13:08) ( NTS ) / MacBook Apple Sillicon M1
The text was updated successfully, but these errors were encountered: