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 user / developer I would like to know a build fails because of something I have changed rather than issues with Travis CI / Docker
### Why Is this Needed?
*Summary*: If you review the recent builds [here](https://travis-ci.org/MARKETProtocol/MARKETProtocol) you can see that there is inconsistent errors occuring
[comment]: # (Feature or Bug? i.e Type: Bug)
### Current Behavior
Intermittent build failure
> The command "docker-compose exec eth-bridge scripts/wait_for_oraclize_connector.sh" exited with 1.
> 121.22s$ docker-compose exec eth-bridge-coverage scripts/wait_for_oraclize_connector.sh
> Oraclize connector did not initialize within 2 minutes. Aborting...
> The command "docker-compose exec eth-bridge-coverage scripts/wait_for_oraclize_connector.sh" exited with 1.
### Expected Behavior
Trigger a build in Travis-CI
[comment]: # (Provide a summary of the solution and a task list on what needs to be fixed.)
*Summary*:Resolve issues with docker and travis ci
### Definition of Done
[comment]: # (Any other information that would be useful, bullets are helpful.)