scheduler-claim-locking: Serialize scheduler claims #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "task/scheduler-claim-locking"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Assigned idea
Serialize scheduler claims
Approach: Edit task/instruction.md with the unique slug scheduler-claim-locking. Describe the shared state, the lock boundary, and the behavior when a claim is already held.
Verification: task/instruction.md contains the heading
# scheduler-claim-locking.src/scheduler/claim-manager.ts contains a
Map<string, Promise<void>>used to guard claims.Risk: Generated work item; validate by PR diff and gate result.
Required edit: update task/instruction.md with scheduler-claim-locking.
Agent context
Task slug: scheduler-claim-locking
Branch: task/scheduler-claim-locking
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.