prefect-fix-resolve-race-condition
## Task A few enterprise customers running Prefect Server using compound automations are reporting that under busy event traffic the parent automation sometimes never fires or fires twice when all child events from a single batch came through. Can you please investigate and fix the issue so the parent fire exactly once per legitimate batch? ## General instructions - The code repo is at /repo/prefect. - You are inside of a Docker container. You may not be able to perform all operations you would normally be able to do on a local machine. Dependencies have not been pre-installed, and you may need to install them yourself. - You are expected to act autonomously as a software engineer to complete tasks you are given. - Do not stop until you feel you have completed the task and your code changes can be merged. - You may need to use software engineering skills like analyzing the codebase, researching technologies, running services, analyzing logs, etc. to complete the task. Not all tasks will be solvable by reading source code alone.
Agent Results
Agent details
Verifier Tests
Gemini 3.1 Pro2/3
Rubric Criteria
Gemini 3.1 Pro4/4
Fail → Pass
serializes_concurrent_compound_trigger_evaluation
atomic_claim_on_clearing_firings
fix_addresses_both_failure_modes
Pass → Pass
preserves_single_child_compound_trigger_semantics
Taste Scores
Patch Bloat— 0.2x
9 agent / 58 oracle SLOC, 2 / 2 files(raw: 0.5x)
Practice Alignment — 3.0/5
3
style consistency3
pattern adherence4
library usage3
abstraction level2
documentation fitRelative Taste — 3.0/5
4
minimality2
approach quality3
hygiene3
fluency2
craftsmanship