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

[Bug] StackerDB configuration can be changed at any point in a tenure #5650

Open
jcnelson opened this issue Jan 3, 2025 · 1 comment
Open
Assignees
Labels
bug Unwanted or unintended property causing functional harm

Comments

@jcnelson
Copy link
Member

jcnelson commented Jan 3, 2025

When originally designed, StackerDB configurations were not meant to be changed except for at the start of a tenure. This is because the cost of reloading them is borne by the p2p thread and is expensive. Furthermore, the ones for miners and signers don't change very often at all -- no more than once per tenure.

The code, however, does not enforce this. This should get fixed ASAP so that (1) the p2p thread only needs to refresh StackerDB views when the Stacks tenure changes, and (2) before other projects start using StackerDBs in the wild.

@jcnelson jcnelson added the bug Unwanted or unintended property causing functional harm label Jan 3, 2025
@jcnelson jcnelson self-assigned this Jan 3, 2025
@github-project-automation github-project-automation bot moved this to Status: 🆕 New in Stacks Core Eng Jan 3, 2025
@jcnelson jcnelson mentioned this issue Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unwanted or unintended property causing functional harm
Projects
Status: Status: 🆕 New
Development

No branches or pull requests

2 participants
@jcnelson and others