Repository navigation
feat(upload): Table of common error codes - #20072
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
The plan checks client errors, MDX runtime 404 logs, and not-found counts for the upload guide. An issue escalates when those 404 logs appear or client errors rise. The plan also checks SDK page load volume. Services: PlanWhat changedThe resumable upload guide now shows a table of common upload error status codes and fixes. The compression section now says byte sizes apply before any form of Content-Encoding. The table omits auth failures and unexpected 500 responses. develop-docs must deploy before this page is live. RiskInvalid MDX can 404 the upload guide when runtime compile runs. A render fault can raise client errors on SDK documentation pages. Wrong error text can send SDK authors to a bad fix. Telemetry cannot see that text. Intended effectThis change only adds and rewords documentation. No metric shows that the new table or the compression sentence is present. absent and confirmed look the same in telemetry. Do not treat a quiet error rate as success. Regression watchA bad table can 404 this page or raise client errors on SDK pages. The upload guide itself had zero page loads in the baseline window. Use the SDK slice and site-wide errors instead.
If error events rise, inspect new titles for MDX or table render faults. Hours with fewer than 15 page loads can push the error share above 7% without a real fault. Not observableExact-path |
|
|
||
| | Status | Error Text | Solution | | ||
| | ----------------------- | ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | ||
| | 400 Bad Request | `Missing X-Decoded-Content-Length header` | Specify the size of the request body before applying `Content-Length`. | |
There was a problem hiding this comment.
What does "before applying Content-Length" mean?
There was a problem hiding this comment.
I think the wording is a bit clumsy but what would be needed is to, add the X-Decoded-Content-Length header with the size before any content encodings are done.
| | 400 Bad Request | `Missing X-Decoded-Content-Length header` | Specify the size of the request body before applying `Content-Length`. | | ||
| | 400 Bad Request | `non-final chunk {chunk_length} is smaller than upload granularity {upload_granularity}` | Use chunks of at least `Upload-Min-Chunk-Size` bytes, in multiples of `Upload-Chunk-Granularity`, except for the final chunk. | | ||
| | 409 Conflict | `upload offset mismatch (server holds {offset} bytes)` | Make a `HEAD` request to obtain the server's current state. | | ||
| | 413 Payload Too Large | `Chunk of {chunk_length} bytes exceeds the remaining {remaining} bytes` | The initial `Upload-Length` was wrong. | |
There was a problem hiding this comment.
nit: The The initial Upload-Length was wrong. under solution reads funky.
|
Verified in
|
This branch was successfully deployed
3 participants
DESCRIBE YOUR PR
Adds a table of errors codes to the upload guide. Common errors (like auth) or unexpected errors (like 500) are omitted.
Closes INGEST-1303
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace
YYYY-MM-DDwith the due date. You can update this information later by editing the PR description.PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: