-
Notifications
You must be signed in to change notification settings - Fork 10
0.11.1-alpha.2 #35
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
Open
zoedberg
wants to merge
43
commits into
RGB-WG:v0.11_fixes
Choose a base branch
from
zoedberg:0.11.1-2
base: v0.11_fixes
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
0.11.1-alpha.2 #35
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
0cee011 to
7f6e0d8
Compare
cf665cb to
a1b8e57
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## v0.11_fixes #35 +/- ##
===============================================
+ Coverage 37.10% 41.09% +3.98%
===============================================
Files 276 255 -21
Lines 41375 37798 -3577
===============================================
+ Hits 15354 15532 +178
+ Misses 26021 22266 -3755
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
b328baf to
5a756dc
Compare
65212ba to
e177198
Compare
Open
Draft
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.
This PR updates the tests to the v0.11 fixes and improvements epic - part 2 (part 1: #30).
The part 2 of the epic includes the following fixes/changes:
1.80.01.81.0 (due toaws-lc-syshalf)check_chain_neton theAnyResolverWitnessOrd::Ignored+ fix select valid witness when usingWitnessOrd::Ignored(make sure to select mined/mempool TXs first)WitnessVoutbeneficiary. This allows a sender to embed the tapret commitment on the receiver output (thus avoiding to construct a bitcoin change output just to put the commitment)BlockHeightto bp-consensus, useNonEmptyVecinTypedAssigns, remove commented code, allow more errors inevolve_state, useNonEmptyOrdSetin Inputs)validate_consignment_resolver_errortestStandardTypes: filter type system for schema, in order to makeKittypes smallerReservedBytes(untested and insufficient to achieve the desired flexibility)This is not yet complete, we'll add more commits in the following days and update the description accordingly.
Involved PRs: