[jira] [Updated] (AMBARI-25546) 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: -- External issue URL: (was: https://github.com/apache/ambari/pull/3221) Fix Version/s: (was: 2.7.5) 2.7.6 > 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.6 > > Attachments: heatmap-NaN-screentshot.png, > heatmap-negative-screentshot.png > > Time Spent: 10m > Remaining Estimate: 0h > > 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) 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: -- External issue URL: https://github.com/apache/ambari/pull/3221 > 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 > > Time Spent: 10m > Remaining Estimate: 0h > > 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] [Commented] (AMBARI-25546) 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:comment-tabpanel=17179710#comment-17179710 ] echohlne commented on AMBARI-25546: --- we try to enhance the validation of the input text, here is the pr: [https://github.com/apache/ambari/pull/3221] please help to review it thanks a lot. > 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 > > Time Spent: 10m > Remaining Estimate: 0h > > 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) 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: The maximum parameter on the heapmap page still supports negative numbers And NaN after parsing (was: the maximum parameter on the heapmap page still supports negative numbers And NaN after parsing) > 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) 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: 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 And NaN after parsing) > 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 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)
[jira] [Updated] (AMBARI-25545) If the file or directory name in HDFS contains non-ASCII characters, the name of zip file generated by downloading will be displayed incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-25545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] echohlne updated AMBARI-25545: -- Description: Steps to Reproduce: # create a directory contains non-ascii characters such as create a Chinese directory or a Japanese directory. # Select a directory just created in step 1, then click download button, and you can see that the name of the generated zip file is incorrect. The problem screenshot is shown in the attachment. was: Steps to Reproduce: 1. create a directory contains non-ascii characters such as create a Chinese directory or a Japanese directory. 2. Select a directory just created in step 1, then click download button, and you can see that the name of the generated zip file is incorrect. > If the file or directory name in HDFS contains non-ASCII characters, the name > of zip file generated by downloading will be displayed incorrectly > > > Key: AMBARI-25545 > URL: https://issues.apache.org/jira/browse/AMBARI-25545 > Project: Ambari > Issue Type: Bug > Components: contrib >Affects Versions: 2.7.4 > Environment: ambari 2.7.4 >Reporter: echohlne >Priority: Major > Fix For: 2.7.6 > > Attachments: question-screenshot.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Steps to Reproduce: > # create a directory contains non-ascii characters such as create a Chinese > directory or a Japanese directory. > # Select a directory just created in step 1, then click download button, and > you can see that the name of the generated zip file is incorrect. > > The problem screenshot is shown in the attachment. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25546) It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers after parsing
echohlne created AMBARI-25546: - Summary: It is unreasonable that the maximum parameter on the heapmap page still supports negative numbers 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 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)
