Bug 1856352
Summary: | Area chart edge case - all data points are zero | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Paul Weil <pweil> | ||||||
Component: | Management Console | Assignee: | Jon Jackson <jonjacks> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||||
Severity: | low | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 4.5 | CC: | aos-bugs, jokerman, spadgett | ||||||
Target Milestone: | --- | ||||||||
Target Release: | 4.6.0 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: |
Cause: Victory does not handle 'all zero' data sets well.
Consequence: y-axis tick marks for all-zero data sets were repeated zeros.
Fix: Update area chart logic to force a y-domain of [0,1] when all data sets are all-zero.
Result: y-axis tick marks for all-zero data sets are "0" and "1".
|
Story Points: | --- | ||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2020-10-27 16:13:56 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Paul Weil
2020-07-13 12:58:30 UTC
Will address next sprint. Created attachment 1711282 [details]
filesystem
Created attachment 1711283 [details]
network
Attached screenshot for refer, Zero data display as a line at 0 y-axis This could be Verified. Checked on 4.6.0-0.nightly-2020-08-12-155346 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196 |