Transaction table is not correctly migrated.

Concordium / concordium-node

The main concordium node implementation.

GNU Affero General Public License v3.0

45 stars 22 forks source link

Transaction table is not correctly migrated. #905

Closed abizjak closed 1 year ago

abizjak commented 1 year ago

Bug Description

2023-06-22T12:07:12.640933363Z: DEBUG: Sent a direct message to peer 00000000000017ea containing a catch-up status message
2023-06-22T12:07:12.711113749Z: DEBUG: Runner: Catch-up status message deserialized.
2023-06-22T12:07:12.712788692Z: WARN: Runner: Released global state lock following error.
concordium-stagenet-node-6.0.0: TreeStateInvariantViolation "The recorded next sequence number for update type UpdateMicroGTUPerEuro (1) doesn't match the one that is going to be finalized (10690)"
�oncordium-stagenet-node-6.0.0: warning: too many hs_exit()s

Versions

Software Version: 6.0.0

abizjak commented 1 year ago

The problem is that when initializing skov V1 from V0 in

migrateSkovFromConsensusV0 regenesis migration gsConfig@GlobalStateConfig{..} oldPbsc oldBlockState bakerCtx handlerCtx unliftSkov = do

we call

mkInitialSkovData

which just construct

emptyTransactionTable