R David Murray added the comment:
As I noted on the other issue, this is the wrong place to report planetpython
issues.
--
nosy: +r.david.murray
priority: bug -> wish
status: unread -> resolved
___
PSF Meta Tracker
R David Murray added the comment:
The tracker is not planetpython. Probably the right people to contact about
this (or at least a good place to start) is the infrastructure team.
--
nosy: +r.david.murray
priority: feature -> wish
status: unread -> ch
R David Murray added the comment:
My understanding (and I thought experience, but I can't swear to it)
was that it was already prohibited. Maybe we broke something in our
recent changes to support the github workflow?
--
nosy: +r.david.murray
status: unread ->
R David Murray added the comment:
I would think that a PR should only ever apply to one issue (the others
should be closed or made dependencies), so I think this should be
limited to linking to the first issue mentioned
--David
--
nosy: +r.david.murray
R David Murray added the comment:
I don't know what about the submit changes button you are suggesting changing,
and I don't currently have a test instance set up to look at what the
difference is. It would be helpful if that change the triagers mark change
were separate chang
R David Murray added the comment:
Yes, there is a reason :) Someone comes to the tracker with a bug, and does a
good search...and with an open-only search doesn't find an issue, because we've
already fixed it but it isn't in the version of python they are running. But
the d
R David Murray added the comment:
I'm not sure what you mean by "be conservative". Leave the current tag alone
and add "easy (C)" and just apply it to the identified C issues? That would
actually make sense. We could also add a *new* 'easy (python)',
R David Murray added the comment:
Personally I rarely use 'search' (except for the canned searches I've made),
and almost always use the upper right search box. I would strongly object to
losing the upper right search box as it currently functions.
The "usual" way
R David Murray added the comment:
So we change the current tag to 'easy (python)', and someone goes in and
changes any easy C issues to 'easy (C)'? I'm not sure how useful 'easy (doc)'
will be in reality, but we might as well have it for symmetry :)
As you
R David Murray added the comment:
We have since had the occasion to add Developer to a couple of people
specifically so they could be assigned issues (people Raymond is tutoring). So
IMO that field is working as desired at the current time. There's no
alternative to a thread on
R David Murray added the comment:
Well, we can edit the apache server config too. In fact, I thought I'd done
the diffie-hellman fix, but I guess I didn't.
I don't understand the 'cert expires' part, it was renewed in September of 2015.
Is there any reason we cou
R David Murray added the comment:
If we are going to do anything with the assigned to field, I think we should
just remove it. But if we don't remove it, I think having triagers in the
assignment list is fine. They are on a path to be a developer, so if they want
to use it I don'
R David Murray added the comment:
Grade: C.
That is pretty uninformative. Did I miss something?
--
nosy: +r.david.murray
status: unread -> chatting
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/is
R David Murray added the comment:
Maybe put the code in with a switch so we can turn it on and off? I'm pretty
sure we're going to want it, but not positive.
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/
R David Murray added the comment:
Yes, I was assuming we'd post to the right account when we can determine it.
It was only github accounts with no linkage where we'd need a 'generic' user
for posting. And we *will* get PRs from people who won't open bugs.python.org
R David Murray added the comment:
I anticipate that even if we improve our patch commit rate we'll still have
1000+ open PRs. I don't think pounding on github's infrastructure for every
page render on our bug tracker is very friendly, not to mention probably not
very perfor
R David Murray added the comment:
Hmm. Good question. We could use a specific user to create such issues.
As for noise...we do typo issues now, so if we have an increased volume of them
I think that just means we're fixing more typos. I don't really see the
problem with t
R David Murray added the comment:
And if the PR doesn't reference an issue number, it should create a new issue.
I think we should also look for issue numbers in the body of the PR as well.
The user might put it in the description rather than the title, if they provide
a descri
R David Murray added the comment:
Don't do lookups, do mechanical translation. The translation happens at page
rendering time, so if github changes it URLs (or we move to a different
provider), we just change the linkifier code to match.
--
nosy: +r.david.m
R David Murray added the comment:
If github batched the review comments, what we would want (what we've wanted
for a long time from reitveld) is a note posted to b.p.o that there *are*
review comments. But since github does *not* batch review comments, posting
every comment (espec
R David Murray added the comment:
But, really, this level of discussion should take place on the workflow mailing
list, not in the context of the patch.
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/issue
R David Murray added the comment:
Berker: I presume the point here is that this creates the field, and issue 589
fills it in automatically by having github call roundup when a PR is created.
I haven't looked at either patch closely enough to know if I'm right, but
that's what
R David Murray added the comment:
Looks OK to me (without testing it). You probably meant to write
'status_changed' twice in the assignment for status_close, though.
--
status: unread -> chatting
___
PSF Meta T
R David Murray added the comment:
By the way, the current edit screen we are using was submitted upstream but not
accepted because of this remaining bug, so if you fix this we should submit the
revised patch upstream.
___
PSF Meta Tracker
R David Murray added the comment:
Should be "would not solve" in that last sentence.
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/
R David Murray added the comment:
I misspoke. Looking at the edit screen again, the issue is the 'leave in/leave
out' versus 'delete', which is indeed retire. The complicating factor is: what
if you 'leave in' a public query that someone then retires? It is st
R David Murray added the comment:
If I remember correctly this problem is the result of an incomplete fix to an
earlier problem. As I remember it the problem is that if you don't delete the
query it still shows up even when retired. To keep the DB consistent, the
correct fix would
R David Murray added the comment:
This bug tracker is for reporting problems with bugs.python.org. Your post
belongs on bugs.python.org itself if anywhere, but it sounds like your problem
is really with your tk version or your window system. You might want to try
posting to the python-list
R David Murray added the comment:
That is correct, it is a tracker-wide setting, and the community has elected to
get the notifications. To make it a user setting would be a feature request
for the Roundup tracker; their tracker is at http://issues.roundup-tracker.org/
if you want to submit
R David Murray added the comment:
The disabling of ipv6 reported by mmangoba does not appear to have been
effective. On the advice of p@trick, I added 'inet_protocols=ipv4' to the
postfix config and restarted (around 15:28 Eastern) and that seems to have
worked. Serhiy was abl
R David Murray added the comment:
This should be reported to Roundup upstream. The fix should be simple (just
changing the csv dialect), so it doesn't really matter who develops the patch
as long as both upstream and we apply it :)
--
nosy: +r.david.murray
status: unread ->
R David Murray added the comment:
This is the bug tracker for issues with the python bug tracker. For problems
with third party software, you will need to find the bug tracker for that
software (pyodbc, in this case).
--
nosy: +r.david.murray
priority: bug -> wish
status: unr
R David Murray added the comment:
That has nothing to do with this issue. Nor do we do anything currently with
dmarc. There are other issues about roundup mail getting marked as spam, you
could repost your observations on one of those if you like.
--
nosy: +r.david.murray
R David Murray added the comment:
And you both have the power to undo it if you decide you don't like it :)
(bugs.python.org/component, in case you've forgotten).
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/
R David Murray added the comment:
Done.
--
nosy: +r.david.murray
status: unread -> resolved
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/is
R David Murray added the comment:
This is a bug tracker for reporting bugs with the main python bug tracker.
Please post your question to the python-list mailing list or stack overflow.
--
nosy: +r.david.murray
priority: bug -> wish
status: unread -> ch
R David Murray added the comment:
I'm glad you found a solution. Yes, it is true that if you use a virtual
environment then you must always use that virtual environment (one way or
another).
___
PSF Meta Tracker
R David Murray added the comment:
Actually, rereading your patch it looks like it does the right thing before the
patch. So if there's a bug in venv support somehow, that would be the thing to
report upstream.
___
PSF Meta Tracker
R David Murray added the comment:
Thanks for the suggestion, but this is an incorrect (insecure) change. The
correct change would be to use the "usual mechanisms" (and frankly I forget
what those are) to resolve the absolute path to the executable at install time
and use that.
And
R David Murray added the comment:
Since I have no need for the feature, not me :)
This wouldn't really belong in the issue search page anyway, unless someone
completely rewrote it. Instead you'd create a search template for msg, which
could list the issue the message is linked to
R David Murray added the comment:
Well, it *can* be searched on, its just that it is 'last activity date' because
it is really there to be sorted on.
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/
R David Murray added the comment:
Well, the correct fix would be to change the search template so that the form
says "last activity date".
That field is really there to be sorted on, not searched on.
--
nosy: +r.david.murray
status: unread -
R David Murray added the comment:
Mail is consistently sent from rep...@bugs.python.org, always from the same IP
address, 46.4.197.70. 46.4.197.70 resolves to bugs.python.org.
So, we are meeting the requirements set forth in the article you link. I've
asked about adding SPF records, wh
R David Murray added the comment:
This is the tracker for problems with the functioning of the bugs.python.org
tracker. python bugs should be reported to the bugs.python.org tracker itself,
not here.
--
nosy: +r.david.murray
priority: urgent -> wish
status: unread -> re
R David Murray added the comment:
Ah, this is a duplicate of issue 458, then.
--
status: chatting -> resolved
superseder: +editing "homepage" field is not possible
___
PSF Meta Tracker
<http://psf.upfronthosting.co
R David Murray added the comment:
Here is the traceback from the log. My guess would be that the problem is due
to the relatively recent (three months or so?) cross site scripting security
fixes, which are preventing the real error message (whatever it is) from
getting rendered.
10.0.0.1
R David Murray added the comment:
I've used plenty of web sites where the equivalent of 'no selection' was not a
valid choice (ie: you had to select something before the form would be accepted
for submission).
Your argument appears to be that once the issue has been created,
On Wed, 16 Jul 2014 23:57:25 +0900, "Stephen J. Turnbull"
wrote:
> For use, in the end it did pretty much nothing for XEmacs or Debian;
> that's why I stopped. *They* were pretty good about forwarding
> relevant bugs upstream, but very little came from my efforts -- and
> not because I wasn't di
On Tue, 15 Jul 2014 10:12:19 +0300, anatoly techtonik
wrote:
> If Roundup plugin system is reworked a bit, it is
> possible to make extensions to create and monitor
> upstream bugs (Debian). Maybe even exchange
> messages with it.
That would be downstream, and I'm not sure why we would want to d
R David Murray added the comment:
Did they copy the contents? Can we set up some sort of redirect
instead?
--
nosy: +r.david.murray
status: unread -> chatting
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundu
R David Murray added the comment:
Sounds good to me.
--
nosy: +r.david.murray
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/issue
New submission from R David Murray:
Apr 22 17:32:16 psf postfix/smtp[3647]: 2CDF8568E0:
to=, relay=mx4.hotmail.com[65.55.37.120]:25,
delay=0.66, delays=0.02/0/0.48/0.16, dsn=5.0.0, status=bounced (host
mx4.hotmail.com[65.55.37.120] said: 550 SC-001 (COL0-MC4-F23) Unfortunately,
messages from
In case you missed it on the other lists I posted it to, we're planning
on having discussions about our roundup/rietveld setup and how to improve
it on the new core-workflow mailing list:
https://mail.python.org/mailman/listinfo/core-workflow
I'm certainly hoping that we will get more people
New submission from R David Murray:
When Roundup detects that someone else has updated an issue, it tries to give
you a link to use to open the message in a new window so you can see what
changes were made to the metadata. After the XSS issues were fixed, this link
became escaped HTML and so
R David Murray added the comment:
When I search for 'human' in 'all text' leaving all the other fields at their
defaults, I get that issue among the 45 results returned. When I search from
the search box, I get 157 results, and 18104 is on the first page of results.
Th
R David Murray added the comment:
Delete is fixed, at least for most browsers. There are probably some where the
javascript I used won't work.
--
status: chatting -> resolved
___
PSF Meta Tracker
<http://psf.upfrontho
R David Murray added the comment:
Also fixed the public yes/no dropdown, which had yet a different bug :(.
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/issue
R David Murray added the comment:
The leave in/out dropdown is a different problem. I've fixed that one today.
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/
R David Murray added the comment:
I managed to make some time to look at this, and I believe I've fixed it. The
template loader method 'get' no longer exists, it is now 'load'. Changing the
call to 'load('user.openid') seems to have worked.
I haven&
New submission from R David Murray:
The traceback in the admin email looks like this:
Traceback (most recent call last):
File "/home/roundup/lib/python2.6/site-packages/roundup/cgi/client.py", line
463, in inner_main
html = self.handle_action()
File "/home/roundup/lib
On Mon, 06 Jan 2014 14:14:25 +0900, "Stephen J. Turnbull"
wrote:
> Benjamin Peterson writes:
>
> > Not sure if this is interesting.
>
> > 2. As soon as we submit the crafted URL, we get an alert box saying XSS.
> >URL:
> >
> >
> http://bugs.python.org/issue?%40columns=status&messag
R David Murray added the comment:
Before I saw Barry's message, I removed 2.6 from the list of versions via the
web interface (which retires it). It can be re-added (un-retired) though, if
we have consensus on that. (It is id '1', which someone will need to know if
they do th
R David Murray added the comment:
Technically it is possible to search for retired version, and the search form
could even be changed to support it. I'm not sure that it is worth it,
though...I don't know what purpose would be served by searching based on
version as opposed to sea
R David Murray added the comment:
murray@psf:~$ traceroute6 www.python.org
traceroute to www.python.org (2001:888:2000:d::a2), 30 hops max, 80 byte packets
1 2a01:4f8:131:2480::3 (2a01:4f8:131:2480::3) 3001.350 ms !H 3001.349 ms !H
3001.345 ms !H
R David Murray added the comment:
I've added izak and roche to nosy to see if we can get an answer about the any
network issue that might be involved.
--
nosy: +izak, r.david.murray, roche
___
PSF Meta Tracker
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
R David Murray added the comment:
I'm not sure what this submission is trying to say, but it doesn't seem to have
anything to do with a bug in the python bug tracker, which is the purpose of
this bug tracker. It sounds like you want to be communicating with the django
communi
R David Murray added the comment:
Looks like the meta-tracker also just got hit, in issue 195.
--
status: unread -> chatting
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/is
New submission from R David Murray:
Christian Heims reported on the infrastructure list that there was spam on
issue 12641 from "unknown users". I've done some poking around, and they
weren't created via openid. Presumably they were created the normal way
through t
R David Murray added the comment:
Here are the log records for emails sent to your address since July 21st at
06:25 CEST:
Jul 22 13:57:02 psf postfix/smtp[29578]: 8ED9A56A35: to=,
relay=gmail-smtp-in.l.google.com[2a00:1450:400c:c03::1a]:25, delay=0.67,
delays=0.01/0/0.06/0.6, dsn=2.0.0
R David Murray added the comment:
Because sorting is a generic interface. You'd have to add special code to deny
sorting by password. But as Martin says, it's not a security issue.
--
nosy: +r.david.murray
___
PSF Me
R David Murray added the comment:
If I understand you correctly, the only issue here is the XSS. The other
things are simply things a logged in user with appropriate privileges can
normally access?
I believe this issue should be reported upstream in the roundup tracker.
--
nosy
R David Murray added the comment:
Well, yes, I know that is common. Unfortunately, https doesn't solve that lack
of security knowledge, since if one account gets cracked because of insecure
servers, the rest of their accounts are also compro
R David Murray added the comment:
As Martin (I think) has said, just how damaging would compromising this
password be? Tracker changes are all reversible.
On the other hand I'm in favor of using https in general. This was discussed
on the infrastructure list, and the issue is that bu
R David Murray added the comment:
It looks like the function that does the splitting into words for
indexing/searching is:
re.findall(r'(?u)\b\w{2,25}\b', text)
which if I pass it '2.7.4' doesn't return any matches...that is, as usual for
text indexes punct
On Wed, 20 Mar 2013 10:26:19 +0300, anatoly techtonik
wrote:
> You're wrong. I did't even have a slight though about making Python take
> over another established product. I am speaking about the culture of eating
> your own dogfood and collaborating with upstream. Don't you think that
> changes
On Sun, 17 Mar 2013 02:56:12 +0300, anatoly techtonik
wrote:
> The major goal is to lower the barrier to let people start hacking at
> Roundup. The secondary goal it to I am not sure about the Python 3 porting,
> but currently b.p.o uses a patched version of Roundup, which is no good. If
> someth
New submission from R David Murray:
Now that we have an automated CLA system, it would be great if the resulting
email could also be sent to b.p.o, and a script update the 'contributor form
received' checkbox and date field. Obviously this requires cooperation from
the r
On Tue, 19 Feb 2013 18:17:07 +0100, =?ISO-8859-15?Q?=22Martin_v=2E_L=F6wis=22?=
wrote:
> Should that also be done for bugs.python.org? What do you think?
> (IIUC, we can figure out what users have changed there passwords
> from the roundup journals, so we would only reset them for those
> who did
On Wed, 13 Feb 2013 10:20:51 -0800, "fwierzbi...@gmail.com"
wrote:
> Proposal: Jython to use the same tracker as CPython
I think you should send this to the python-committers mailing list,
and probably then to python-dev assuming it passes muster on
committers :)
I have no objection myself.
--
R David Murray added the comment:
This is the issue tracker for the python.org issue trackers (the
"metatracker"). jython's issue tracker is at bugs.jython.org. However, your
question isn't really appropriate for an issue tracker, you are better off
posting it to the
On Sun, 25 Nov 2012 16:07:56 +0200, Ezio Melotti wrote:
> On Sun, Nov 25, 2012 at 3:30 PM, anatoly techtonik wrote:
>
> > On Sun, Nov 25, 2012 at 1:56 AM, Ezio Melotti wrote:
> >
> >> On Sun, Nov 25, 2012 at 12:24 AM, anatoly techtonik
> >> wrote:
> >>
> >>> On Sat, Nov 24, 2012 at 7:04 AM, Ezio
R David Murray added the comment:
Yes, sorry, I was explaining the constraints but I didn't express that well.
Note that the *only* time such messages are sent anywhere other than to the
submitter and the roundup-admin (that no one has time to fully track) is when
they come from the
R David Murray added the comment:
The problem with that suggestion is that this is just the message template that
is used when an email submission fails. So if a user did a reply to a tracker
message, and their reply failed for some reason, they would get a message that
said "this messa
On Fri, 16 Nov 2012 08:50:22 +0200, Ezio Melotti wrote:
> Hi,
> the message you saw was caused by a problem with the new irker detector --
> it should be fixed now.
> For the record the message you received says:
> """
> New changeset a2b54b6d9759 by Mark Dickinson in branch 'default':
> Issue #16
R David Murray added the comment:
Yes, 10 lines. It happens in mailgw.py in the parseContent routine:
elif signature.match(lines[0]) and 2 <= len(lines) <= 10:
# lose any signature
break
that would also be the routine to modify if one wanted to improve the algorith
R David Murray added the comment:
If the contributor icon is not added, I think removing the contrib form
received marker would be good. As it is, one is fooled into expecting both
icons should be there when appropriate, and might mistakenly think someone is
not a committer because the
R David Murray added the comment:
This is probably a duplicate of issue 448.
--
nosy: +r.david.murray
status: unread -> chatting
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/is
New submission from R David Murray:
I tried to remove Colin Winter's UID from the 'assign-to' field for component,
but when I clicked save I got the red-bar error message 'No such action
"editcsv"'
--
messages: 2565
nosy: r.david.murray
priority: bu
On Sun, 15 Jul 2012 14:38:20 -0700, Chris Jerdonek
wrote:
> What is the right resolution status when closing an issue that was
> originally valid but later fixed indirectly by another issue? Fixed, out
> of date, or duplicate (and putting the other issue in the Superseder)?
I'd go with duplicat
R David Murray added the comment:
Yeah, I didn't look in the docs, I did 'grep -r python-bugs' trackers/tracker'
in the roundup directory :)
___
PSF Meta Tracker
<http://psf.upfronthosting.co.z
R David Murray added the comment:
If I'm reading this right, we just need to add
'busybody_email=some-email-address' to the detectors/config.ini for the jython
tracker instance. So that could just be your address, if you don't want a full
blown mailing list that oth
R David Murray added the comment:
Well, since we have an email list for the CPython tracker that gets all
activity, there must be a way to do it. It probably involves a reactor for the
tracker instance. You'll need to get Barry or someone involved to set up the
mailing
R David Murray added the comment:
I use unique passwords for all services for exactly this reason so I, for one,
am not worried.
--
nosy: +r.david.murray
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/issue
New submission from R David Murray :
I would like to add a new classification, 'email', (on which I would be
auto-nosy). My motivation for this is that I don't like having all the email
issues assigned to me when I obviously can't be actively working on all of
them. I&#
R David Murray added the comment:
Oh, I hate web sites that don't take me back to exactly the page I was on after
I log in. -1 on that proposal. We could strip @action's from the URL, though,
that would make sense.
--
nosy: +r.da
R David Murray added the comment:
Fixed in r88947. The xapian find function was only returning the first 10
results, and many of *those* got filtered out because they were inside file
objects, which we don't include in search results by default.
Interestingly, although we host the rou
New submission from R David Murray :
I propose to alter the weekly roundup-summary email by breaking down the 'open'
category in the header issue summary into the subcategories 'enhancements' and
'bugs'. The idea is that you get what you measure, and if we se
New submission from R David Murray :
With the OS upgrade, the bug tracker is now using Roundup's xapian support for
full text searches. However, this does not appear to be returning complete
results. One example: searching on 'strftime' returns issues 6641, 3091, 2782,
a
R David Murray added the comment:
Sorry, I thought the title made the same bug appropriate, but you are right,
since it is a different problem it should be a different bug. I'll close this
one and open a new one (I have a bit more info to add).
--
status: chatting ->
1 - 100 of 135 matches
Mail list logo
