[jira] [Updated] (AMBARI-25546) It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Description: We like this open source software very much, but we found a little problem in use. the maximum parameter on the heapmap page still supports negative numbers and NaN after JS parsing which is not very kindly. examples has been shown in the attachment. was: We like this open source software very much, but we found a little problem in use. the maximum parameter on the heapmap page still supports negative numbers and NaN after JS parsing. examples has been shown in the attachment. > It is unreasonable that the maximum parameter on the heapmap page still > supports negative numbers And NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.5 > > Attachments: heatmap-NaN-screentshot.png, > heatmap-negative-screentshot.png > > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing which is not very kindly. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Description: We like this open source software very much, but we found a little problem in use. the maximum parameter on the heapmap page still supports negative numbers and NaN after JS parsing. examples has been shown in the attachment. was: It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers after parsing. examples has been shown in the attachment > It is unreasonable that the maximum parameter on the heapmap page still > supports negative numbers And NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.5 > > Attachments: heatmap-NaN-screentshot.png, > heatmap-negative-screentshot.png > > > We like this open source software very much, but we found a little problem in > use. > the maximum parameter on the heapmap page still supports negative numbers and > NaN after JS parsing. > examples has been shown in the attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25546) It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing
[ https://issues.apache.org/jira/browse/AMBARI-25546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25546: -- Summary: It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing (was: It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers after parsing) > It is unreasonable that the maximum parameter on the heapmap page still > supports negative numbers And NaN after parsing > --- > > Key: AMBARI-25546 > URL: https://issues.apache.org/jira/browse/AMBARI-25546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: echohlne >Priority: Minor > Fix For: 2.7.5 > > Attachments: heatmap-NaN-screentshot.png, > heatmap-negative-screentshot.png > > > It is unreasonable that the maximum parameter on the heapmap page still > supports negative numbers after parsing. > examples has been shown in the attachment -- This message was sent by Atlassian Jira (v8.3.4#803005)