feat: load account should return db error #1447
Merged
Conversation
This file contains 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
DaniPopes
reviewed
May 22, 2024
DaniPopes
approved these changes
May 23, 2024
rakita
approved these changes
May 24, 2024
|
failed tests not related |
This was referenced May 24, 2024
Closed
Closed
Closed
Closed
This was referenced May 31, 2024
Closed
Closed
Closed
Closed
This was referenced Jun 17, 2024
Closed
Closed
Merged
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.
Since the db may be a remote db, it could happen a network error under the db error.
And when remote db error happen, the application level maybe need to retry it. So it's better to keep db error original rather than be a custom string.
Or just return another db error with extra error info?