Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data inconsistency between blockchain and contracts/disputes #285

Open
ashishjur opened this issue Jul 16, 2020 · 0 comments
Open

Data inconsistency between blockchain and contracts/disputes #285

ashishjur opened this issue Jul 16, 2020 · 0 comments
Labels
check Control if the behaviour is as per requirements
Milestone

Comments

@ashishjur
Copy link

Expected Behavior

Data in JBP's contracts/disputes tables should be in sync with blockchain.

Current Behavior

In case the transaction fails, data on DB is different than that of on blockhain.

Possible Solution

Steps to Reproduce

Environment: Dev

Branch release/0.9.4 commit 318593c

  1. Create a contract
  2. Open a dispute
  3. Try to amend dispute. It will show gas estimate 5. Run the transaction. It will fail.
  4. Do step 3 few times. Refresh page.

Now you have data in DB about amendments of dispute proposals but not on blockchain as transactions failed.
This flow serves purpose of reaching data inconsistancy. There could be other such cases mainly due to nature of how tata is propogated in JBP's contracts/disputes tables and blockchain.

PS: Actual bug of gas estimate 5 has been fixed in later commits.

@ashishjur ashishjur added the check Control if the behaviour is as per requirements label Jul 16, 2020
@tyagishuchi1 tyagishuchi1 added this to the Legacy milestone Jul 20, 2020
@tyagishuchi1 tyagishuchi1 modified the milestones: Legacy, Editor, Open Layer Jul 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
check Control if the behaviour is as per requirements
Projects
None yet
Development

No branches or pull requests

2 participants