🤖 fix: bump usageStore when MuxMessage is stored #696
Merged
Conversation
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
When compaction is interrupted, we don't receive usage metadata from the interruption event itself. However, we do have historical usage data from messages stored in the aggregator. Without bumping usageStore when MuxMessages are received, the UI doesn't re-render to display this historical usage, making it appear as if costs have reset. This single-line addition ensures the usage store stays in sync with message arrivals, so historical usage data is properly reflected in the UI. Fixes #695 _Generated with `mux`_
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.
When compaction is interrupted, we don't receive usage metadata from the interruption event itself. However, we do have historical usage data from messages stored in the aggregator. Without bumping usageStore when MuxMessages are received, the UI doesn't re-render to display this historical usage, making it appear as if costs have reset.
This single-line addition ensures the usage store stays in sync with message arrivals, so historical usage data is properly reflected in the UI.
Changes
this.usageStore.bump(workspaceId)after live MuxMessage storage in WorkspaceStoreTesting
Relates to #695
Generated with
mux