service · inferred from evidence
S3
AWS Simple Storage Service, a hosted object storage service.
- Prediction interrupted; please retry (code: PA) when passing a file object as input
Calling replicate.run with a local file object failed with a Prediction interrupted error (code PA), while the same model worked from the Replicate website. Maintainer mattt explained the difference: client libraries send files in the reque
- unstructured NLTK download throws `HTTP 403 Forbidden` on the nltk_data tarball
unstructured's `_download_nltk_packages_if_not_present` suddenly started throwing `HTTP 403 Forbidden` when downloading `https://utic-public-cf.s3.amazonaws.com/nltk_data_3.8.2.tar.gz`. It worked until late November 2024. Is the download UR
- MinIO: anonymous PUT to public bucket with AWS SDK Java v2.30 fails with 400 "Missing fields in request"
Running MinIO locally in Docker with a public bucket, an anonymous PUT with the AWS SDK for Java v2 (2.30.x) fails with: software.amazon.awssdk.services.s3.model.S3Exception: Missing fields in request. (Service: S3, Status Code: 400). The t
- Weaviate backup stuck in STARTED state forever
Running a backup on Weaviate 1.25.5 (Helm chart, single instance, S3 backend) left the backup stuck in STARTED state for hours on a tiny dataset (~7k objects), with the status endpoint never advancing. The reporter noted this happened even
- input_images must be a zip file error when running a training with a file handle
Creating a Flux LoRA training failed with `input_images must be a zip file` even though the uploaded file was a valid zip. Maintainer mattt found the cause in how file uploads pass filenames: when you hand the client a file handle, the file
- OpenSearch 3.x snapshot repository fails on S3-compatible storage: "trailing checksum is not supported"
After upgrading to OpenSearch 3.0.0, snapshot repositories on S3-compatible storage (e.g. Outscale) stopped working. The repository-s3 plugin in 3.0.0 upgraded the AWS SDK to 2.30.31, and testing a repository failed with: "Caused by: softwa
- mcp-server-motherduck: cant set a custom S3 endpoint (IBM COS) for the database connection
Using the MotherDuck MCP server against an S3-compatible store (IBM Cloud Object Storage), there was no way to set a custom endpoint through the direct MCP connection. The only thing that worked was creating a secret manually with an ENDPOI
- Supabase Storage S3 API: AWS Go SDK v2 uploads fail with 403 SignatureDoesNotMatch
Using the AWS SDK for Go v2 (aws-sdk-go-v2) against Supabase Storage's S3-compatible endpoint, PutObject fails with: operation error S3: PutObject, https response error StatusCode: 403, api error SignatureDoesNotMatch: The request signature
- Textract rejects local PDFs: `Exception: PDF must be in S3 bucket`
Running `python3 textractor.py --documents document-name.pdf --text --forms --tables` on a local PDF fails with `Exception: PDF must be in S3 bucket`. Can Textract process a document on my local disk, or does it have to be in S3?
- textractor raises `KeyError: 'Geometry'` when an expense field has an empty value
I call `textract.start_expense_analysis` on a multi-page invoice PDF stored in S3. When I access `document.expense_documents`, I get `KeyError: 'Geometry'`. Debugging the textractor package, I found the Geometry part is missing for an `Expe
- aws-lambda-nodejs deploy fails: Uploaded file must be a non-empty zip
Deploying a Lambda with the aws-lambda-nodejs NodejsFunction construct failed with Uploaded file must be a non-empty zip. The dependencies had just been updated, and a nearly identical API and Lambda in the same project deployed fine. The c