fix: ensure time-based future operations are queued and executed #25722
+93
−14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Reopen #25675
Time‑based FutureOperations were never actually used: they were created but never stored in the shared queue or removed from it, so they never executed.
queueOperations and runQueuedTimeOperations took the time queue slice by value and modified only a local copy. We changed both functions to take a *[]FutureOperation and updated all call sites to pass &timeOperationQueue, then updated the code to work through the pointer. Now time‑scheduled operations are correctly enqueued, executed when their BlockTime is reached, and removed from the global queue.