ng this mainly since I'm the only admin and the list isn't
> seemingly used anymore.
>
> On Tue, Jun 18, 2019 at 3:49 PM Brett Cannon wrote:
>>
>> They can be.
>>
>> On Mon, Jun 17, 2019 at 11:44 PM Ezio Melotti wrote:
>>>
>>> On Mon,
On Mon, Jun 17, 2019 at 10:59 PM Brett Cannon wrote:
>
> There hasn't been an email since December 2018 and I feel this list was
> primarily used for automatic emailing of issues for b.p.o which is now
> tracked on GitHub.
>
> If you disagree with shutting down this list, please speak up and sta
Ezio Melotti added the comment:
No problem, thanks for taking the time to report the issue.
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/issue
Ezio Melotti added the comment:
Reported upstream at http://issues.roundup-tracker.org/issue2551008
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/issue
Ezio Melotti added the comment:
Fixed in https://hg.python.org/tracker/roundup/rev/d7454b42b914
--
status: in-progress -> resolved
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/is
New submission from Ezio Melotti :
def _decode_header_to_utf8(self, hdr):
l = []
for part, encoding in decode_header(hdr):
if encoding:
part = part.decode(encoding)
l.append(part)
return ''.join([s.encode('utf-8
Ezio Melotti added the comment:
The correct place where to report this is https://bugs.python.org/
See also https://devguide.python.org/tracker/#reporting-an-issue for more
information.
--
assignedto: -> ezio.melotti
nosy: +ezio.melotti
status: chatting -> re
Ezio Melotti added the comment:
Have you tried adding the gmail account as primary?
I don't remember if mails are sent to all additional email addresses, or if
they are only used for other purposes (search, identifying users when they
reply via email, etc).
FWIW I haven't notice
Ezio Melotti added the comment:
Keep in mind that converting the repo to Git will make it more difficult to
upgrade, since our roundup is a clone of the main Roundup repo.
So, assuming this issue moves forward, we can either:
* start using official Roundup releases (this means no changes to
Ezio Melotti added the comment:
I applied this yesterday but it's sometimes failing with the following error:
File "extensions/pydevutils.py", line 26, in is_triager
return 'Developer' in db.user.get(userid, 'roles')
TypeError: argument of type &#x
Ezio Melotti added the comment:
Thanks for the report, but this is the meta-tracker. For issues about Python
you should use the bug tracker at https://bugs.python.org/
--
nosy: +ezio.melotti
status: unread -> resolved
___
PSF M
Ezio Melotti added the comment:
Fixed in https://hg.python.org/tracker/python-dev/rev/ebd8421bc9ac
Thanks for the report!
--
assignedto: -> ezio.melotti
nosy: +ezio.melotti
status: unread -> resolved
___
PSF Meta Tracker
Ezio Melotti added the comment:
See also https://hg.python.org/tracker/python-dev/rev/88d5e4654239 (the "show
issue" button wasn't working from the search result page).
___
PSF Meta Tracker
<http://psf.upfronthosting.
Ezio Melotti added the comment:
This is now fixed on all the instances:
python-dev: https://hg.python.org/tracker/python-dev/rev/81ad515ff72a
jython: https://hg.python.org/tracker/jython/rev/bbee7515875a
setuptools: https://hg.python.org/tracker/setuptools/rev/d1ff0055abbb
These changes only
Ezio Melotti added the comment:
This has been included in
https://hg.python.org/tracker/python-dev/rev/182a21789df5
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/issue
Ezio Melotti added the comment:
I reverted https://hg.python.org/tracker/python-dev/rev/4d80cbb989d2 and
https://hg.python.org/tracker/roundup/rev/200ba961cd49 since this was fixed
upstream.
--
nosy: +ezio.melotti
___
PSF Meta
Ezio Melotti added the comment:
See https://hg.python.org/tracker/python-dev/rev/dec273514fa7
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/issue
Ezio Melotti added the comment:
It looks like your CLA has been received yesterday.
You can verify this by clicking on "Your details" in the sidebar, or by
checking if there's a * next to your name in the messages on bugs.python.org.
--
assignedto: -> ezio.melotti
n
Ezio Melotti added the comment:
This can be fixed in the config by setting
subject_prefix_parsing/subject_suffix_parsing to loose instead of strict.
This should still accept valid tags, and ignore invalid ones.
--
nosy: +ezio.melotti
status: unread -> chatt
Ezio Melotti added the comment:
Done in https://hg.python.org/tracker/python-dev/rev/7d4942e1ce43
I used assertTrue because the code does something like closed = bool(...); if
closed: ..., but either one should be fine.
--
assignedto: -> ezio.melotti
status: in-progress -> re
Ezio Melotti added the comment:
Attached a patch that adds support for fix/fixes/fixed.
In order to test this we would currently need to create a file for each
variation, so I just tested directly against the regex. For the future, it
would be better to add to the tests a way to dynamically
Ezio Melotti added the comment:
Actually we just limited the number of issues a pr gets linked to, but still
check the body and link to additional issues: see issue625
If it's desirable to limit it further or allowing only one issue, we could fix
that.
--
nosy: +r.david.m
Ezio Melotti added the comment:
Maciej, didn't we fix this?
--
nosy: +ezio.melotti, maciej.szulik
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/
Ezio Melotti added the comment:
Your guess is right, and this is now fixed. If you find other links that are
using http on tracker please report them!
--
nosy: +ezio.melotti
status: unread -> resolved
___
PSF Meta Tracker
&l
Ezio Melotti added the comment:
What's the status on this?
--
nosy: +ezio.melotti
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/
Ezio Melotti added the comment:
This is now fixed thanks to R. David.
--
assignedto: -> r.david.murray
nosy: +ezio.melotti
status: chatting -> resolved
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta
Ezio Melotti added the comment:
If you hover with the mouse on the PR link in the PR list you will see the
title which includes e.g. [3.5].
Perhaps it would be better to just display the title in that list.
--
nosy: +ezio.melotti
status: unread -> chatt
Ezio Melotti added the comment:
> Maybe we broke something in our recent changes to support the github workflow?
I don't think we changed that part of the code, but perhaps we broke it when
the openid integration was added. IIRC I also saw a few user that have two
accounts, a regular
Ezio Melotti added the comment:
The patch is now live, closing.
--
status: testing -> resolved
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/is
Ezio Melotti added the comment:
(FWIW I've been also considering having a 1:1 match between PR numbers and
internal roundup ids for pull_requests, however this requires two step:
1) make sure that only one Roundup pull_request exists for each GitHub PR;
2) make sure that the PR number
Ezio Melotti added the comment:
I've been looking at the code and perhaps it can be done in
detectors/sendmail.py. I'll try to put together a patch sometimes next week.
--
assignedto: -> ezio.melotti
___
PSF Meta T
Ezio Melotti added the comment:
See https://github.com/python/core-workflow/issues/35
--
nosy: +ezio.melotti
status: unread -> chatting
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/is
Ezio Melotti added the comment:
Done in https://hg.python.org/tracker/python-dev/rev/64d04cffeca4
Thanks for the patch!
--
assignedto: -> ezio.melotti
status: unread -> resolved
___
PSF Meta Tracker
<http://psf.upfronthost
Ezio Melotti added the comment:
See also http://issues.roundup-tracker.org/issue2550920
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/issue
Ezio Melotti added the comment:
The fields (email address, homepage, roles) are validated (by
detectors/userauditor.py) only once the user is being created, and that happens
while clicking on the confirmation link. I can't think of any simple way to
validate them beforehand on the s
Ezio Melotti added the comment:
You should report this upstream on http://issues.roundup-tracker.org/
If I understand correctly you want to be able to login by entering
username+password or email+password, but currently only username+password is
allowed, right?
--
nosy: +ezio.melotti
Ezio Melotti added the comment:
I haven't heard of any similar issues, so the patch should have solved the
problem.
--
status: testing -> resolved
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/me
Ezio Melotti added the comment:
Applied in https://hg.python.org/tracker/roundup/rev/92cf53770045
Thanks for the patch!
--
assignedto: -> ezio.melotti
nosy: +ezio.melotti
status: chatting -> resolved
___
PSF Meta Tracker
Ezio Melotti added the comment:
Applied in https://hg.python.org/tracker/roundup/rev/4d5a7f04978f
--
status: chatting -> resolved
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/is
Ezio Melotti added the comment:
The attached patch fixes the issue.
I couldn't find any method that checks for exact matches, so I kept filter and
then checked the GH username manually. There is a lookup method, but IIUC it
only works on the "key field", which in this case i
New submission from Ezio Melotti:
A user created https://github.com/python/cpython/pull/809 but the PR got linked
with the wrong name: http://bugs.python.org/issue29862
This is because set_roundup_user uses filter() to find matching names, and
filter returns all values that contain the given
Ezio Melotti added the comment:
I successfully redelivered all the requests, so all known bugs should be fixed
now.
--
assignedto: -> ezio.melotti
status: in-progress -> resolved
___
PSF Meta Tracker
Ezio Melotti added the comment:
Other bug fixed: https://hg.python.org/tracker/roundup/rev/1da702d3cf41
Maciej also fixed https://hg.python.org/tracker/roundup/rev/8c49b7b2bc8f and
https://hg.python.org/tracker/roundup/rev/e58c841100f8
I'm still going through all the failed requests and se
Ezio Melotti added the comment:
While going through the other failed request, I found and fixed another bug:
https://hg.python.org/tracker/roundup/rev/f04116acd3d8
While fixing that bug and reading the code I also noticed another unrelated bug
-- Maciej is taking care of it.
There's
Ezio Melotti added the comment:
I asked for access, and looked at the payloads. The 4 errors mentioned in the
previous message are just push messages that don't reference any bpo issue, so
they are not really errors (and they were delivered correctly).
I found older payloads that failed
Ezio Melotti added the comment:
I've been looking at the logs overnight and these are the few errors I got so
far (timestamps should be UTC):
[24/Mar/2017 08:23:44] "POST /tracker/pull_request HTTP/1.1" 200 -
ERROR:root:zero messages created for 31bb6800-106b-11e7-91cd-85bcd9
Ezio Melotti added the comment:
In which cases the committer is set to GitHub?
FWIW Maciej recently pushed a change to show both committer and author:
https://hg.python.org/tracker/roundup/rev/2defe7a040a7
--
status: unread -> chatt
Ezio Melotti added the comment:
I added the title and status to the link in
https://hg.python.org/tracker/python-dev/rev/38de93af8c3d
This only works if the info is already available in Roundup (currently they
should only get set when a PR is added/updated by a webhook
Ezio Melotti added the comment:
I think the patch is fine, but if we are going to update the stage when a PR is
added through the webhooks, perhaps we should do it also when it's added
manually.
--
status: chatting -> unread
___
Ezio Melotti added the comment:
This happened again in http://bugs.python.org/issue29554 -- not sure if someone
was playing with the payloads or if something else triggered the duplication.
___
PSF Meta Tracker
<h
Ezio Melotti added the comment:
This should be the commit webhook that generates messages whenever a new commit
includes bpo-N in the message.
I'd suggest to wait a bit and see if it can be fixed from the GitHub side (i.e.
if we can avoid to trigger those requests in the first
Ezio Melotti added the comment:
See also https://github.com/python/core-workflow/issues/33
If it can be fixed on the GitHub side we can close this.
--
status: unread -> chatting
___
PSF Meta Tracker
<http://psf.upfronthosting
New submission from Ezio Melotti:
Nick just did a merge in https://github.com/python/cpython/pull/118 and for
each merged changeset that contained a reference to bpo, a new message has been
resent to the corresponding issue, see:
http://bugs.python.org/msg288063
http://bugs.python.org
Ezio Melotti added the comment:
Note that we check duplication when adding PRs manually to the issue, but afaik
not when the PR is added by GitHub through the webhooks. I don't know if there
might be cases where separate events might cause a PR to be added more than
once (except for man
Ezio Melotti added the comment:
ISTM that best way to fix this is to just ignore all the (#NNN) at the end of
the commit message. The try/except should also stay to avoid failures in case
of typos or other extraneous ids.
If the commit message references other PRs directly, it might cause
Ezio Melotti added the comment:
I noticed that it's possible to add the same PR multiple times to the same
issue, see e.g. http://bugs.python.org/issue29546
This probably happened because the payload was re-sent manually, and shouldn't
otherwise be an issue, so we might not have to f
Ezio Melotti added the comment:
This seems to work, so I'm going to close it.
--
status: testing -> resolved
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/me
Ezio Melotti added the comment:
I pushed the try/except fix in
https://hg.python.org/tracker/roundup/rev/1e58dddad971
I don't have a delivery_id, but the event was pushed almost 3h ago, around
19:18:56 UTC. See
https://mail.python.org/pipermail/python-bugs-list/2017-February/326183.ht
Ezio Melotti added the comment:
The commit message includes the pull request id, and it got accidentally
captured by the regex that looks for issue numbers. The code doesn't check if
the issue id exists, and that caused the failure.
An easy fix is to add a try/except, but once we rea
Ezio Melotti added the comment:
> I've changed it to set_roundup_user, not sure what kind of constant you were
> talking about.
I meant a constant for the python-dev user you find with: user_ids =
self.db.user.filter(None, {'username': 'python-dev'})
Since the
New submission from Ezio Melotti:
I haven't tried the patch yet, but in
+if len(user_id) > 1:
+# pick first matching user, when multiple found
+user_id = user_id[0]
+elif len(user_id) < 1:
+# set bpobot as userid when no
Ezio Melotti added the comment:
Done in https://hg.python.org/tracker/roundup/rev/f44e8ff423a4
Thanks everyone for the patches and the reviews!
--
assignedto: -> ezio.melotti
nosy: +ezio.melotti
status: in-progress -> testing
_
Ezio Melotti added the comment:
Done in https://hg.python.org/tracker/python-dev/rev/18a7bc95ec31
Thanks for the patch!
--
assignedto: -> ezio.melotti
status: chatting -> resolved
___
PSF Meta Tracker
Ezio Melotti added the comment:
I'm +0.5 on the prefix idea -- by default it should work without prefix (both
for backward compatibility and because most people will copy/paste CSIDs
without bothering adding the prefix). It could be still useful in case people
want to explicitly disambi
Ezio Melotti added the comment:
Done in https://hg.python.org/tracker/python-dev/rev/8708baeae844
Thanks for the patch!
--
assignedto: anish.shah -> ezio.melotti
nosy: +ezio.melotti
status: in-progress -> testing
___
PSF Meta T
Ezio Melotti added the comment:
I committed the latest patch with a few changes (fixed a bug in the url
generation and removed the [remove] buttons) in
https://hg.python.org/tracker/python-dev/rev/f2fa6e43904a
I'll leave the issue open for another day in case something comes up.
Thanks
Ezio Melotti added the comment:
> 1. Add a 't' mark to mark our triagers
If we want to add this, I think we should rethink it a bit, since now we have a
* for people show signed the cla, an image for committers, and a letter for
triagers. Perhaps we could have a black&white
Ezio Melotti added the comment:
I've looked at the latest patch (2016-07-21.16:13:52) and the only major issue
I've found so far is that any user can unlink (remove) any PR, even the ones
created by other users. This is likely because of wrong permissions in
schema.py.
There are
I updated the email address.
Let me know if it works.
Best Regards,
Ezio Melotti
On Thu, Nov 10, 2016 at 7:26 PM, Michael Witten wrote:
> I suspect that this email is inappropriate for this list, yet I am
> unaware of a forum that would be more appropriate.
>
> In short, I re
Ezio Melotti added the comment:
> Adding new keywords will make triagers' and core developers' life harder in
> my opinion.
I agree with Berker on this -- adding new keywords and components makes the
tracker harder to use. With more fields it is more difficult to
find/selec
Ezio Melotti added the comment:
Done.
--
assignedto: -> ezio.melotti
nosy: +ezio.melotti
status: unread -> resolved
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta
Ezio Melotti added the comment:
I applied the patch (thanks Berker!) in
https://hg.python.org/tracker/python-dev/rev/b1707303899e and the issue seems
now resolved. If the problem persists wait for a day for the cached (and
missing) data to expire -- the script will then try to fetch them
Ezio Melotti added the comment:
I committed the latest patch in
https://hg.python.org/tracker/python-dev/rev/deefac77e9dd
Thanks for the initial patch!
--
status: in-progress -> resolved
___
PSF Meta Tracker
&l
Ezio Melotti added the comment:
After discussing with Brett and R. David, I modified Maciej patch to make
GitHub usernames public. The previous patch I uploaded has stricter
permissions checks in case we change our mind.
___
PSF Meta
Ezio Melotti added the comment:
Fixed in c25088641f39, thanks for the patches!
--
assignedto: -> ezio.melotti
status: chatting -> resolved
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta
Ezio Melotti added the comment:
Thanks for the patch!
Have you checked that users can edit their own github username and that they
can not edit the username of other users?
I'm not sure what the permissions for viewing the username should be, maybe it
should be hidden to anonymous and re
New submission from Ezio Melotti:
A user reported that the weekly summary is sent out as us-ascii even though it
contains non-ascii characters. The summary should use utf-8 instead.
Using _charset='utf-8' at line 705 (and later) of
https://hg.python.org/tracker/python-dev/file/t
Ezio Melotti added the comment:
I think you should report this upstream: http://issues.roundup-tracker.org/
--
nosy: +ezio.melotti
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/issue
Ezio Melotti added the comment:
Have you tried entering a date range like the ones in the second bullet list at
http://roundup.sourceforge.net/doc-1.0/user_guide.html#date-properties in the
search page?
___
PSF Meta Tracker
<h
Ezio Melotti added the comment:
Are you asking for something like
http://bugs.python.org/msg?%40sort0=activity&%40sortdir0=on ?
--
nosy: +ezio.melotti
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/i
Ezio Melotti added the comment:
Personally I filter both regular tracker emails and rietveld ones under the
same label, so by using the same "from" address used by the bug tracker I can
get both by using a single filter. I'm not sure if others want to distinguish
between the t
Ezio Melotti added the comment:
This seems to work again now, so I'm closing this issue.
--
assignedto: -> ezio.melotti
nosy: +ezio.melotti
status: unread -> resolved
___
PSF Meta Tracker
<http://psf.upfronthosting
Ezio Melotti added the comment:
Applied in http://hg.python.org/tracker/python-dev/rev/46d557b8228a and
http://hg.python.org/tracker/python-dev/rev/9bab717d18a0.
Thanks for the patch!
--
status: unread -> chatting
___
PSF M
Ezio Melotti added the comment:
Applied in http://hg.python.org/tracker/python-dev/rev/dfcb75b1e932
--
assignedto: -> ezio.melotti
status: chatting -> resolved
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/rou
Ezio Melotti added the comment:
Is it just the image that needs to be replaced or is the myopenid login no
longer available?
--
nosy: +ezio.melotti, loewis
status: unread -> chatting
___
PSF Meta Tracker
&l
Ezio Melotti added the comment:
Should be fixed now.
--
assignedto: -> ezio.melotti
nosy: +ezio.melotti
status: unread -> resolved
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta
Ezio Melotti added the comment:
Done in
http://hg.python.org/tracker/python-dev/rev/90207bfea44c and
http://hg.python.org/tracker/python-dev/rev/bbbe6c190a99.
The script has been running for over a month and seems to work fine, so I'm
closing this.
--
status: in-progress ->
Ezio Melotti added the comment:
See issue522
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/issue546>
___
___
Tracker-d
There is already a notice, but it's only on the "issue" page. We could
move it to the "page" page, so that it shows on all the pages.
On May 25, 2014 6:50 PM, "R. David Murray" wrote:
> Did they copy the contents? Can we set up some sort of redirect
> instead?
>
Ezio Melotti added the comment:
You should report this here: https://bitbucket.org/rptlab/reportlab/issues
--
assignedto: -> ezio.melotti
nosy: +ezio.melotti
status: unread -> resolved
___
PSF Meta Tracker
Ezio Melotti added the comment:
Here is the patch.
I plan to commit it in the next 24 hours, so we can see if it works fine with
tomorrow weekly summary.
If it does I'll add links to the stats page somewhere in the sidebar.
___
PSF
New submission from Ezio Melotti:
I've been working on adding a "stats" page to the tracker, that uses the stats
from the weekly report to plot some graphs. A "static" demo is already up at
http://bugs.python.org/issue?@template=stats
The plots are created client-si
Ezio Melotti added the comment:
Fixed in http://hg.python.org/tracker/python-dev/rev/1fd5ec663c29, thanks for
the report!
--
assignedto: -> ezio.melotti
nosy: +ezio.melotti
status: unread -> resolved
___
PSF Meta Tracker
Ezio Melotti added the comment:
The attached patch fixes the issue by changing action="#" to
action="name_of_current_page".
This loses the information about the query string (e.g. in case of search).
Since Roundup uses different pages for different issues, logging in
Ezio Melotti added the comment:
This is a known issue and a duplicate of
http://psf.upfronthosting.co.za/roundup/meta/issue448. Clearing the query
string or clicking on the logo at the top-left are good workaround until we get
this fixed.
--
nosy: +ezio.melotti
status: unread
Ezio Melotti added the comment:
I did that and everything seems to work fine.
I also reverted on all the trackers the previous fix that was avoiding the XSS
by changing the templates, and checked that the XSS still fails.
--
assignedto: -> ezio.melotti
nosy: +ezio.melotti
sta
Ezio Melotti added the comment:
I wonder how they find webmas...@python.org. On bugs.python.org there's a
"Report tracker problem" link, so if they are having problems they should
follow that link and either report the metaissue or, if we add a link to
tracker-discuss here, r
Ezio Melotti added the comment:
Why do you think this would be useful?
There's already a link to the meta-tracker, and indeed adding a link to
tracker-discuss somewhere here might be ok.
--
nosy: +ezio.melotti
status: unread ->
Ezio Melotti added the comment:
> HTML file attachments should never be served as HTML.
This should be fixed now, but it will affect only new attachments.
The content type of old attachments should be changed (by following the "edit"
link) and/or they should be unlinked (together
Ezio Melotti added the comment:
Committed in http://hg.python.org/tracker/python-dev/rev/4cdbeb1c74c6
--
status: in-progress -> resolved
___
PSF Meta Tracker
<http://psf.upfronthosting.co.za/roundup/meta/is
1 - 100 of 364 matches
Mail list logo
