Repository navigation
test(feed): wait for zero-wait Codex permission acceptance - #16536
Conversation
…cking attention Zero-wait Feed ingress acknowledges at enqueue and accepts asynchronously on the ingress lane, so the test raced the delivery and saw no attention event. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FrR7YbsQtGw2eFtDeyiTcK
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. 🧰 Additional context used📚 Code guidelines (3)No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: manaflow-ai/cmux/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 1 remain after this review. 📝 WalkthroughWalkthroughThe zero-wait Codex permission test now waits for the asynchronous ChangesCodex permission acceptance test
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~8 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to This test change waits for asynchronous acceptance before checking attention events. The callback ordering and bounded wait leave no actionable merge-blocking risk. 🚥 Pre-merge checks | ✅ 24 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (24 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
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 |
|
All contributors have signed the CLA ✍️ ✅ |
|
Subagent review at ecbca1c: approve. On the zero-wait path, |
CI failure attributionCI passes on Written by |
Bugbot is paused — on-demand spend limit reachedBugbot uses usage-based billing for this team and has hit its on-demand spend limit. A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue. |
|
Green at 38b64bb; landing. Resource check: test-only. It adds one semaphore wait capped at 2 s inside a single test and changes no product code, so no runtime CPU, memory or disk impact. |
|
Merge receipt for |
0bfd027 test(cloud): fix the Cloud header and moved-panel focus tests that never ran (manaflow-ai#16539) c5c4345 localization: accept numbered placeholders in any order (manaflow-ai#16376) 456edeb fix(settings): replace custom sidebar mockups with real previews (manaflow-ai#16569) 98dc3ab Prototype: cmux Cloud as a remote MCP server (manaflow-ai#16568) 6c22525 test(remote): isolate tmux stale-surface fixture (manaflow-ai#16566) 3ec9918 Re-land "fix(coderouter): initialize Cloud VM account pools (manaflow-ai#16397)" (manaflow-ai#16572) 2b895a5 Fix browser paste routing with terminal text box beta (manaflow-ai#6380) (manaflow-ai#16560) 2bd3455 localization: check Swift defaultValue literals against their catalog en value (manaflow-ai#16396) c43086e test(cli): expect --mark-read to mark every listed inbox message (manaflow-ai#16537) fcda4f0 test(feed): wait for zero-wait Codex permission acceptance before checking attention (manaflow-ai#16536) 7d57a03 fix(remote): evict stale persistent SSH bridge leases (manaflow-ai#16558) d630cb8 docs: add protected-folder diagnostics for tmux sessions (manaflow-ai#12219) 7dceaac test: create cwd fixtures that new terminals now resolve on disk (manaflow-ai#16538) 28cc575 docs: cover surface resume binding CLI contract (manaflow-ai#16473) 5c7dca1 Fix idle zsh PR probes triggering chpwd hooks (manaflow-ai#16553) # Conflicts: # .github/workflows/ci-guards.yml
Summary
FeedCoordinatorTests.zeroWaitCodexPermissionSurfacesTransientNeedsInputAttention, added in #15926, fails on main withattention.events.count → 0. The product change works as intended. The test is racy:ingestBlocking(waitTimeout: 0)acknowledges when the event is enqueued, and the ingress lane accepts it later on its execution queue. That ordering is the documented zero-wait contract (zero-wait telemetry must acknowledge before asynchronous acceptance). The test read the attention recorder as soon asingestBlockingreturned, so it usually ran before the main-actor acceptance that surfaces attention.The test now passes an
onAcceptedcallback and waits for it before checking the recorder. No product code changes.Testing
CI; no local build per team rule.
Changelog
none
🤖 Generated with Claude Code
https://claude.ai/code/session_01FrR7YbsQtGw2eFtDeyiTcK
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by cubic
Fixes the racy
zeroWaitCodexPermissionSurfacesTransientNeedsInputAttentiontest, which read the attention recorder before zero-wait ingress had asynchronously accepted the event.onAcceptedcallback before asserting on the attention hook.Written for commit 38b64bb. Summary will update on new commits.
Summary by CodeRabbit