agent: fix db migration for value_aggregate from 20 to 39 digits #973
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
carlosvdr
changed the title
dwerner
approved these changes
Aug 16, 2024
carlosvdr
force-pushed
the
fix-db-value
branch
from
f8675f6
to
6f0a8ab
Compare
carlosvdr
force-pushed
the
fix-db-value
branch
from
6f0a8ab
to
20543b2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migrations from the indexer-rs side are using the correct value at
scalar_tap_ravs > value_aggregatesince it uses unsigned 128bits numbers (39 digits)We had at first in mind 64 (therefore the 20 digits) but we need to increase this to match indexer-rs
This also happens for the nonce where it is defined as 20 digits so we are specifying it in the migrations
WARNING!!!!!! do not ignore
After running this new migrations its necessary to restart TAP-AGENT
