fix: keep panel progress active when navigating away during categorization - #49
Open
Harsh16gupta wants to merge 1 commit into
Open
fix: keep panel progress active when navigating away during categorization#49Harsh16gupta wants to merge 1 commit into
Harsh16gupta wants to merge 1 commit into
Conversation
Harsh16gupta
force-pushed
the
fix/panel-state-persistence
branch
from
August 21, 2026 17:37
2085a3e to
126364b
Compare
Harsh16gupta
force-pushed
the
fix/panel-state-persistence
branch
from
August 21, 2026 17:59
126364b to
538d99a
Compare
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.
What was broken? (this was reported by a user on the forum -- I tried to reproduce the bug but was not able to do it.)
If you start the categorization pipeline and navigate away (like opening Tools → Options) while the model is loading or embeddings are being generated, the side panel resets to the initial "No categories yet" screen when you come back.
The pipeline was still running in the background, but the UI completely lost track of it. If a user clicked "Run" again at that point, it would also kick off a second redundant pipeline run.
What changes in this PR?
setupPanel.tsso ifoperationState.inProgressis already true, clicking run just returns the current state instead of launching another pipeline.operationState.inProgressas true on start, and reset it to false insideonCompleteandonError.getInitialStateso if the webview queries initial state while a background job is running, it receives a status update rather than an idle state.AppStateContext.tsx, if the initial IPC response is delayed/missed because the main thread is busy loading models/embeddings, the webview will retry polling up to 5 times to catch back up with the running job.