Repository navigation
test(e2e): wait for resolved context window in visual chat scenario - #1941
Conversation
The chat visual scenario captured its screenshot before the selected model's metadata had resolved. Router models arrive asynchronously over the extension-host message channel, so the context-window readout briefly rendered the `1` fallback, producing non-deterministic screenshots. Wait for a resolved context window before capturing. Failing runs: - https://github.com/Zoo-Code-Org/Zoo-Code/actions/runs/37288898485/job/111694365121 - https://github.com/Zoo-Code-Org/Zoo-Code/actions/runs/37287279414/job/111689058401 - https://github.com/Zoo-Code-Org/Zoo-Code/actions/runs/37347520689/job/111889755914
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review. 📜 Recent review details🧰 Additional context used📚 Code guidelines (1)📓 Path-based instructions (4)Check strict typing and exhaustive behavior across normal, boundary, error, cancellation, retry, and compatibility paths.⚙️ CodeRabbit configuration file Files:
Reserve end-to-end coverage for behavior that requires the real VS Code host, workspace APIs, extension activation, webview messaging, file watchers, or a full workflow.⚙️ CodeRabbit configuration file Files:
Act as an adversarial second-opinion reviewer.⚙️ CodeRabbit configuration file Files:
Source excerpt: Keep the Electron matrix limited to high-value shell integration scenes that require the real VS Code host.📄 CodeRabbit inference engine (apps/vscode-e2e/AGENTS.md) Files:
🔇 Additional comments (1)
📝 SummarySummary by CodeRabbit
WalkthroughThe chat visual test waits up to 60 seconds for ChangesChat visual test
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Merge Risk: ⚪ Minimal · up to Chat screenshots wait for the selected model’s context-window metadata before capture. The configured model resolves to a value distinct from the fallback, and no actionable merge risk remains beyond normal checks. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 7 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (7 passed)
Full details: Description checkExplanation The description explains the screenshot failure and its cause, and includes failing run links. It does not provide the required approved issue link or a test procedure, so key template information is missing. Resolution Add the approved GitHub issue number under “Related GitHub Issue” and document how the change was tested and how reviewers can reproduce or verify it under “Test Procedure”. Also complete the applicable pre-submission checklist items before marking the PR ready for review.
✨ Finishing Touches🧪 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 |
Review statusThanks for contributing. This comment tracks the review sequence and the next action. Current step: Awaiting fresh human maintainer or CODEOWNER approval. Automated review is complete for the latest commit but does not replace human approval. Review-state labels are managed by this workflow; do not edit them manually. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
The chat visual scenario captured its screenshot before the selected model's metadata had resolved. Router models arrive asynchronously over the extension-host message channel, so the context-window readout briefly rendered the
1fallback, producing non-deterministic screenshots. Wait for a resolved context window before capturing.Failing runs: