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 bf30354
Browse filesBrowse the repository at this point in the historyBrowse files
fix(workspace): ask about the running engine the way it runs, and keep asking until the answer is given
Four sites where a rule stated in one place had not reached its neighbour.
The reuse answer, like the attached one, is given after announcements that
are awaits; it now asks the same two questions again after the last of them
and settles a change the same way it would have before them. The verdict
handling is one closure asked twice, so the two askings cannot drift.
The version probe resolves a relative `cwd` against the instance directory,
as the engine's own launch does; probed against wherever this process
started, a relative command or PATH entry could name a different binary
than the one the engine runs.
The memo's re-probe key carries the whole launch identity of both halves,
not their argv: a replacement with the same argv under a different PATH or
working directory runs a different binary and is probed again.
`entryIdentity` is the one definition, shared with `sameEntry`.
The undo keeps an entry that was rewritten AND disabled while it was held.
Projecting the disable onto what the undo replaced would have overwritten
the newer transport with the old one; neither the transport nor the disable
is ours.
A read-count fixture gains the reuse answer's second intent read. Reverting
each of the four fails a named test.
0 commit comments