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

Improvements to loading state from a TSV #677

Closed
CharlieC3 opened this issue Nov 1, 2024 · 1 comment
Closed

Improvements to loading state from a TSV #677

CharlieC3 opened this issue Nov 1, 2024 · 1 comment

Comments

@CharlieC3
Copy link
Member

Currently if the tsv_file_url property is configured, the chainhook node will attempt to download and restore from this file on reboot, even if there is pre-existing data (e.g. data restored from a volume snapshot).

Ideally the chainhook node would only download and restore from a TSV if its working dir is empty.

@github-project-automation github-project-automation bot moved this to 🆕 New in DevTools Nov 1, 2024
@smcclellan smcclellan moved this from 🆕 New to 📋 Backlog in DevTools Nov 11, 2024
rafaelcr added a commit that referenced this issue Nov 12, 2024
Also, remove the old code that attempted to re-import a TSV every 32
Stacks blocks

Fixes #677
@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✅ Done in DevTools Nov 12, 2024
github-actions bot pushed a commit that referenced this issue Nov 12, 2024
## [1.9.0-stacks-signers.8](v1.9.0-stacks-signers.7...v1.9.0-stacks-signers.8) (2024-11-12)

### Bug Fixes

* only import stacks tsv if chainstate is empty ([#684](#684)) ([1f9f37e](1f9f37e)), closes [#677](#677)
Copy link

🎉 This issue has been resolved in version 1.9.0-stacks-signers.8 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants