Problemsby Glyph
Amazon S3 users keep filing bugs
3 posts from 3 people3d activeFading, +0 this week
Posts per day
The posts behind it
[Catalogsv2] Spark support for Amazon S3 Tables
## Goal Support Amazon S3 Tables through its Spark/Iceberg catalog integration. ## Required coverage - Identify the supported Spark catalog implementation and required AWS/Iceberg versions. - Keep credentials and session properties outside `catalogs.yml`; map only logical dbt...
CSV scans over mixed S3 buckets fail or have incorrect data
### Checks - [x] I have checked that this issue has not already been reported. - [x] I have confirmed this bug exists on the [latest version](https://pypi.org/project/polars/) of Polars. ### Reproducible example AI was used to build the MRE. ### Log output ### Issue description...
issue: S3 storage: non-ASCII file names of 210-218 bytes upload fine but can never be read (Errno 36)
...and/or related issues (closed ones too). #5192 and #25954 are about the **upload** path failing; this report is about a name range where upload succeeds and every later **read** fails. ### Installation Method Docker ### Open WebUI Version 0.10.2 (also reproduced against `main`...
Companies and products named
About this problem
Evidence
3 posts from 3 people in 3 places, about 1 a week over 24 days. Mostly on open-webui/open-webui, pola-rs/polars, dbt-labs/dbt. Tools named alongside: Docker, MinIO, Polars, PyPI.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about Amazon S3 that state a pain but match no known issue yet. First post Sep 23, 2026, latest Oct 16, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
History