Failed issue tracker submission
An unexpected error occurred during the processing of your message. The tracker administrator is being notified. Return-Path: <python-dev@python.org> X-Original-To: report@bugs.python.org Delivered-To: roundup+tracker@psf.upfronthosting.co.za Received: from mail.python.org (mail.python.org [82.94.164.166]) by psf.upfronthosting.co.za (Postfix) with ESMTPS id 833861CBB0 for <report@bugs.python.org>; Fri, 20 Apr 2012 19:00:09 +0200 (CEST) Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3VZ3GK10QGzN51 for <report@bugs.python.org>; Fri, 20 Apr 2012 19:00:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901; t=1334941209; bh=PuPHOLI7fb95kba5/ecLxSLCC9UpM27v8bYaw31epzE=; h=Date:Message-Id:Content-Type:MIME-Version: Content-Transfer-Encoding:From:To:Subject; b=ZfbTowau33LvKWnJHYtZ8Fy/cAslebBopL912urudimFDYNg5n7CHpPwxlMLlLTv5 tR2OZmCp3w90e6h937L7R6g7mew3xHaxeRbzP06cEK0JTyOQaekSKHBxivVMuU2hjL AE1J6MRlKrxJoqE8dQMyzP7+wM5o39unn76WD6bE= Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 20 Apr 2012 19:00:09 +0200 Received: from dinsdale.python.org (svn.python.org [IPv6:2001:888:2000:d::a4]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.python.org (Postfix) with ESMTPS for <report@bugs.python.org>; Fri, 20 Apr 2012 19:00:09 +0200 (CEST) Received: from localhost ([127.0.0.1] helo=dinsdale.python.org ident=hg) by dinsdale.python.org with esmtp (Exim 4.72) (envelope-from <python-dev@python.org>) id 1SLHBo-00063N-NT for report@bugs.python.org; Fri, 20 Apr 2012 19:00:08 +0200 Date: Fri, 20 Apr 2012 19:00:08 +0200 Message-Id: <E1SLHBo-00063N-NT@dinsdale.python.org> Content-Type: text/plain; charset="utf8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 From: python-dev@python.org To: report@bugs.python.org Subject: [issue14633] TmV3IGNoYW5nZXNldCBhMjgxYTY2MjI3MTQgYnkgQnJldHQgQ2Fubm9uIGluIGJyYW5jaCAnZGVm YXVsdCc6Cklzc3VlICMxNDYzMzogU2ltcGxpZnkgaW1wLmZpbmRfbW9kdWUoKSB0ZXN0IGFmdGVy IGZpeGVzIGZyb20gaXNzdWUKaHR0cDovL2hnLnB5dGhvbi5vcmcvY3B5dGhvbi9yZXYvYTI4MWE2 NjIyNzE0Cg==
I'm getting one of these every couple of days. What's the deal? On Apr 21, 2012 1:03 AM, "Python tracker" < roundup-admin@psf.upfronthosting.co.za> wrote:
An unexpected error occurred during the processing of your message. The tracker administrator is being notified.
Return-Path: <python-dev@python.org> X-Original-To: report@bugs.python.org Delivered-To: roundup+tracker@psf.upfronthosting.co.za Received: from mail.python.org (mail.python.org [82.94.164.166]) by psf.upfronthosting.co.za (Postfix) with ESMTPS id 833861CBB0 for <report@bugs.python.org>; Fri, 20 Apr 2012 19:00:09 +0200 (CEST) Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3VZ3GK10QGzN51 for <report@bugs.python.org>; Fri, 20 Apr 2012 19:00:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901; t=1334941209; bh=PuPHOLI7fb95kba5/ecLxSLCC9UpM27v8bYaw31epzE=; h=Date:Message-Id:Content-Type:MIME-Version: Content-Transfer-Encoding:From:To:Subject; b=ZfbTowau33LvKWnJHYtZ8Fy/cAslebBopL912urudimFDYNg5n7CHpPwxlMLlLTv5 tR2OZmCp3w90e6h937L7R6g7mew3xHaxeRbzP06cEK0JTyOQaekSKHBxivVMuU2hjL AE1J6MRlKrxJoqE8dQMyzP7+wM5o39unn76WD6bE= Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 20 Apr 2012 19:00:09 +0200 Received: from dinsdale.python.org (svn.python.org[IPv6:2001:888:2000:d::a4]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.python.org (Postfix) with ESMTPS for <report@bugs.python.org>; Fri, 20 Apr 2012 19:00:09 +0200 (CEST) Received: from localhost ([127.0.0.1] helo=dinsdale.python.org ident=hg) by dinsdale.python.org with esmtp (Exim 4.72) (envelope-from <python-dev@python.org>) id 1SLHBo-00063N-NT for report@bugs.python.org; Fri, 20 Apr 2012 19:00:08 +0200 Date: Fri, 20 Apr 2012 19:00:08 +0200 Message-Id: <E1SLHBo-00063N-NT@dinsdale.python.org> Content-Type: text/plain; charset="utf8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 From: python-dev@python.org To: report@bugs.python.org Subject: [issue14633]
TmV3IGNoYW5nZXNldCBhMjgxYTY2MjI3MTQgYnkgQnJldHQgQ2Fubm9uIGluIGJyYW5jaCAnZGVm
YXVsdCc6Cklzc3VlICMxNDYzMzogU2ltcGxpZnkgaW1wLmZpbmRfbW9kdWUoKSB0ZXN0IGFmdGVy
IGZpeGVzIGZyb20gaXNzdWUKaHR0cDovL2hnLnB5dGhvbi5vcmcvY3B5dGhvbi9yZXYvYTI4MWE2 NjIyNzE0Cg==
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/anacrolix%40gmail.com
On Sat, 21 Apr 2012 08:54:56 +0800, Matt Joiner <anacrolix@gmail.com> wrote:
I'm getting one of these every couple of days. What's the deal? On Apr 21, 2012 1:03 AM, "Python tracker" < roundup-admin@psf.upfronthosting.co.za> wrote:
There is a bug in the interface between roundup and hg that is new since roundup was switched to using xapian for indexing. When an hg commit mentions more than one issue number, the second (or subsequent, presumably) issue number triggers a write conflict and results in the email doing the second issue update being rejected. Since the email address associated with the hg update email is python-dev, the bounce gets sent here. There are currently only three people who do maintenance work on the tracker (it used to be just one), and none of us have found time to try to figure out a fix yet. --David
Cheers On Apr 21, 2012 10:25 AM, "R. David Murray" <rdmurray@bitdance.com> wrote:
On Sat, 21 Apr 2012 08:54:56 +0800, Matt Joiner <anacrolix@gmail.com> wrote:
I'm getting one of these every couple of days. What's the deal? On Apr 21, 2012 1:03 AM, "Python tracker" < roundup-admin@psf.upfronthosting.co.za> wrote:
There is a bug in the interface between roundup and hg that is new since roundup was switched to using xapian for indexing. When an hg commit mentions more than one issue number, the second (or subsequent, presumably) issue number triggers a write conflict and results in the email doing the second issue update being rejected. Since the email address associated with the hg update email is python-dev, the bounce gets sent here.
There are currently only three people who do maintenance work on the tracker (it used to be just one), and none of us have found time to try to figure out a fix yet.
--David
participants (3)
-
Matt Joiner -
Python tracker -
R. David Murray