Moved from GitHub badger/601
Posted by danielmai:
(This is a renewal of the challenge initiated in #570)
We are always looking to proactively fix issues in our software. If you can prove that Badger loses data under certain conditions and provide a reproducible set of instructions of the data loss, we’ll pay you $1337 as a cash reward for your finding. You find an issue in Badger and get paid, and we get to improve our software. It’s a win-win.
- Badger must be run with
SyncWrites=trueenabled (the default). Badger only promises durability of successful writes.
- A valid data loss bug would use public APIs of Badger and use them in the correct way. Creating unwanted behavior by using internal functions, or using the public APIs in an incorrect way, can still be useful to make Badger more robust, but won’t constitute a valid entry for this challenge.
- The steps must be reproducible by the Dgraph team. If we can’t reproduce them at our end, we won’t consider it a valid entry.
- The setup must be general enough. If it requires a supercomputer or some crazy RAID array to run, we won’t be able to reproduce the issue.
- We try to keep things simple and intend to pay the same amount for valid issues. However, if the bug only causes Badger to not return data, and the data is fully recoverable by an easy fix to the code – that’s technically not a data loss (See #578). For those bugs, we reserve the right to pay less than the above mentioned bounty amount. The amount for these bugs will be decided based an internal team review.
- Challenge participants must adhere to our Code of Conduct. To summarize it briefly, don’t be destructive or inflammatory.
- In cases of disagreement, the Dgraph team will make the final decision.
Submit an entry
If you have a reproducible data loss bug, don’t reply here. File a separate GitHub issue with a link to this issue and we’ll evaluate it.