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]: vestingBalancesSummary API is showing old data #11721

Open
JonRay15 opened this issue Sep 30, 2024 · 0 comments
Open

[Bug]: vestingBalancesSummary API is showing old data #11721

JonRay15 opened this issue Sep 30, 2024 · 0 comments
Labels
api bug fe-request A list of reasonably high value API change requests from front end

Comments

@JonRay15
Copy link

Problem encountered

I run this to check my actual accounts and I see I have no vesting balances (which is expected).

query partyAccounts {
  partiesConnection(id:"b62eafc46e6fadc6e45ae51de8bda199f0702131e5b23665f3411223c598acc2"){
    edges{
      node{
        id
        accountsConnection{
          edges{
            node{
              balance
              asset{
                id
                symbol
                decimals
              }
              type
            }
          }
        }
      }
    }
  }
}

However if I run this I see that supposedly I have about 5.8 VEGA still vesting .... and for some reason this hasnt been updated since epoch 982.

query vestingDetails {
  party(id: "b62eafc46e6fadc6e45ae51de8bda199f0702131e5b23665f3411223c598acc2") {
    vestingStats{
      rewardBonusMultiplier
      quantumBalance
      epochSeq
      }
    vestingBalancesSummary{
      epoch
      vestingBalances{
        asset {
          id
          symbol
          quantum
          decimals
        }
        balance
      }
      lockedBalances {
        asset {
          id
          symbol
          quantum
          decimals
        }
        balance
        untilEpoch
      }
    }
  }
}

Observed behaviour

As above

Expected behaviour

The vestingBalancesSummary API should accurately reflect the accounts API.

Steps to reproduce

1. Submit `xyz` transaction
2. With this payload
3. Query `abc` API
4. Observe the error

Software version

0.77.10

Failing test

No response

Jenkins run

No response

Configuration used

No response

Relevant log output

No response

@JonRay15 JonRay15 added bug api fe-request A list of reasonably high value API change requests from front end labels Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api bug fe-request A list of reasonably high value API change requests from front end
Projects
Status: No status
Development

No branches or pull requests

1 participant