Document or normalize soft wraps in ui.waitFor text matching
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- bun, typescript
- Domain
- cli, testing-qa
Research direction
Start with the ui.waitFor entry point and reproduce the 100x32 TUI case using the visible reply and the existing wait call. Inspect the recorded frame and frame.lines output to determine the current physical-line behavior. Done means either documenting that matching contract or providing and verifying an opt-in soft-wrap-normalized match, with the chosen scope made explicit.
Written by the indexing model from the issue text.
Description
Drive 2.1.0, Bun 1.4.0, OpenCode V2 97303c39dd153b64d7036249b279490201820b19, a 100x32 TUI.
A visible reply can fail ui.waitFor("No sourcebook tools are available yet.") when the substring crosses a terminal soft wrap. The model reply was:
The sourcebook executable is ready, but it is not connected. No sourcebook tools are available yet.
The scripted response completed, but the wait timed out after 5000ms with UiWaitTimeoutError. Adding a paragraph break before “No sourcebook tools…” made the unchanged wait pass. The server-side request/history path was not failing.
It would help to document whether string matching is against physical terminal lines, or offer an opt-in soft-wrap-normalized match. The error object's frame.lines printed as [Object ...] through run, so identifying the wrap required inspecting the recording.
Expected: either a documented physical-line matching contract, or a way to wait for visible prose independently of soft wrapping. No runtime change is needed for the workaround: use a shorter visible substring or a semantic/server-side predicate.
- Dominant language
- TypeScript
- Stars
- 32
- Forks
- 4
- Avg merge
- 10m
- Merged PRs (30d)
- 13
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from anomalyco/opencode-drive
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
anomalyco/opencode-drive#102 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
anomalyco/opencode-drive#104 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
anomalyco/opencode-drive#103 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
anomalyco/opencode-drive#97 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 68/100
anomalyco/opencode-drive#86 · 1 comment ·
Maintainers usually reply within 1 day
All issues in anomalyco/opencode-drive
Similar issues
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
opensearch-project/security-dashboards-plugin#2545 ·
Maintainers usually reply within 1 day
-
Add: Dream TR SDOpencheck:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
doctor integrity sample scans soft-deleted pages on Postgres (batch path has no deleted_at filter)Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
SocialGouv/egapro#4672 · 1 comment ·
Maintainers usually reply within 2 days
-
area:agents area:tui bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
anthropics/claude-code#98358 ·
Maintainers usually reply within 1 day