Repository navigation
fix: carry a request id on every call, and match production's 10 MB ingest limit - #8
Merged
Merged
Conversation
…ngest limit Every request now sends its own x-request-id (a UUID per request). The id reported in errors, and by --verbose, is the body's requestId, else the response's x-request-id header, else the one the CLI sent. So every error carries an id, including a bare 413/502 from a proxy and network failures or timeouts. For those last two, the output says it is the CLI's own id and that the request may still have reached the API. Requests also send User-Agent "databox-cli/<version> (node <v>; <platform>)", so CLI usage and versions are visible in the API's request logs. dataset ingest checked a 30,000,000-byte payload. Production enforces MaxPayloadSizeMb=10 on Content-Length: measured on 2026-09-29, 10,399,982 bytes passed the size check and 10,599,982 got 413 request_too_large. The CLI now refuses anything over 10 MiB (10,485,760 bytes) before sending. Packaging: - npm pkg fix normalises the bin path and repository URL that npm corrected at publish. - npm audit fix (no --force) clears the two high advisories in runtime dependencies. - The version is 1.0.1, with a CHANGELOG entry, and the api-client rules describe the new headers and request-id resolution. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
bwiz
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every request now sends its own x-request-id (a UUID per request). The id reported in errors, and by --verbose, is the body's requestId, else the response's x-request-id header, else the one the CLI sent. So every error carries an id, including a bare 413/502 from a proxy and network failures or timeouts. For those last two, the output says it is the CLI's own id and that the request may still have reached the API.
Requests also send User-Agent
"databox-cli/ (node ; )", so CLI usage and versions are visible in the API's request logs.
dataset ingest checked a 30,000,000-byte payload. Production enforces MaxPayloadSizeMb=10 on Content-Length: measured on 2026-09-29, 10,399,982 bytes passed the size check and 10,599,982 got 413 request_too_large. The CLI now refuses anything over 10 MiB (10,485,760 bytes) before sending.
Packaging: