Delete all alarms on abortAllDurableObjects()
#1918
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.
Fixes cloudflare/workers-sdk#5388
In the Workers Vitest integration, we call the
abortAllDurableObjects()
function after each test to abort all Durable Objects and close all SQLite databases. If the isolated storage option is enabled, we backup/restore.sqlite
files to automatically undo writes performed in tests. Right now, this doesn't cancel Durable Object alarms. This means that an alarm scheduled in one test might end up firing when another later test is running. This could lead to unexpected test results, and non-determinism in tests.This PR addresses this issue by automatically deleting all Durable Object alarms when
abortAllDurableObjects()
is called. This is a local-only internal API that's currently only used in the Vitest integration, so making this breaking change is fine. 馃憤