-
Notifications
You must be signed in to change notification settings - Fork 215
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
return sql.ErrNotFound if account doesn't exist #6508
base: develop
Are you sure you want to change the base?
Conversation
Previously, it returned an empty account. Now the error handling decision is left for the caller.
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## develop #6508 +/- ##
=======================================
Coverage 79.9% 79.9%
=======================================
Files 353 353
Lines 46517 46534 +17
=======================================
+ Hits 37211 37225 +14
- Misses 7199 7208 +9
+ Partials 2107 2101 -6 ☔ View full report in Codecov by Sentry. |
bors merge |
## Motivation The decision how to handle a situation when the queried account doesn't exist should be left to the caller - it's not the responsibility of the code accessing the cache/database.
Build failed: |
Bors merge |
## Motivation The decision how to handle a situation when the queried account doesn't exist should be left to the caller - it's not the responsibility of the code accessing the cache/database.
Build failed: |
bors merge |
## Motivation The decision how to handle a situation when the queried account doesn't exist should be left to the caller - it's not the responsibility of the code accessing the cache/database.
Build failed: |
bors merge |
## Motivation The decision how to handle a situation when the queried account doesn't exist should be left to the caller - it's not the responsibility of the code accessing the cache/database.
Build failed: |
bors merge |
## Motivation The decision how to handle a situation when the queried account doesn't exist should be left to the caller - it's not the responsibility of the code accessing the cache/database.
Build failed: |
bors merge |
Already running a review |
bors merge |
## Motivation The decision how to handle a situation when the queried account doesn't exist should be left to the caller - it's not the responsibility of the code accessing the cache/database.
Build failed:
|
bors merge |
## Motivation The decision how to handle a situation when the queried account doesn't exist should be left to the caller - it's not the responsibility of the code accessing the cache/database.
Build failed:
|
bors merge |
## Motivation The decision how to handle a situation when the queried account doesn't exist should be left to the caller - it's not the responsibility of the code accessing the cache/database.
Build failed: |
bors try |
tryBuild failed: |
bors try |
tryBuild failed: |
@poszu I'm just using your PR to check if the new systest is working as expected. |
bors try |
tryBuild succeeded: |
OK, but keep in mind that this change might actually be unsound as the systests failed few times in a way they hadn't fail before |
Motivation
The decision how to handle a situation when the queried account doesn't exist should be left to the caller - it's not the responsibility of the code accessing the cache/database.
Description
Previously, it returned an empty account. Now the error handling decision is left for the caller.
Test Plan
Updated tests