test: drop the stale meetAutoOrchestratorHandoff snapshot assertion - #5682
Conversation
The assertion checking that `meetAutoOrchestratorHandoff` defaults to `false` was removed because the feature has been enabled by default, making the check no longer valid. Auto-committed-on: dragonfly Co-authored-by: Medulla <medulla@tinyhumans.ai>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe JSON-RPC end-to-end snapshot test no longer asserts that ChangesSnapshot test update
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This change removes an outdated test expectation without changing production behavior; no actionable merge-blocking risk remains after normal checks and review. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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. Comment |
What
Removes the
meetAutoOrchestratorHandoffassertion fromjson_rpc_app_state_snapshot_returns_runtime_shapeintests/json_rpc_e2e.rs. 11 deletions, tests only.Why
mainis red onRust Core Coverage (cargo-llvm-cov):#5674 removed the meetings domain, so the app-state snapshot no longer carries the field, but this assertion still required it. The gate it guarded (#1299 — don't auto-hand a Meet transcript to the orchestrator without consent) no longer has anything to guard: there is no Meet call to end.
This is the third instance of the same drift. #5681 fixed the first two (the
config_*_meet_settingsRPC expectations inconfig_auth_app_state_connectivity_e2e.rsanddomain_modules_e2e.rs); this one was missed there because it asserts the snapshot field name, not the RPC method name, so ameet_settingsgrep did not reach it.Like the other two, this fails on every PR that merges
main— it is currently the soleRust Core Coveragefailure on #5664, #5667, #5668, #5669 and #5671.Not included
tests/raw_coverage/*.rsstill contain[meet] auto_orchestrator_handoff = …blocks in their TOML config fixtures. Those are inert — an unknown config section is ignored, and those tests pass — so they are left alone rather than widening this fix.Verification
Summary by CodeRabbit