perf: push Eidoverse travel destinations from a shared watcher - #8579
Merged
Merged
Conversation
atomantic
force-pushed
the
claim/issue-8536
branch
from
September 26, 2026 01:26
cd95fc8 to
8b0c8bb
Compare
atomantic
force-pushed
the
claim/issue-8536
branch
from
September 26, 2026 01:34
8b0c8bb to
9bf157f
Compare
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Eidoverse travel currently probes every online peer every 30 seconds in each open tab. Share that ongoing work in one server watcher while visible travel panels subscribe, and push changed destination snapshots directly to those panels.
The watcher stops after the last unsubscribe/disconnect, serializes probes and drops obsolete results. Panels reconcile once on reconnect or tab re-show and protect pushed snapshots from older HTTP responses. Deferred world updates resume when projection/editing gates clear, without another poll or destination event. Existing peer admission, authentication and private-network boundaries remain unchanged.
Validation: focused socket/component regressions; pregate (733 server files, 28 client files); client build; isolated boot smoke. The configured Codex reviewer returned no findings. The boot smoke passed its survival check and used its SIGKILL shutdown fallback; the readiness validation gap is tracked separately in #8581.
Refs #8536
Remaining
This is the guest-travel slice of #8536. The same issue still tracks AI provider/quota cards, fleet setup and usage, Jev/Laya status, loaded models and memory management, Browser/Tailcat status, usage-backfill progress, and Eidoverse projection progress. MediaCapacityPanel is already socket-driven on the base branch.