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

[Bug]: STATUS not being updated when a duplicate deposit is seen #10915

Closed
gordsport opened this issue Mar 16, 2024 · 0 comments · Fixed by #10918
Closed

[Bug]: STATUS not being updated when a duplicate deposit is seen #10915

gordsport opened this issue Mar 16, 2024 · 0 comments · Fixed by #10918
Assignees
Labels

Comments

@gordsport
Copy link
Contributor

gordsport commented Mar 16, 2024

Problem encountered

A duplicate deposit TX has been noticed and the status of this has remained as OPEN. We also need to check if this issue is alsol possible with staking.

Observed behaviour

https://api1.vega.community/graphql/

query{
  deposits{
    edges{
      node{
        asset{symbol}
        party{id}
        amount
        status
        createdTimestamp,
        txHash
      }
    }
  }
}

"txHash": "0xc2e24585893c352728e9bfea4d4088593a209ddb7c9cc6136648d3e79eefae74"

Additional information

This duplicate deposit has been rejected by Vega and will never finalise and it’s only the status in the API that is showing as open forever until the fix can be deployed in the next release.

Expected behaviour

The duplicated deposit should be marked as REJECTED or something similar

Software version

0.74.10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Status: In Testing
Development

Successfully merging a pull request may close this issue.

3 participants