fix: simplify portal serve caching logic and fix debounce scheduling#252
Merged
aliasghar98 merged 1 commit intodevfrom Mar 25, 2026
Merged
Conversation
- Remove unnecessary mutex and event queue from portal serve action
- Fix debounce service to reschedule execution if a new handler arrived
during processing
|
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.
Summary
portal serveaction — these were left over from a prior implementation and no longer needed after theDebounceServicerefactorDebounceServiceto reschedule execution if a new handler arrives while the current one is still processing, preventing missed updatesTest plan
apimatic portal serveand make rapid successive file changes — verify the portal rebuilds and live-reloads correctly without duplicate or missed builds🤖 Generated with Claude Code