reverted TxMempool.CheckTx to previous behavior (CON-266)#3386
Merged
Conversation
|
The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #3386 +/- ##
==========================================
+ Coverage 59.08% 59.11% +0.03%
==========================================
Files 2100 2100
Lines 173008 173003 -5
==========================================
+ Hits 102219 102279 +60
+ Misses 61926 61868 -58
+ Partials 8863 8856 -7
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
sei-will
approved these changes
May 5, 2026
wen-coding
approved these changes
May 5, 2026
This file contains hidden or 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
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.
#3334 made TxMempool.CheckTx and Application.CheckTx return an error instead of ResponseCheckTx with an error code. This PR reverts to the previous behavior. Since there is no case in which Application.CheckTx returns unwrapped error, the signature has been tightened to always return ResponseCheckTxV2. Proxy.CheckTxSafe() keeps returning (*ResponseCheckTxV2,error) though, so that in case of panic the stack trace is not send as part of the RPC response.