fix(workflows): clear pruned loop history via batched deletes - #12
Open
Conversation
Loop pruning deleted each metadata key with its own driver.delete via an unbounded Promise.all. Once a prune exceeded ~128 entries the fan-out overran the actor SQLite coordinator's 128-permit admission cap and failed long-lived ctx.loop workflows with 'SQLite transaction queue is full'. Route pruning through batchDelete, chunking keys at MAX_KV_BATCH_ENTRIES (the engine's KV_TX_MAX_ROWS per-commit cap) and running prefix/range sweeps and key batches concurrently, so permit cost drops from N to ceil(N/128). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Author
|
Stack for rivet-dev/workflows
Get stack: change nputktmr |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Loop pruning deleted each metadata key with its own driver.delete via an
unbounded Promise.all. Once a prune exceeded ~128 entries the fan-out overran
the actor SQLite coordinator's 128-permit admission cap and failed long-lived
ctx.loop workflows with 'SQLite transaction queue is full'.
Route pruning through batchDelete, chunking keys at MAX_KV_BATCH_ENTRIES (the
engine's KV_TX_MAX_ROWS per-commit cap) and running prefix/range sweeps and key
batches concurrently, so permit cost drops from N to ceil(N/128).
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com