-
Notifications
You must be signed in to change notification settings - Fork 939
Treat ABORTED writes as retryable #1456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I was wondering if we needed similar handling for transaction writes, but it looks like we retry them regardless of the error code 🤔... so not an issue, I guess.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still LGTM.
I looked at the transaction code too. While our current handling seems specious there I think addressing that is out of scope for this change. I've addressed the test failure by adding |
This is a port of firebase/firebase-js-sdk#1456.
* Treat ABORTED writes as retryable This is a port of firebase/firebase-js-sdk#1456. * Regenerate spec test json
This corresponds to a server-side change that will be released for the v1 protocol only (see b/119437764). This is a port of firebase/firebase-js-sdk#1456.
This corresponds to a server-side change that will be released for the v1 protocol only (see b/119437764). This is a port of firebase/firebase-js-sdk#1456.
This corresponds to a server-side change that will be released for the v1 protocol only.