Repository navigation
server: fan ticket results out to each event subscriber - #113
Merged
Merged
Conversation
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
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.
A half-open learning event stream could consume a ticket result from the shared queue before the current core received it, leaving that core waiting indefinitely after reconnecting to a retained engine. Each subscriber now owns a queue, and terminal results are sent to every open subscriber.
Completed Cormac's handed-off implementation. Verified the rebuilt isolated CPU engine with tools/server/tests/learn-tickets.py, including two simultaneous streams receiving the same ticket result. The test also covers revoke/unload and no replay of results produced without subscribers. Build and live fixture passed on IntelMac; normal CI and core live-engine integration remain required. Core pin has not moved.