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.

Sign up for GitHub

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

Jump to bottom

Config option consensus.max_epochs_stored is ignored #3112

Closed
sisou opened this issue Nov 21, 2024 · 0 comments · Fixed by #3111
Closed

Config option consensus.max_epochs_stored is ignored #3112

sisou opened this issue Nov 21, 2024 · 0 comments · Fixed by #3111
Assignees
@paberr
Labels
bug Something isn't working

Comments

@sisou
Copy link
Member

sisou commented Nov 21, 2024

On both history and full nodes, the generated config logged in DEBUG at node startup always shows max_epochs_stored: 1, no matter what is set in the config file.

Maybe other settings have the same issue.
@sisou sisou added the bug Something isn't working label Nov 21, 2024
@sisou sisou changed the title Config option consensus.max_epoch_stored is not taken from config file, is always 1 Config option consensus.max_epochs_stored is not taken from config file, is always 1 Nov 21, 2024
@sisou sisou changed the title Config option consensus.max_epochs_stored is not taken from config file, is always 1 Config option consensus.max_epochs_stored is ignored Nov 21, 2024
@paberr paberr linked a pull request Nov 21, 2024 that will close this issue
Only ever prune beyond max_epochs_stored #3111
Merged
3 tasks
@paberr paberr mentioned this issue Nov 21, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@paberr paberr

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Only ever prune beyond max_epochs_stored nimiq/core-rs-albatross
2 participants
@sisou @paberr