-
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
[Merged by Bors] - v2alpha1: support ineffectual transaction state #6468
[Merged by Bors] - v2alpha1: support ineffectual transaction state #6468
Conversation
zap.String("tx_id", tx.ID.String()), | ||
zap.Error(err), | ||
) | ||
return nil |
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.
I'm not sure if returning nil
is correct here. The transaction then has no state - instead I think it should be something like unknown/unspecified/error - maybe TransactionState_TRANSACTION_STATE_UNSPECIFIED
?
Co-authored-by: Matthias Fasching <[email protected]>
Co-authored-by: Matthias Fasching <[email protected]>
bors merge |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #6468 +/- ##
=========================================
- Coverage 80.0% 79.9% -0.1%
=========================================
Files 353 353
Lines 46424 46445 +21
=========================================
+ Hits 37154 37155 +1
- Misses 7170 7188 +18
- Partials 2100 2102 +2 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
Build failed: |
bors merge |
Build failed: |
bors merge |
Build failed: |
bors merge |
Build failed: |
bors merge |
Pull request successfully merged into develop. Build succeeded: |
Motivation
#6443 Introduced new transaction state
TRANSACTION_STATE_INEFFECTUAL
which was not supported by v2alpha1.Closes #6466