From roundup-admin at psf.upfronthosting.co.za  Thu Oct  3 20:29:21 2013
From: roundup-admin at psf.upfronthosting.co.za (Python tracker)
Date: Thu, 03 Oct 2013 18:29:21 +0000
Subject: [Tracker-discuss] Failed issue tracker submission
Message-ID: <20131003182921.02DB2560CB@psf.upfronthosting.co.za>



The node specified by the designator in the subject of your message
("19951") does not exist.

Subject was: "[issue19951]"



Mail Gateway Help
=================
Incoming messages are examined for multiple parts:
 . In a multipart/mixed message or part, each subpart is extracted and
   examined. The text/plain subparts are assembled to form the textual
   body of the message, to be stored in the file associated with a "msg"
   class node. Any parts of other types are each stored in separate files
   and given "file" class nodes that are linked to the "msg" node.
 . In a multipart/alternative message or part, we look for a text/plain
   subpart and ignore the other parts.
 . A message/rfc822 is treated similar tomultipart/mixed (except for
   special handling of the first text part) if unpack_rfc822 is set in
   the mailgw config section.

Summary
-------
The "summary" property on message nodes is taken from the first non-quoting
section in the message body. The message body is divided into sections by
blank lines. Sections where the second and all subsequent lines begin with
a ">" or "|" character are considered "quoting sections". The first line of
the first non-quoting section becomes the summary of the message.

Addresses
---------
All of the addresses in the To: and Cc: headers of the incoming message are
looked up among the user nodes, and the corresponding users are placed in
the "recipients" property on the new "msg" node. The address in the From:
header similarly determines the "author" property of the new "msg"
node. The default handling for addresses that don't have corresponding
users is to create new users with no passwords and a username equal to the
address. (The web interface does not permit logins for users with no
passwords.) If we prefer to reject mail from outside sources, we can simply
register an auditor on the "user" class that prevents the creation of user
nodes with no passwords.

Actions
-------
The subject line of the incoming message is examined to determine whether
the message is an attempt to create a new item or to discuss an existing
item. A designator enclosed in square brackets is sought as the first thing
on the subject line (after skipping any "Fwd:" or "Re:" prefixes).

If an item designator (class name and id number) is found there, the newly
created "msg" node is added to the "messages" property for that item, and
any new "file" nodes are added to the "files" property for the item.

If just an item class name is found there, we attempt to create a new item
of that class with its "messages" property initialized to contain the new
"msg" node and its "files" property initialized to contain any new "file"
nodes.

Triggers
--------
Both cases may trigger detectors (in the first case we are calling the
set() method to add the message to the item's spool; in the second case we
are calling the create() method to create a new node). If an auditor raises
an exception, the original message is bounced back to the sender with the
explanatory message given in the exception.
-------------- next part --------------
Return-Path: <tracker-discuss at python.org>
X-Original-To: report at bugs.python.org
Delivered-To: roundup+tracker at 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 B9D6B560C9
	for <report at bugs.python.org>; Thu,  3 Oct 2013 20:29:20 +0200 (CEST)
Received: from albatross.python.org (localhost [127.0.0.1])
	by mail.python.org (Postfix) with ESMTP id 3crN683Px4z7LjM
	for <report at bugs.python.org>; Thu,  3 Oct 2013 20:29:20 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901;
	t=1380824960; bh=CLeKahvH0Lz0ah1N11RAumMj6FWK5rbMkYAZ1oOtMW4=;
	h=From:To:Subject:Date:From;
	b=lszFkNxHJ/BfF52UdqDRJgBKNwdHgJuurM9lXT4HGFybpm6dBCKRuWhL6cyTbzy11
	 7WyfThoKZXxGZ+Uc2SlVvPBK2yY6srYdkfpKnW5NXsKKCiFUnaMc8egIgCmyhSE8zz
	 3l1N+YVr+9OQcX2MPPVrqF5KbutVSRr9HfX2wYPo=
Received: from localhost (HELO mail.python.org) (127.0.0.1)
  by albatross.python.org with SMTP; 03 Oct 2013 20:29:20 +0200
Received: from virt-7yvsjn.psf.osuosl.org (unknown [140.211.10.72])
	by mail.python.org (Postfix) with ESMTP
	for <report at bugs.python.org>; Thu,  3 Oct 2013 20:29:19 +0200 (CEST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
From: tracker-discuss at python.org
To: report at bugs.python.org
Subject: [issue19951]
Message-Id: <3crN683Px4z7LjM at mail.python.org>
Date: Thu,  3 Oct 2013 20:29:20 +0200 (CEST)

TmV3IGNoYW5nZXNldCAxNTJmNzIzNTY2NzAgYnkgRXJpYyBTbm93IGluIGJyYW5jaCAnZGVmYXVs
dCc6Cltpc3N1ZTE5OTUxXSBGaXggZG9jc3RyaW5nIGFuZCB1c2Ugb2YgX2dldF9zdXBwcG9ydGVk
X2ZpbGVfbG9hZGVycygpIHRvIHJlZmxlY3QgMi10dXBsZXMuCmh0dHA6Ly9oZy5weXRob24ub3Jn
L2NweXRob24vcmV2LzE1MmY3MjM1NjY3MAo=

From metatracker at psf.upfronthosting.co.za  Sat Oct 12 14:41:17 2013
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Sat, 12 Oct 2013 12:41:17 +0000
Subject: [Tracker-discuss] [issue528] bugs.python.org unreachable with IPv6
Message-ID: <1381581677.85.0.785078690339.issue528@psf.upfronthosting.co.za>


New submission from Antoine Pitrou:

Lately bugs.python.org has become unreachable if your connection supports IPv6:

$ curl -vI http://bugs.python.org
* About to connect() to bugs.python.org port 80 (#0)
*   Trying 2a01:4f8:131:2480::3...
^C


It works fine if you force IPv4 instead:

$ curl -vI -4 http://bugs.python.org
* About to connect() to bugs.python.org port 80 (#0)
*   Trying 46.4.197.70...
* connected
* Connected to bugs.python.org (46.4.197.70) port 80 (#0)
> HEAD / HTTP/1.1
> User-Agent: curl/7.26.0
> Host: bugs.python.org
> Accept: */*
> 
* additional stuff not fine transfer.c:1037: 0 0
* HTTP 1.1 or later with persistent connection, pipelining supported
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Sat, 12 Oct 2013 12:38:59 GMT
Date: Sat, 12 Oct 2013 12:38:59 GMT
< Server: BaseHTTP/0.3 Python/2.6.6
Server: BaseHTTP/0.3 Python/2.6.6
< Expires: Sat, 12 Oct 2013 12:38:58 GMT
Expires: Sat, 12 Oct 2013 12:38:58 GMT
< Content-Type: text/html; charset=utf-8
Content-Type: text/html; charset=utf-8
< Cache-Control: no-cache
Cache-Control: no-cache
< Via: 1.1 bugs.python.org
Via: 1.1 bugs.python.org
* no chunk, no close, no size. Assume close to signal end

< 
* Closing connection #0

----------
messages: 2789
nosy: loewis, pitrou
priority: critical
status: unread
title: bugs.python.org unreachable with IPv6

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue528>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Oct 12 14:50:59 2013
From: metatracker at psf.upfronthosting.co.za (Antoine Pitrou)
Date: Sat, 12 Oct 2013 12:50:59 +0000
Subject: [Tracker-discuss] [issue528] bugs.python.org unreachable with IPv6
In-Reply-To: <1381581677.85.0.785078690339.issue528@psf.upfronthosting.co.za>
Message-ID: <1381582259.5.0.747625277448.issue528@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

$ traceroute bugs.python.org
traceroute to bugs.python.org (46.4.197.70), 30 hops max, 60 byte packets
 1  93.184.35.125 (93.184.35.125)  0.417 ms  0.594 ms  0.583 ms
 2  xe0-0-1-133.edg-sde-3.nerim.net (194.79.129.45)  0.391 ms  0.379 ms  0.533 ms
 3  te2-3-136.bbn-sde-2.nerim.net (194.79.129.2)  10.522 ms  10.812 ms  10.796 ms
 4  te2-2-94.bbn-vtr-1.nerim.net (194.79.131.89)  10.777 ms  10.773 ms  10.999 ms
 5  te2-4-20.bbn-vtr-2.nerim.net (194.79.131.138)  10.737 ms  10.969 ms  10.960 ms
 6  xe0-0-0-520.mpr-sbg-1.nerim.net (194.79.129.90)  10.682 ms  10.594 ms  10.591 ms
 7  xe0-0-3.mpr-fra-1.nerim.net (80.81.193.39)  10.570 ms  10.449 ms  10.441 ms
 8  * * *
 9  core1.hetzner.de (213.239.245.6)  11.437 ms *  11.432 ms
10  core22.hetzner.de (213.239.245.178)  16.399 ms  16.007 ms  16.380 ms
11  juniper2.rz13.hetzner.de (213.239.245.122)  16.353 ms  16.343 ms  15.729 ms
12  hos-tr3.ex3k12.rz13.hetzner.de (213.239.224.77)  16.956 ms  16.611 ms hos-tr4.ex3k12.rz13.hetzner.de (213.239.224.109)  16.591 ms
13  * * *
14  * * *

[etc.]

$ traceroute6 bugs.python.org
traceroute to bugs.python.org (2a01:4f8:131:2480::3), 30 hops max, 80 byte packets
 1  * * *
 2  2001:7a8:1:133::1 (2001:7a8:1:133::1)  2.111 ms * *
 3  te2-2-71.bbn-sde-1.nerim.net (::ffff:194.79.133.1)  8.781 ms  9.153 ms  9.141 ms
 4  te2-2-95.bbn-cbe-2.nerim.net (::ffff:194.79.131.86)  9.113 ms  9.105 ms  9.293 ms
 5  linx.ipv6.nerim.net (2001:7f8:4::3389:1)  9.068 ms  9.043 ms  9.232 ms
 6  2001:7f8:4::32e6:1 (2001:7f8:4::32e6:1)  20.083 ms  14.614 ms  12.722 ms
 7  r1nue1.core.init7.net (2001:1620:2::96)  27.711 ms  27.690 ms  27.668 ms
 8  gw-hetzner.init7.net (2001:1620:1000::1aa)  27.631 ms  27.633 ms  27.622 ms
 9  core12.hetzner.de (2a01:4f8:0:3::25)  27.523 ms  27.509 ms  27.490 ms
10  core21.hetzner.de (2a01:4f8:0:3::1a)  30.008 ms  29.990 ms  30.095 ms
11  core22.hetzner.de (2a01:4f8:0:3::a2)  30.424 ms  30.422 ms  30.405 ms
12  juniper2.rz13.hetzner.de (2a01:4f8:0:3::7a)  30.376 ms  30.359 ms  30.351 ms
13  * * *
14  * * *

[etc.]

----------
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue528>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Oct 25 19:12:38 2013
From: metatracker at psf.upfronthosting.co.za (Dustin Oprea)
Date: Fri, 25 Oct 2013 17:12:38 +0000
Subject: [Tracker-discuss] [issue529] Bugs Login Broken Under Chrome
Message-ID: <1382721158.03.0.223486564986.issue529@psf.upfronthosting.co.za>


New submission from Dustin Oprea:

When I try to log-in on bugs.python.org using Chrome (28), the browser does a post, and presents a "broken form: multiple @action values submitted" banner. No other content shows.

It works fine under Firefox. I'd submit a bug, but the normal Python bug tracker doesn't seem to have a website-related category. Is there a place that I can report the bug?




Dustin Oprea

----------
messages: 2791
nosy: dsoprea
priority: critical
status: unread
title: Bugs Login Broken Under Chrome

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue529>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Oct 25 19:49:28 2013
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Fri, 25 Oct 2013 17:49:28 +0000
Subject: [Tracker-discuss] [issue529] Bugs Login Broken Under Chrome
In-Reply-To: <1382721158.03.0.223486564986.issue529@psf.upfronthosting.co.za>
Message-ID: <1382723368.5.0.909171288723.issue529@psf.upfronthosting.co.za>


R David Murray added the comment:

This is the correct tracker to report problems with the python bug tracker.

The issue you report is a known issue, but has nothing to do with chrome.  It has to do with what page you start on when you submit the login form.

See issue 448 for more information.

----------
nosy: +r.david.murray
priority: critical -> bug
status: unread -> resolved
superseder: +Cannot log into search results page

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue529>
_______________________________________________________