fix(code): hydrate cloud runs after renderer reload#1631
Merged
Conversation
joshsny
approved these changes
Apr 14, 2026
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
2 participants
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
reloading PostHog Code during an active cloud run could leave the chat view stuck on an infinite spinner (🧵 thread)
The main-process cloud watcher survives the reload, but the fresh renderer store starts empty. On reconnect, the renderer could reattach to the existing watcher without rebuilding the session from persisted logs, leaving the session with no events and no processed log count. We need to hydrate ✨
Changes
Hydrate cloud sessions from persisted logs when reconnecting after a reload and the renderer does not yet have processed cloud history. Also added some regression coverage.