Fix: pass run identity on A5 dependency collector error close - #2484
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe discharge-error path in ChangesDevice error emission
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The incomplete run’s dependency graph is not published, and no material merge-blocking risk is established for this change. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit checks the run epoch with care, Comment |
The boundary-wait discharge error path still calls the old one-argument emit_device_dep_gen_graph signature, breaking both A5 onboard runtime builds after the retained dependency-graph collector change. Pass the current run epoch and the unsuccessful completion verdict used by the adjacent collector teardown. Keep the discharge error authoritative and avoid marking a failed retirement as a clean dependency-graph close.
Problem and change
Main at
92a14e4e7fails to build both A5 onboard runtimes after #2483:DeviceRunner::drain_executionstill calls the old one-argumentemit_device_dep_gen_graphon its boundary-wait discharge-error path, while the method requires three arguments.Pass
prepared.identity.run_epochandfalse, matching the adjacent collector teardown's unsuccessful completion verdict. The originaldischarge_rcremains authoritative; this path does not certify a clean retained dependency-graph close.This is a one-line build fix. No parameter API or planning documents are included.
Validation
pip install --no-build-isolation -e .: both A5 runtime builds report no matching one-argument call.test_a5_tmr_dep_gen_retained_runs,test_a5_tmr_dep_gen_run_identity, andtest_a5_hbg_dep_gen_run_identity. The retained-run suite includesUnprovenCompletionPublishesNothing; these tests cover the collector contract, not an injected onboard discharge failure.