This repository was archived by the owner on May 13, 2025. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 36
Stats response changes #443
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Values need to be formatted before display in the UI.
The function now returns raw numeric values instead of pre-formatted byte strings, but the UI components (lines 86, 98, 106, 115, 123) still display these values directly without formatting. This will result in plain numbers being shown to users instead of human-readable formats like "1.2 MB".
Apply the following changes to ensure proper formatting:
return { - storageSize, - lifetimeIngestedSize, - lifetimeStorageSize, - deletedStorageSize, - ingestedSize, + storageSize: formatBytes(storageSize), + lifetimeIngestedSize: formatBytes(lifetimeIngestedSize), + lifetimeStorageSize: formatBytes(lifetimeStorageSize), + deletedStorageSize: formatBytes(deletedStorageSize), + ingestedSize: formatBytes(ingestedSize), lifetimeCompressionRate, activeCompressionRate, };Alternatively, update all display components to format these values at render time.
Also applies to: 158-166
💡 Verification agent
🧩 Analysis chain
Ensure consistent data property path access notation.
There's an inconsistency in how the data property paths are accessed:
parseable_storage_size_data,parseable_events_ingested_size)parseable_lifetime_storage_size.data,parseable_deleted_storage_size.data)This inconsistency could lead to access errors if the data structure is uniform across all properties.
🏁 Script executed:
Length of output: 612
The previous script’s use of the
--type tsxflag produced errors because “tsx” isn’t a recognized file type for ripgrep. This revised script uses glob patterns to include both.tsand.tsxfiles, which should yield the expected output for verifying property path usage across the codebase. Please run this script and review the results to determine whether the inconsistent property access (dot notation vs. underscore notation) is indeed an issue that needs addressing.🏁 Script executed:
Length of output: 6687
Consistent Property Access Required: Update Dot Notation to Underscore Notation
In
src/pages/Systems/StorageSection.tsx, the property access for lifetime and deleted storage sizes is inconsistent with the type definitions. While other properties use the underscore naming convention (e.g.,parseable_storage_size_data), the code currently uses dot notation for these two properties:_.get(record, 'parseable_lifetime_storage_size.data', 0)to_.get(record, 'parseable_lifetime_storage_size_data', 0)_.get(record, 'parseable_deleted_storage_size.data', 0)to_.get(record, 'parseable_deleted_storage_size_data', 0)This adjustment aligns with the definitions in
src/@types/parseable/api/clusterInfo.tsand ensures uniform data access.