• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

umputun / revdiff / 24159838977
89%

Build:
DEFAULT BRANCH: master
Ran 08 Apr 2026 09:34PM UTC
Jobs 1
Files 30
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

08 Apr 2026 09:32PM UTC coverage: 87.396%. Remained the same
24159838977

push

github

web-flow
docs(skill): handle long-running launcher on harnesses with short bash timeouts (#51)

* docs(skill): handle long-running launcher on harnesses with short bash timeouts

Some harnesses (e.g. OpenCode) kill the launcher after a short default
bash timeout while the user is still annotating. Document a two-layer fix
in SKILL.md: prefer setting the bash tool timeout when supported, and add
a recovery fallback that waits for the user to confirm exit and reads the
most recent /tmp/revdiff-output-* file.

* docs(skill): refine timeout guidance with background-task handling

Replace the hardcoded 1800000 suggestion with "max supported by your
harness" after discovering that Claude Code caps at 600000 but does not
kill the child process — it auto-backgrounds the bash call and hands the
model a task output path. The session auto-resumes when the task
completes.

Split Step 3 recovery into two cases:
  - Case A: background task handoff (Claude Code): do not Read the task
    output file while the child is still running; poll via BashOutput or
    trust the auto-resume, then cat the known output path on completion.
  - Case B: hard timeout error (no background handoff): the existing
    user-confirmation + ls -t /tmp/revdiff-output-* recovery.

Validated by running a real revdiff session in a separate Claude Code,
watching the JSONL transcript cross the 600000ms boundary, and observing
auto-background + auto-resume behaviour.

* docs(skill): prefer run_in_background and harden recovery cat

Recommend run_in_background: true on harnesses that support it so the
launcher runs without hitting any timeout cap, and reframe Case A as
the expected collection path rather than recovery. Guard the timeout
recovery cat against empty/missing output files.

* docs(skill): drop run_in_background, recommend max bash timeout

5166 of 5911 relevant lines covered (87.4%)

410.41 hits per line

Jobs
ID Job ID Ran Files Coverage
1 24159838977.1 08 Apr 2026 09:34PM UTC 30
87.4
GitHub Action Run
Source Files on build 24159838977
  • Tree
  • List 30
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • e9f6b51a on github
  • Prev Build on master (#24159617917)
  • Next Build on master (#24160579334)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc