Unify backend resolution + surface dropped stream frames#315
Merged
Conversation
…frames, drop dead isInitializing
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.
Backend-layer cleanup (no behaviour change for the default Pyodide path).
initBackendFromUrl()+autoDetectBackend()were both awaited at startup and could each independentlyswitchBackend('flask')+init(). Replaced by a singleresolveBackend()with clear precedence: URL?backend=flaskoverride → same-origin/api/healthprobe → Pyodide default.+page.sveltenow calls the one function. Theremotebackend stub in the registry is kept (planned).JSON.parsefailures on stream-data (// Ignore parse errors); now they emit a stderr note so a corrupt frame is visible instead of vanishing.isInitializingin PyodideBackend (set, never read).svelte-check: 0 errors/0 warnings; production build (incl. worker) succeeds.Note: deliberately did not lift the stream-message dispatch into
AbstractBackend— the two implementations are subtly divergent (id-matching vs none; ordering of callback-vs-state-clear) in the streaming hot path, so the small dedup wasn't worth the regression risk.