fix: clear Electron HTTP cache on startup to prevent stale frontend#451
Merged
fix: clear Electron HTTP cache on startup to prevent stale frontend#451
Conversation
Chromium's HTTP cache persists in the user's app data directory across app updates. This can cause the Electron app to serve stale frontend assets after an update. Clearing the session cache on startup ensures fresh assets are always fetched from the Python backend. Co-Authored-By: Claude Opus 4.6 <[email protected]> Signed-off-by: Yondon Fu <[email protected]>
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.
Summary
app.on('ready')before any window creation or frontend loading%APPDATA%/daydream-scope/persists across updatesawait session.defaultSession.clearCache()Test plan
npm run dist:win), run it, confirm it starts correctly🤖 Generated with Claude Code