Clear NEAR DA data on docker compose test env reset #272
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
Hyodar
force-pushed
the
test/clear-near-da-data
branch
from
7276489
to
97c7290
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.
Current Behavior
NEAR DA data was not being cleared on a docker compose test env reset. The usual fix for this would be resetting the volumes whenever resetting -
docker compose down -vor such. Still, this may pass unnoticed and cause some confusion.A related PR is #267.
New Behavior
The above issue is prevented by clearing the relevant data on the
indexer_setupservice. So, when re-upping it should be clean even if the volumes were not reset.Breaking Changes
None