-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix formatting cumulative memory in Web UI #12596
Conversation
Can you please make labeller apply the |
</td> | ||
{taskRetriesEnabled && | ||
<td className="info-failed"> | ||
{formatDataSizeBytes(query.queryStats.failedCumulativeUserMemory / 1000.0) + " seconds"} | ||
{formatDataSize(query.queryStats.failedCumulativeUserMemory / 1000.0) + "*seconds"} |
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.
MB*s
? (MBs
would be correct, but not clear)
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.
I started with MBs but yeah, I think it is not clear.
Elsewhere we use full seconds
(not an abbreviation), so I guess this is fine.
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.
optional
Value for cumulative memory of a query was previously reported using following format: "4.33T seconds". It is not obviouls that it represents integer of memory coinsumption over time. This commit changes format to: "4.33TB*seconds"
5ccddb0
to
5fd2387
Compare
👍 |
Value for cumulative memory of a query was previously reported using
following format:
"4.33T seconds". It is not obviouls that it represents integer of memory
coinsumption over time.
This commit changes format to:
"4.33TB*seconds"
Related issues, pull requests, and links
Documentation
(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
( ) No release notes entries required.
(x) Release notes entries required with the following suggested text: