feat: handle grpc events #986
Merged
+53
−51
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
…nents in Main function (#987)
…multiple StreamEventsClient anyway
…ltiple StreamEventsClient anyway
ym
approved these changes
Nov 20, 2025
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.
Problem
The HDMI status label on the physical device display remained stuck on "Disconnected" even when video was actively streaming.
Root Cause
The gRPC event processing goroutine was never started. While events from the native video process were successfully received and buffered in
eventCh, no code was consuming them. ThehandleEvent()method and callbacks were properly configured but unreachable - events accumulated in the channel buffer but were never processed.Solution
Move the uncalled goroutine to
NewGRPCClient()to continuously read fromeventChand process events.