Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id BF0A7200BC2 for ; Thu, 17 Nov 2016 08:30:36 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id BD553160B0B; Thu, 17 Nov 2016 07:30:36 +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 12AD4160AFF for ; Thu, 17 Nov 2016 08:30:35 +0100 (CET) Received: (qmail 49638 invoked by uid 500); 17 Nov 2016 07:30:34 -0000 Mailing-List: contact dev-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@spark.apache.org Received: (qmail 49628 invoked by uid 99); 17 Nov 2016 07:30:34 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Nov 2016 07:30:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D94BBC0FD4 for ; Thu, 17 Nov 2016 07:30:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.781 X-Spam-Level: * X-Spam-Status: No, score=1.781 tagged_above=-999 required=6.31 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Kh6ixPpTAyDn for ; Thu, 17 Nov 2016 07:30:31 +0000 (UTC) Received: from mail-it0-f44.google.com (mail-it0-f44.google.com [209.85.214.44]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 819775F297 for ; Thu, 17 Nov 2016 07:30:30 +0000 (UTC) Received: by mail-it0-f44.google.com with SMTP id l8so119723776iti.1 for ; Wed, 16 Nov 2016 23:30:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=kRb68URcaxQlZP+gkpzutBrBNA9E0aH2N9+gfiLMn3g=; b=ZalIEDTVhBqOSHbHgEJMic/auA9hIkC4UqZD7+ivRBGqZjU4Kt8pKsagYTGRUvXq92 GJ2numQfnCR6cgX9K0VzDeJzJQXIjq7ZOMkiMZFXge559A789TCXbh3kbrROGMmXRCTm p30e83Sqm7n1mMQ2KMcoVDSw/8ZX7A/bfiU/zCe6qaJg+61w/8qZccSFNIHOt7PpJzpV b+GepKVLycUlzrevite5R6FkKY+hRn/DOdrh7iWRUADLUmbEivd0rgRAa9lKA9PiY+Tu K4IUFTw6IJ417J7dOF+mXbCP67qy6mD+rrQ1d8G8RmuOXPCUovtIbTWN66Y8lucDO38G w4bA== X-Gm-Message-State: AKaTC007uF8dTvE3RfnREPt+n3ObiI43j4Mb3BR2v0+gW+ry3+ahG57Y/L8yanzqtU6mUISZehwjrSnu+CtWYw== X-Received: by 10.202.5.5 with SMTP id 5mr621665oif.157.1479367829311; Wed, 16 Nov 2016 23:30:29 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Holden Karau Date: Thu, 17 Nov 2016 07:30:18 +0000 Message-ID: Subject: Re: issues with github pull request notification emails missing To: Reynold Xin , "dev@spark.apache.org" Content-Type: multipart/alternative; boundary=94eb2c18d080f5587005417a292b archived-at: Thu, 17 Nov 2016 07:30:36 -0000 --94eb2c18d080f5587005417a292b Content-Type: text/plain; charset=UTF-8 +1 it seems like I'm missing a number of my GitHub email notifications lately (although since I run my own mail server and forward I've been assuming it's my own fault). I've also had issues with having greatly delayed notifications on some of my own pull requests but that might be unrelated. On Thu, Nov 17, 2016 at 8:20 AM Reynold Xin wrote: > I've noticed that a lot of github pull request notifications no longer > come to my inbox. In the past I'd get an email for every reply to a pull > request that I subscribed to (i.e. commented on). Lately I noticed for a > lot of them I didn't get any emails, but if I opened the pull requests > directly on github, I'd see the new replies. I've looked at spam folder and > none of the missing notifications are there. So it's either github not > sending the notifications, or the emails are lost in transit. > > The way it manifests is that I often comment on a pull request, and then I > don't know whether the contributor (author) has updated it or not. From the > contributor's point of view, it looks like I've been ignoring the pull > request. > > I think this started happening when github switched over to the new code > review mode ( > https://github.com/blog/2256-a-whole-new-github-universe-announcing-new-tools-forums-and-features > ) > > > Did anybody else notice this issue? > > > --94eb2c18d080f5587005417a292b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
+1 it seems like I'm missing a numb= er of my GitHub email notifications lately (although since I run my own mai= l server and forward I've been assuming it's my own fault).

=
I've also had issues with having greatly delayed notifications on s= ome of my own pull requests but that might be unrelated.

On Thu, Nov 17, 2016 at 8:20 AM Reynold = Xin <rxin@databricks.com> = wrote:
I've noticed that a lot of github pull request notifications n= o longer come to my inbox. In the past I'd get an email for every reply= to a pull request that I subscribed to (i.e. commented on). Lately I notic= ed for a lot of them I didn't get any emails, but if I opened the pull = requests directly on github, I'd see the new replies. I've looked a= t spam folder and none of the missing notifications are there. So it's = either github not sending the notifications, or the emails are lost in tran= sit.

The way it manifests is that I often comment on a pull request, an= d then I don't know whether the contributor (author) has updated it or = not. From the contributor's point of view, it looks like I've been = ignoring the pull request.
=
I think this started= happening when github switched over to the new code review mode (=C2=A0https= ://github.com/blog/2256-a-whole-new-github-universe-announcing-new-tools-fo= rums-and-features )


Did anybody else notice this issue?


--94eb2c18d080f5587005417a292b--