Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
In partnership with Protocol Labs, we’re excited to welcome builders from everywhere to APOLLO, your mission control to engage with the builder…
Gitcoin is GDPR compliant. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
## Before you `start work`
Please read our contribution [guidelines](https://docs.marketprotocol.io/#contributing) and if there is a bounty involved please also see [here](https://docs.marketprotocol.io/#gitcoin-and-bounties)
If you have ongoing work from other bounties with us where funding has not been released, please do not pick up a new issue. We would like to involve as many contributors as possible and parallelize the work flow as much as possible.
Please make sure to comment in the issue here immediately after starting work so we know your plans for implementation and a timeline.
Please also note that in order for work to be accepted, all code must be accompanied by test cases as well.
## User Story
As a developer I would like to be able to easily see any changes in coverage from my commits
### Why Is this Needed?
[comment]: # (Describe the problem and why this task is needed. Provide description of the current state, what you would like to happen, and what actually happen)
*Summary*: After upgrading to newer version of `solidity-coverage` and `solidity` our coverage environment is failing tests that are passing otherwise.
[comment]: # (Feature or Bug? i.e Type: Bug)
### Current Behavior
[comment]: # (Describe what actually happened.)
Coverage environment fails tests that pass in test environment
### Expected Behavior
[comment]: # (Describe what you expected to happen.)
Coverage and tests to line up
[comment]: # (Describe how we can replicate the bug step by step.)
### Definition of Done
[comment]: # (Any other information that would be useful, bullets are helpful.)
- [ ] Revert errors resolved in coverage run
### Additional Information
## failing with coverage network
Running: node --max-old-space-size=4096 ../node_modules/.bin/truffle test --network coverage
19) Orders are signed correctly
> No events were emitted
19) Contract: OrderLib Orders are signed correctly:
Error: VM Exception while processing transaction: revert
at Object.InvalidResponse (/app/node_modules/truffle/build/webpack:/~/web3/lib/web3/errors.js:38:1)
at XMLHttpRequest.request.onreadystatechange (/app/node_modules/truffle/build/webpack:/~/web3/lib/web3/httpprovider.js:128:1)
at XMLHttpRequestEventTarget.dispatchEvent (/app/node_modules/truffle/build/webpack:/~/xhr2/lib/xhr2.js:64:1)
at XMLHttpRequest._setReadyState (/app/node_modules/truffle/build/webpack:/~/xhr2/lib/xhr2.js:354:1)
at XMLHttpRequest._onHttpResponseEnd (/app/node_modules/truffle/build/webpack:/~/xhr2/lib/xhr2.js:509:1)
at IncomingMessage. (/app/node_modules/truffle/build/webpack:/~/xhr2/lib/xhr2.js:469:1)
at endReadableNT (_stream_readable.js:1054:12)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
## Passing in same CI run
docker-compose exec truffle truffle test
✓ Orders are signed correctly (254ms)