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: canPrune should take a time #9308

Closed
Tracked by #7820
just-mitch opened this issue Oct 21, 2024 · 0 comments · Fixed by #9751
Closed
Tracked by #7820

bug: canPrune should take a time #9308

just-mitch opened this issue Oct 21, 2024 · 0 comments · Fixed by #9751
Assignees
Milestone

Comments

@just-mitch
Copy link
Contributor

just-mitch commented Oct 21, 2024

See the comment here #9193

We need to allow canPrune to accept a time so it can check in the future, not when the last block was published.

@just-mitch just-mitch added this to the Sequencer & Prover Testnet milestone Oct 21, 2024
@just-mitch just-mitch self-assigned this Oct 21, 2024
@just-mitch just-mitch changed the title bug: canPropose should take a time bug: canPrune should take a time Oct 21, 2024
@github-project-automation github-project-automation bot moved this to Todo in A3 Oct 28, 2024
This was referenced Nov 5, 2024
@LHerskind LHerskind linked a pull request Nov 5, 2024 that will close this issue
@LHerskind LHerskind self-assigned this Nov 5, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in A3 Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants