Accept QA7 routine wording variants - #5423
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughSummary by CodeRabbit
WalkthroughAdds ChangesOR-matching helper and qa_7c update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~4 minutes Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (3 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 |
There was a problem hiding this comment.
Code Review
This pull request introduces a helper function _required_text_matches to support pipe-separated alternative options in the required_text matching logic for live QA routines, updating the qa_7c_slack_bug_logger_routine case and adding corresponding unit tests. The review feedback points out a potential issue where empty options (e.g., due to trailing or consecutive pipes) could vacuously succeed, and suggests filtering out empty strings and handling text normalization directly within the helper function.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/reborn_webui_v2_live_qa/run_live_qa.py`:
- Around line 1031-1033: The word-check in the required-text matching logic is
currently using raw substring containment, which lets `bug` match inside
unrelated words like `debug` or `bugfix`. Update the matching in
`run_live_qa.py` within the `all(...)`/`any(...)` block to perform word-aware
matching instead of `option.strip().lower() in normalized_text`, so the `bug`
requirement is only satisfied by a standalone word while preserving the existing
handling of `piece.split('|')` alternatives.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 3d68b416-9eae-43f6-94af-9fa41ae9b889
📒 Files selected for processing (1)
scripts/reborn_webui_v2_live_qa/run_live_qa.py
Summary
|bugWhy
QA 7C can legitimately report the created automation as "fires every 5 minutes" or "watches Slack" instead of literally saying "trigger". The latest
/canary allfailure showed the routine was described successfully but rejected by an overly literal text gate.Verification
python3 -m pytest scripts/reborn_webui_v2_live_qa/test_run_live_qa.py -q