[hotfix] Clarify moment image upload errors - #6016
Closed
mashbean wants to merge 1 commit into
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
Superseded by another agent's fix. |
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.
Summary
Unknown Error.Too Frequentstate forACTION_LIMIT_EXCEEDED, which can happen during repeated image upload attempts becausedirectImageUploadis rate-limited.directImageUploadDonemutation so future debugging does not only show#<Object>.Verification
npm run i18nnpm run lint:tsnpm run format -- --list-differentgit diff --checkNotes
Follow-up to #6011 and #6013. Production is on the new build, but repeated upload attempts can still surface a generic
Unknown Error; this PR makes that state diagnosable and user-readable.