Active Stake empty for epoch 231

[CyberCyclone]

I've been using cardano-graqhql and I've noticed that retrieving data for ActiveStake epoch 231 is completely empty. I've compared it against 2 nodes that was NOT affected by this bug: IntersectMBO/cardano-db-sync#398 and I am pulling transactions.

I've checked the actual tables and looking up 230 pulls data, 231 has no records.

I'm currently running cardano-graphql commit 6f20487 which is using cardano-db-sync:6.0.0

[erikd]

I do not know what cardano-graqhql does, but I do know that db-sync currently does not store active state.

@rhyslbw ?

[CyberCyclone]

Awesome, thanks for that. I thought it was a shared feature. To keep things clean I'll recreate it on the cardano-graqhql github and link back here for future reference.

[erikd]

Probably better if I move this ticket to grpahql.

[CyberCyclone]

As mentioned in #376, this is fixed by doing a db and node re-sync, but it doesn't seem to be directly linked to the db-sync 398 bug because db-sync worked fine after the epoch boundary. It's just the extra graphql features that failed at the boundary.

[rhyslbw]

If you are not seeing records in the Hasura Console, then the data isn't in the DB at that point. ActiveStake is simple SQL View that remaps the names of a table and it's columns to the semantics that an 'active stake' record contains the stake registered with a stake key for a given epoch.

I'll try to reproduce this and get back to you.

[rhyslbw]

Will close as it's not reproducible, however feel free to reopen should it occur again