Skip to content

Classify workspace storage exhaustion as unavailable - #657

Merged
SaladDay merged 2 commits into
mainfrom
classify-workspace-storage-exhaustion
Oct 10, 2026
Merged

SaladDay merged 2 commits into
mainfrom
classify-workspace-storage-exhaustion

Conversation

@SaladDay

@SaladDay SaladDay commented Oct 10, 2026 •

Copy link
Copy Markdown
Collaborator

Files.create can encounter a full disk or quota with valid input. Before publishing a destination file, the Runtime now maps those errors to the existing unavailable result, producing HTTP 503 and settling the exact write as rejected so later writes can proceed. Existing destination conflicts, invalid input and uncertain receipts retain their behavior.

Validation: errno classification red/green tests; focused localworkspace/Runtime tests; real PostgreSQL public API 503, rejected settlement and successor 201; Windows/Darwin cross-compilation; EN/zh documentation checks. Independent complete-diff review found no blocking issues. These tests inject errno/receipts; they do not qualify a production quota backend or exhaust a real filesystem.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@SaladDay
SaladDay merged commit 951b755 into main Oct 10, 2026
22 checks passed
@SaladDay
SaladDay deleted the classify-workspace-storage-exhaustion branch October 10, 2026 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant