[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998231#comment-13998231 ] Hudson commented on YARN-2016: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1753 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1753/]) YARN-2016. Fix a bug in GetApplicationsRequestPBImpl to add the missed fields to proto. Contributed by Junping Du (jianhe: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1594085) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/impl/pb/GetApplicationsRequestPBImpl.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/api/TestGetApplicationsRequest.java > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Fix For: 2.4.1 > > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998507#comment-13998507 ] Junping Du commented on YARN-2016: -- bq. It would be good to have a unit test as I mentioned before. The test case I uploaded was specific to one issue, but tests with directions of the wire transfers and something like that would be also. May be that is something I will consider adding. [~venkatnrangan], you are right that end-to-end functional test (cover whole process of client, wire and server) like your demo test code is also very helpful. It would be great if you can file some JIRA and contribute it. I will help to review it. Thanks! > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Fix For: 2.4.1 > > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998193#comment-13998193 ] Hudson commented on YARN-2016: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1779 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1779/]) YARN-2016. Fix a bug in GetApplicationsRequestPBImpl to add the missed fields to proto. Contributed by Junping Du (jianhe: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1594085) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/impl/pb/GetApplicationsRequestPBImpl.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/api/TestGetApplicationsRequest.java > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Fix For: 2.4.1 > > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[
https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994162#comment-13994162
]
Hadoop QA commented on YARN-2016:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12644248/YARN-2016.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3730//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3730//console
This message is automatically generated.
> Yarn getApplicationRequest start time range is not honored
> --
>
> Key: YARN-2016
> URL: https://issues.apache.org/jira/browse/YARN-2016
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
>Affects Versions: 2.4.0
>Reporter: Venkat Ranganathan
>Assignee: Junping Du
> Attachments: YARN-2016.patch, YarnTest.java
>
>
> When we query for the previous applications by creating an instance of
> GetApplicationsRequest and setting the start time range and application tag,
> we see that the start range provided is not honored and all applications with
> the tag are returned
> Attaching a reproducer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996780#comment-13996780 ] Karthik Kambatla commented on YARN-2016: Sorry for missing those merge-backs. A simple unit test like here wouldn't have let the mistake happen. > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Fix For: 2.4.1 > > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997187#comment-13997187 ] Venkat Ranganathan commented on YARN-2016: -- [~djp] It would be good to have a unit test as I mentioned before.The test case I uploaded was specific to one issue, but tests with directions of the wire transfers and something like that would be also. May be that is something I will consider adding > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Fix For: 2.4.1 > > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997114#comment-13997114 ] Junping Du commented on YARN-2016: -- bq. Sorry for missing those merge-backs. A simple unit test like here wouldn't have let the mistake happen. No worry. We all make mistakes. :) I am proposing to add a simple unit test like this for any PBImpl changes in future. [~kasha] and all in watch list, Thoughts? > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Fix For: 2.4.1 > > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996512#comment-13996512 ] Junping Du commented on YARN-2016: -- [~venkatnrangan], you are right. When similar bug happens, we often suspect the logic in client or server but ignore the wire logic. In most cases, we don't even have a simple unit test to verify these PBImpls which cause bug get hidden easily. Already filed YARN-2051 to address this, it would be great if you want to help there. Thanks! > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Fix For: 2.4.1 > > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996037#comment-13996037 ] Venkat Ranganathan commented on YARN-2016: -- Thanks for fixing this. +1 on adding more unit tests. I think this area seems to be needing more tests as we also saw that this issue was not thought to be a problem (see YARN-1977 which does not validate the PB part) > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Fix For: 2.4.1 > > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995981#comment-13995981 ] Hudson commented on YARN-2016: -- FAILURE: Integrated in Hadoop-trunk-Commit #5604 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5604/]) YARN-2016. Fix a bug in GetApplicationsRequestPBImpl to add the missed fields to proto. Contributed by Junping Du (jianhe: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1594085) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/api/protocolrecords/impl/pb/GetApplicationsRequestPBImpl.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/api/TestGetApplicationsRequest.java > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Fix For: 2.4.1 > > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995925#comment-13995925 ] Junping Du commented on YARN-2016: -- Thanks [~jianhe] for review and comments! Filed YARN-2051 to address more tests for PBImpl. > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Fix For: 2.4.1 > > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[
https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995498#comment-13995498
]
Hadoop QA commented on YARN-2016:
-
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12644248/YARN-2016.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3733//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3733//console
This message is automatically generated.
> Yarn getApplicationRequest start time range is not honored
> --
>
> Key: YARN-2016
> URL: https://issues.apache.org/jira/browse/YARN-2016
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
>Affects Versions: 2.4.0
>Reporter: Venkat Ranganathan
>Assignee: Junping Du
> Attachments: YARN-2016.patch, YarnTest.java
>
>
> When we query for the previous applications by creating an instance of
> GetApplicationsRequest and setting the start time range and application tag,
> we see that the start range provided is not honored and all applications with
> the tag are returned
> Attaching a reproducer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995361#comment-13995361 ] Jian He commented on YARN-2016: --- Adding unit tests for all records would be another big effort. Junping, you can open a new jira to discuss about this if needed. Committing this. > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994757#comment-13994757 ] Junping Du commented on YARN-2016: -- Thoughts? > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994756#comment-13994756 ] Junping Du commented on YARN-2016: -- Thanks [~jianhe] for review and comments. This is not the first time I saw the similar mistake happens in PB implementation so I am sure this is not the last time. I suggest we add more unit tests for existing PB implementation and make sure any changes on PB implementation has unit test to make sure it works. > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994740#comment-13994740 ] Jian He commented on YARN-2016: --- Thanks Junping for the patch ! LGTM, +1 I'm surprised that we missed these fields in the PB implementation. We should be careful when we work on PB patches give that mostly we don't have tests for the PB changes. > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Attachments: YARN-2016.patch, YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988449#comment-13988449 ] Junping Du commented on YARN-2016: -- The start time range (and other properties) is not merged from local to proto in PBImpl of getApplicationRequest. Will deliver a patch to fix it soon. > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan >Assignee: Junping Du > Attachments: YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored
[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987922#comment-13987922 ] Venkat Ranganathan commented on YARN-2016: -- I have briefly discussed this with [~vinodkv] and [~djp] has an idea on the fix > Yarn getApplicationRequest start time range is not honored > -- > > Key: YARN-2016 > URL: https://issues.apache.org/jira/browse/YARN-2016 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager >Affects Versions: 2.4.0 >Reporter: Venkat Ranganathan > Attachments: YarnTest.java > > > When we query for the previous applications by creating an instance of > GetApplicationsRequest and setting the start time range and application tag, > we see that the start range provided is not honored and all applications with > the tag are returned > Attaching a reproducer. -- This message was sent by Atlassian JIRA (v6.2#6252)
