About issue 1661

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

About issue 1661

李玉珏@163
Hi:

https://issues.apache.org/jira/browse/IGNITE-1661?filter=-2.

The issue is china's developer found, but the community has no feedback.
Today, the issue reporter asked me, but I can't answer.
I would like to ask, does anyone know what the issue is? Are developers
using incorrect? If it is bug, when can fix it?

Reply | Threaded
Open this post in threaded view
|

Re: About issue 1661

Denis Magda
Hi,

Don't hesitate to reaching out community over @dev or @user list if
there is no feedback in some JIRA ticket.

Alex G., is this issue somehow related to the task you're working on
https://issues.apache.org/jira/browse/IGNITE-2610

On 2/17/2016 4:23 PM, 李玉珏@163 wrote:
> Hi:
>
> https://issues.apache.org/jira/browse/IGNITE-1661?filter=-2.
>
> The issue is china's developer found, but the community has no feedback.
> Today, the issue reporter asked me, but I can't answer.
> I would like to ask, does anyone know what the issue is? Are
> developers using incorrect? If it is bug, when can fix it?
>

Reply | Threaded
Open this post in threaded view
|

Re: About issue 1661

Alexey Goncharuk
Yes, from the description it looks related to IGNITE-2610. I will check the
test attached to the IGNITE-1661 once I finish the fix for IGNITE-2610.
Reply | Threaded
Open this post in threaded view
|

Re: About issue 1661

dsetrakyan
I linked IGNITE-2610 and IGNITE-1661 in Jira. Let’s process them together.

On Wed, Feb 17, 2016 at 12:58 PM, Alexey Goncharuk <
[hidden email]> wrote:

> Yes, from the description it looks related to IGNITE-2610. I will check the
> test attached to the IGNITE-1661 once I finish the fix for IGNITE-2610.
>
Reply | Threaded
Open this post in threaded view
|

Re: About issue 1661

李玉珏@163
Hi:

Thanks!

在 16/2/18 06:29, Dmitriy Setrakyan 写道:
> I linked IGNITE-2610 and IGNITE-1661 in Jira. Let’s process them together.
>
> On Wed, Feb 17, 2016 at 12:58 PM, Alexey Goncharuk <
> [hidden email]> wrote:
>
>> Yes, from the description it looks related to IGNITE-2610. I will check the
>> test attached to the IGNITE-1661 once I finish the fix for IGNITE-2610.
>>


Reply | Threaded
Open this post in threaded view
|

Re: About issue 1661

Alexey Goncharuk
Hi,

I have merged the changes fixing IGNITE-2610 and verified the test in
IGNITE-1661. Please verify and close the ticket if all is ok.
Reply | Threaded
Open this post in threaded view
|

Re: About issue 1661

dsetrakyan
Alexey, can this be verified in master?

On Thu, Feb 18, 2016 at 7:47 AM, Alexey Goncharuk <
[hidden email]> wrote:

> Hi,
>
> I have merged the changes fixing IGNITE-2610 and verified the test in
> IGNITE-1661. Please verify and close the ticket if all is ok.
>
Reply | Threaded
Open this post in threaded view
|

Re: About issue 1661

Alexey Goncharuk
Yes, the fix has been merged to master.
On Feb 18, 2016 22:06, "Dmitriy Setrakyan" <[hidden email]> wrote:

> Alexey, can this be verified in master?
>
> On Thu, Feb 18, 2016 at 7:47 AM, Alexey Goncharuk <
> [hidden email]> wrote:
>
> > Hi,
> >
> > I have merged the changes fixing IGNITE-2610 and verified the test in
> > IGNITE-1661. Please verify and close the ticket if all is ok.
> >
>