Resolving a defect in upscaledb - 19/07/2018 03:47 EDT

While using upscaledb for managing distributed database we have encountered a bug related to deleting the keys, which occurs only when transactions are enabled. The issue is described in details on GitHub: [login to view URL] Our proposed approach of resolving the issue assumes two phases: 1. identification of likely problem area and proposal of cost and a timeframe for resolving the defect (further referred to as the Offer); 2. resolving the defect. We will collect submissions from contractors interested in delivering phase 1 for 5 working days since publishing of the project. Then, we will select up to 3 contractors whom the work within phase 1 will be commissioned. Each of the 3 contractors will be paid 300$ provided that they will submit the valid Offer. In phase one you will be expected to recreate problem based on the test case we have provided, identify likely problem areas, and initial analysis of the bug, as well prepare fix price offer for fixing the bug and addressing the issue for Phase 2. The second step will be payable as proposed in the Offer provided that the defect is resolved successfully. Potentially, we are interested in outsourcing continuous support of upscaledb (ongoing support fee) – details will be discussed after successful delivery of the phase 2.