Repository navigation
Conversation
added 2 commits
October 24, 2026 20:31
The 503 body for a request that reached its deadline now says to retry with a new signature. The SQL error text and the route constant stay equal. Details: TC-1997
Details: TC-1997
Contributor
Author
|
APPROVE: see TC-1997 (reviewed exact head 489ede7) |
Contributor
Author
This branch has not been deployed
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
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.
The 503 body for a request that reached its deadline before its write began now reads:
request_timeout: no change was applied; retry the request with a new signatureChanges:
SqlError::RequestTimeoutdisplay text (tinycloud-core) andREQUEST_TIMEOUT_BODY(tinycloud-node-server) carry the new sentence; they stay equal.Details: TC-1997