Closed saschagoebel closed 5 years ago
It fails because the deploy_contract
fixture used to deploy the merkle_drop_contract
deploys to a different chain then what you get with --jsonrpc test
.
https://github.com/trustlines-protocol/contract-deploy-tools/blob/master/deploy_tools/cli.py#L26-L30
The way to solve this would be to not use the merkle_drop_contract
fixture and use a merkle drop contract that you deployed with the cli tools to the --jsonrpc test
chain
Ahhh! I remember some talk about this some time ago. Thanks!
Merging #52 into master will increase coverage by
3.1%
. The diff coverage is100%
.
@@ Coverage Diff @@
## master #52 +/- ##
=========================================
+ Coverage 73.3% 76.41% +3.1%
=========================================
Files 6 7 +1
Lines 266 301 +35
=========================================
+ Hits 195 230 +35
Misses 71 71
Impacted Files | Coverage Δ | |
---|---|---|
merkle_drop/cli.py | 95.14% <100%> (+1.72%) |
:arrow_up: |
merkle_drop/status.py | 100% <100%> (ø) |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 07f444f...f3467da. Read the comment docs.
I didn't come up with an additional check that makes sense right now, but the remaining value check is right here: https://github.com/trustlines-protocol/merkle-drop/pull/52/files#diff-d616077eae5c677134893708f5530692R232 - It's just not in the example though :-o
Woops, then my bad, did not see that.
Implementation of #47
Example output: