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.
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
TXM In-memory: add address state framework : STEP 2 #12122
TXM In-memory: add address state framework : STEP 2 #12122
Changes from 12 commits
8e329ed
b69865e
36574fa
788d9b7
885cfb7
25186b5
e0d9939
cd5f156
dcb01d9
777d53a
c364858
44854b0
e992b20
751788e
0f91f8c
0f266ef
a3cb0de
4831b0a
6e1e9bc
87b196c
abe7d1b
99cfc64
f470445
b10e97e
c1d40af
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check failure on line 19 in common/txmgr/address_state.go
GitHub Actions / lint
Check failure on line 44 in common/txmgr/address_state.go
GitHub Actions / lint
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.
@prashantkumar1982 @poopoothegorilla does panic make sense here? I doubt we will ever hit this, but if by some miracle we do, wouldn't it be better to just drop the TX, log it, and proceed? Or is this error only possible through some sort of dev error that we want to catch ASAP?
Check failure on line 126 in common/txmgr/address_state.go
GitHub Actions / lint
Check failure on line 131 in common/txmgr/address_state.go
GitHub Actions / lint
Check failure on line 139 in common/txmgr/address_state.go
GitHub Actions / lint
Check failure on line 151 in common/txmgr/address_state.go
GitHub Actions / lint
Check failure on line 164 in common/txmgr/address_state.go
GitHub Actions / lint
Check failure on line 173 in common/txmgr/address_state.go
GitHub Actions / lint
Check failure on line 177 in common/txmgr/address_state.go
GitHub Actions / lint
Check failure on line 181 in common/txmgr/address_state.go
GitHub Actions / lint