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
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Fixed
--mode runtime now addresses the player. It only ever affected cs exec; health and every canonical command went to the editor regardless. So cs health --mode runtime called a dead player healthy, and cs command session/list --mode runtime listed the editor's REPL sessions
rather than the ones cs exec --mode runtime had created in the player.
Commands whose contract does not require the editor now reach the player. command/list and command/registry.snapshot deliberately stay with the
editor, which owns registry authority; answering them from a player would
overwrite the project's cached contracts with its shorter list.
When no player answers on 15500-15509, commands that need one exit 3 and say
so instead of falling back to the editor.
cs batch --mode runtime sent the whole batch to the editor while cs command
reached the player, so the same command id answered from a different process
depending on how it was invoked — and a batch of mutations applied to the
editor. A batch is one roundtrip, so command/list and command/registry.snapshot cannot be split out of it and are refused there
instead; request them separately without --mode runtime.
Added
cs pull retrieves a file from whichever process is being addressed. A
relative path resolves against the target's persistentDataPath — the form to
use against another machine, since Android and iOS give a user no absolute
path to hold. An absolute path names a file on the target and is used as
given. Every pull reports which rule applied. Large files are fetched as
successive ranges.
references/player.md covers debugging a running player: what it answers,
why a device reports no consoleLogPath, and how to record a profiler capture
on a device and open it at home.
runtime/info routing: the device, build, and well-known paths of whichever
process replies.
Changed
The runtime port probe runs its ten candidates concurrently at 1s each rather
than one after another at 0.3s. Hosts that drop packets to closed ports made
the sequential form cost the full timeout per port, and the longer per-port
budget suits a player on another machine.
The package-owned registry grows to 62 (56 authoring + 6 control).