[ 
https://issues.apache.org/jira/browse/YETUS-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472848#comment-15472848
 ] 

Yetus QA commented on YETUS-446:
--------------------------------

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 14m 
18s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} pylint {color} | {color:green}  0m  
6s{color} | {color:green} There were no new pylint issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
 0s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 14m 29s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.11.2 Server=1.11.2 Image:yetus/yetus:e4e4903 |
| JIRA Issue | YETUS-446 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12827496/YETUS-446.02.patch |
| Optional Tests |  pylint  |
| uname | Linux 1f27af23a2b9 3.13.0-93-generic #140-Ubuntu SMP Mon Jul 18 
21:21:05 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | nobuild |
| git revision | master / 4779af3 |
| pylint | v1.6.4 |
| modules | C: . U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-YETUS-Build/493/console |
| Powered by | Apache Yetus 0.4.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> releasedocmaker not handling 0 version in a range correctly?
> ------------------------------------------------------------
>
>                 Key: YETUS-446
>                 URL: https://issues.apache.org/jira/browse/YETUS-446
>             Project: Yetus
>          Issue Type: Bug
>          Components: Release Doc Maker
>    Affects Versions: 0.4.0
>            Reporter: Allen Wittenauer
>            Assignee: Ajay Yadava
>         Attachments: YETUS-446.00.patch, YETUS-446.01.patch, 
> YETUS-446.02.patch
>
>
> Playing around this morning, I seem to have hit an interesting bug.
> {code}
> releasedocmaker --project FALCON --outputdir FALCON --projecttitle 'Apache 
> Falcon' --version 0 --version 1 --range --index --license
> {code}
> results in this URL getting generated:
> {code}
> https://issues.apache.org/jira/rest/api/2/search?jql=project+in+%28%27FALCON%27%29+and++++++++++++++++fixVersion+in+%28%270.0%27%29+and++++++++++++++++resolution+%3D+Fixed&startAt=0&maxResults=100
> {code}
> A completely valid URL.  However,  RDM reports on the screen:
> {code}
> JIRA returns HTTP error 400: Bad Request. Aborting.
> Please make sure the specified projects are correct.
> {code}
>  whereas JIRA spits back
> {code}
> {"errorMessages":["The value '0.0' does not exist for the field 
> 'fixVersion'."],"errors":{}}
> {code}
> So somewhere we are generating an invalid version and not verifying it with 
> JIRA. Additionally, our error message is wrong which isn't going to help the 
> user at all.  :(



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to