From dev-return-30563-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Thu Feb 1 02:48:29 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 7DC2B180662 for ; Thu, 1 Feb 2018 02:48:29 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6DFD7160C56; Thu, 1 Feb 2018 01:48:29 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B678F160C42 for ; Thu, 1 Feb 2018 02:48:28 +0100 (CET) Received: (qmail 34589 invoked by uid 500); 1 Feb 2018 01:48:27 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 34578 invoked by uid 99); 1 Feb 2018 01:48:27 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2018 01:48:27 +0000 Received: from mail-qk0-f181.google.com (mail-qk0-f181.google.com [209.85.220.181]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 5E1881A00D0 for ; Thu, 1 Feb 2018 01:48:27 +0000 (UTC) Received: by mail-qk0-f181.google.com with SMTP id y80so17434207qkb.4 for ; Wed, 31 Jan 2018 17:48:27 -0800 (PST) X-Gm-Message-State: AKwxytcTlnF/sHyXVToifihOD5BcXIA+kHtC0VSFiAMbrXapgJpPXCSn xLe8Tw8AS6wvIr/GQXJwo95Yh92f3gkTFNcq22LWpw== X-Google-Smtp-Source: AH8x226XaEygEqki8wanGEWNSBQlJEKfCOhTrp9HsMAhOVMfLJGxeipflxdnfV5L+jHvXpfr5ryjgDaalzak5ZSVyec= X-Received: by 10.55.108.199 with SMTP id h190mr38588087qkc.78.1517449706484; Wed, 31 Jan 2018 17:48:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.39.234 with HTTP; Wed, 31 Jan 2018 17:47:46 -0800 (PST) In-Reply-To: <6D7C3C0D-02BC-4EBA-B8F7-7369D506D58D@apache.org> References: <1512149945757-0.post@n6.nabble.com> <1512443929840-0.post@n6.nabble.com> <1516046557911-0.post@n6.nabble.com> <6D7C3C0D-02BC-4EBA-B8F7-7369D506D58D@apache.org> From: Dmitriy Setrakyan Date: Wed, 31 Jan 2018 17:47:46 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Fwd: Semaphore Stuck when no acquirers to assign permit To: dev@ignite.apache.org Cc: Timay , Vladisav Jelisavcic Content-Type: multipart/alternative; boundary="001a11487604b84c4c05641cca33" --001a11487604b84c4c05641cca33 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Tim, Vlad, Any update on this ticket? I looked inside, but cannot understand the status. Thanks, D. ---------- Forwarded message ---------- From: Denis Magda Date: Fri, Jan 19, 2018 at 9:14 PM Subject: Re: Semaphore Stuck when no acquirers to assign permit To: user@ignite.apache.org, dev@ignite.apache.org Igniters, Who can check out Tim=E2=80=99s fix for the semaphore? pull request: https://github.com/apache/ignite/pull/3138 < https://github.com/apache/ignite/pull/3138> jira: https://issues.apache.org/jira/browse/IGNITE-7090 < https://issues.apache.org/jira/browse/IGNITE-7090> =E2=80=94 Denis > On Jan 15, 2018, at 12:02 PM, Timay wrote: > > I saw a release date set for 2.4 but have not had any feedback on the jira so > i wanted to check in on this. Can this make it into the 2.4 release? > > Thanks > Tim > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ --001a11487604b84c4c05641cca33--