fix(test): wait for the title hit in the search route test - #367
Conversation
The poll loop stopped at the first page with any hit. Message hits can be indexed before the session title hit, so the title assertion failed under suite load. Poll until user, assistant, and title hits are all present.
|
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 configuration
📒 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 search-route test now continues polling until results include ChangesSearch route test
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Merge Risk: ⚪ Minimal · up to The search-route test now waits for the title result without masking a missing result. No actionable merge risk remains. 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 | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkResolution Replace the unrelated session, workspace, terminal, and other change details with an accurate description of the test update. State the requirement or bug, explain that polling stopped before the title hit appeared, describe the change to wait for user, assistant, and title hits, and note that product behavior is unchanged. Add reproduction steps and root cause if treating this as a bug, and report relevant test coverage.
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 |
commit: |
Related Issue
No public issue. This is maintainer work for session safety, workspace trust, and terminal controls.
Problem
A very large session transcript can crash the local server. A fork drops the source title kind. File tools and git can follow a symlink out of the workspace. Project-local config can apply before the workspace is trusted. The terminal has no setting for the fullscreen layout, no click-to-toggle fold, and no jump-to-bottom control.
What changed
Also in this change:
auto_session_titlecan turn automatic titles off.PYTHINKER_CODE_REPEAT_BREAKER=0turns off the repeated-tool-call stop.Hosted banner targeting and login-region relay selection are not in this change.
Evidence
After: package
tscis clean for agent-core-v2, agent-gateway, transcript, oauth, telemetry, and the CLI. Focused tests: 141 passed (fold, MCP OAuth, repeat breaker, git hardening, real path). Write-tool tests passed. Tower identity fallback passed after the test forcesuser.useConfigOnly.pnpm test,pnpm lint,pnpm build, andnix buildwere not run on this branch.Merge Danger
Door: two-way
Revert the branch. No published version or identity field changes.
Blast Radius: session
Workspace trust, file tools, git calls, session fork titles, and the terminal layout are the user-visible surfaces. A wrong trust gate can hide project-local config until the user trusts the folder.
Checklist
/approve). Internal maintainer change; no public issue.gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update. Config and env docs were updated in the same change. Thegen-docsskill was not run as a separate pass.[skip changeset]
Summary by CodeRabbit