Fix how masp tx's are identified #2790
Merged
Conversation
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2790 +/- ##
=======================================
Coverage 59.39% 59.40%
=======================================
Files 298 298
Lines 92771 92770 -1
=======================================
+ Hits 55104 55106 +2
+ Misses 37667 37664 -3 ☔ View full report in Codecov by Sentry. |
grarco
previously approved these changes
Mar 3, 2024
Closed
batconjurer
force-pushed
the
bat/fix/issue-2684
branch
from
74b0524 to
f43e333
Compare
brentstone
added a commit
that referenced
this pull request
Apr 17, 2024
* bat/fix/issue-2684: [chore]: Added changelog [fix]: Fix how masp txes are identified
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.
Describe your changes
Resolves issue #2684
Indicate on which release or other PRs this topic is based on
Checklist before merging to
draft