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.
Fix duplicate events on re-initialize
The frontend code maintains a variable containing the last event from the event stream on the server received over the socket. It uses this when a reinitialization occurs to make sure that the full event stream is not sent over the socket again.
However, the socket does not just contain events from the event stream - it also contains other pseudo events that do not have an ID - for example:
{token: "******", status: "ok"}
{status_update: true, type: "info", id: "STATUS$CONTAINER_STARTED", message: "Container started"}
If one of these happened to be the last event received, then the stream was duplicated.
This PR updates the stream to only store a last event if it has a numeric id.
#5358
To run this PR locally, use the following command: