Skip to content

skills: SESSION_BUSY is two CLI invocations, not an in-page lock - #389

Open
ankitranjan7 wants to merge 1 commit into
mainfrom
skills/session-busy-recipe
Open

skills: SESSION_BUSY is two CLI invocations, not an in-page lock#389
ankitranjan7 wants to merge 1 commit into
mainfrom
skills/session-busy-recipe

Conversation

@ankitranjan7

Copy link
Copy Markdown
Contributor

Description

Closes #385. Skill half of #378.

SESSION_BUSY is produced by a second webcmd --session <id> … while the first still holds the Session. It is not a homemade flag inside page.evaluate.

Guidance:

  • Overlap two CLI invocations on the same session id.
  • On SESSION_BUSY, wait for the listed holder, then retry the same command.
  • --force close only when that holder is dead.

Runtime lock implementation stays in #378. Published skill names no eval fixture.

Type of Change

  • 📝 Documentation

Checklist

  • I ran the checks relevant to this PR
  • I updated tests or docs if needed
  • If I edited skill-src/, I ran make build and committed skills/
npx vitest run --project unit src/skills.test.ts: 15 passed

Show overlapping webcmd --session commands as the way to contend for a
Session. Wait and retry; do not lock inside page.evaluate.

Closes #385
@github-actions

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

skills(browser): overlapping commands on one session must use SESSION_BUSY, not an in-page lock

1 participant