-
Notifications
You must be signed in to change notification settings - Fork 114
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
fix: allow more than one Rosetta stx_unlock
operation per block
#1712
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov Report
@@ Coverage Diff @@
## master #1712 +/- ##
==========================================
+ Coverage 76.72% 76.77% +0.05%
==========================================
Files 80 80
Lines 11503 11503
Branches 2574 2574
==========================================
+ Hits 8826 8832 +6
+ Misses 2548 2541 -7
- Partials 129 130 +1
|
This seems to have fixed the issue. Testing against our dev env:
|
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.
LGTM, thanks @zone117x
## [7.3.1](v7.3.0...v7.3.1) (2023-09-11) ### Bug Fixes * allow more than one Rosetta `stx_unlock` operation per block ([#1712](#1712)) ([81221c8](81221c8))
🎉 This PR is included in version 7.3.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Only a single
stx_unlock
Rosetta operation is being returned per block, even when multiple unlocks occur in a block.Here are two examples that should include a
stx_unlock
operation for addressSPVEW3RAESA4A4TG5R81A5D06MBMGV3EP0KABEXK
, but do not and only contain a singlestx_unlock
for another address: