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

[1.0 - > main] treat a end_block_num=0 as "forever" in snapshot scheduler for compatibility with leap 4.0 behavior #584

Merged
merged 5 commits into from
Aug 19, 2024

Conversation

spoonincode
Copy link
Member

Merges AntelopeIO/leap#2402 & #571 in to main, which resolved AntelopeIO/leap#2261

[5.0] treat a `end_block_num=0` as "forever" in snapshot scheduler for compatibility with leap 4.0 behavior
[5.0 -> 1.0] treat a `end_block_num=0` as "forever" in snapshot scheduler for compatibility with leap 4.0 behavior
@ericpassmore
Copy link
Contributor

Note:start
group: STABILITY
category: CONFIG
summary: To keep compatibility with previous versions of Leap treat end block num=0 as forever in the snapshot scheduler.
Note:end

Base automatically changed from GH-528-limit-sync-main to main August 19, 2024 17:42
@spoonincode spoonincode linked an issue Aug 19, 2024 that may be closed by this pull request
@spoonincode spoonincode merged commit 754d75f into main Aug 19, 2024
36 checks passed
@spoonincode spoonincode deleted the ss_end_block_num=0 branch August 19, 2024 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Snapshot Scheduling Broken in 5.0.x
4 participants