You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 899fee2
Browse filesBrowse the repository at this point in the historyBrowse files
fix(daemon): mark every session close keeps after its teardown
A claimed session kept by a failed provider lease release was not marked,
so it pinned daemon idle reap and its claim. One wrapper around close
finalization now marks any session still present after teardown, whichever
step failed.
Align the batching and replay docs with the retry wording: retry close
with the same options, leaving out --save-script once the script is
published.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Copy file name to clipboardExpand all lines: website/docs/docs/batching.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,8 @@ acquisition that would recover another session's durable resources, can also be
26
26
another app in the same session keeps its owned resource handles. An Android test IME alone is
27
27
restored by ordinary `close`, including a bounded step. Restoration may settle after the remaining
28
28
batch time. If it fails on a session that holds a device claim, the session and its claim stay; inspect
29
-
the device, then run `close` again to retry the cleanup. A session without a claim is retired. Run a refused step separately with its original arguments and options, the same `--session` value, and
29
+
the device, then retry `close` with the same options, leaving out `--save-script` once the script is
30
+
published. A session without a claim is retired. Run a refused step separately with its original arguments and options, the same `--session` value, and
30
31
the same private CLI context. Inspect `details.partialResults` and
31
32
`details.dispatchedSteps` before retrying the batch: earlier steps may already have changed the app.
32
33
The batch still authenticates and renews its own lease while it runs.
Copy file name to clipboardExpand all lines: website/docs/docs/replay-e2e.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,8 +24,8 @@ affects `close` when it would dispose owned resources or release a provider leas
24
24
that would recover another session's durable resources. Opening another app in the same session
25
25
keeps its owned resource handles. An Android test IME alone is restored by authored `close`, even
26
26
when restoration settles after the remaining replay time. A failed restore on a session that holds a
27
-
device claim keeps the session and its claim; inspect the device, then run`close`again to
28
-
retry the cleanup. A session without a claim is retired. The name is not a complete command. Inspect the failed
27
+
device claim keeps the session and its claim; inspect the device, then retry`close`with
28
+
the same options, leaving out `--save-script` once the script is published. A session without a claim is retired. The name is not a complete command. Inspect the failed
29
29
script path and line, then run that original operation separately with its original arguments and
30
30
options, the same `--session` value, and the same private CLI context. If steps remain and the
31
31
report offers `resume.alternateFrom`, use it with `planDigest` after completing the refused step directly.
0 commit comments