Skip to content

Conversation

@adamspofford-dfinity
Copy link
Contributor

@adamspofford-dfinity adamspofford-dfinity commented Nov 7, 2025

This also changes the rescheduling logic to reschedule immediately after first scheduling it, instead of waiting until it's done to reschedule it. This removes the need for 'batches'.

@adamspofford-dfinity adamspofford-dfinity force-pushed the spofford/concurrent-closures branch 2 times, most recently from 85577e5 to 2b351bc Compare November 7, 2025 19:40
@adamspofford-dfinity adamspofford-dfinity force-pushed the spofford/concurrent-closures branch from 2b351bc to b60eb6d Compare November 7, 2025 19:43
@adamspofford-dfinity adamspofford-dfinity marked this pull request as ready for review November 10, 2025 17:35
@adamspofford-dfinity adamspofford-dfinity requested a review from a team as a code owner November 10, 2025 17:35
@lwshang lwshang merged commit 3852db3 into main Nov 11, 2025
15 checks passed
@lwshang lwshang deleted the spofford/concurrent-closures branch November 11, 2025 02:28
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.

2 participants