[Tracker-discuss] [issue560] error setup msiexec.exe

2014-12-29 Thread Berker Peksag
Berker Peksag added the comment: Thanks for the report, but please create a new issue at https://bugs.python.org/ or better ask your question at https://mail.python.org/mailman/listinfo/python-list first. This tracker is for development of our Roundup instance. -- nosy

[Tracker-discuss] [issue595] Set stage to 'resolved' when an issue is closed

2016-06-09 Thread Berker Peksag
New submission from Berker Peksag: >From https://wiki.python.org/moin/DesiredTrackerFeatures > When an issue is closed stage should be automatically set to 'resolved'. -- files: setresolved.diff messages: 3041 nosy: berker.peksag priority: feature status: unread title: Set

[Tracker-discuss] [issue597] Delete now redundant detectors/changes_xml_writer.py

2016-06-11 Thread Berker Peksag
New submission from Berker Peksag: See https://mail.python.org/pipermail/tracker-discuss/2007-June/000895.html for discussion. The file can be seen at http://bugs.python.org/@@file/recent-changes.xml -- files: delete_changes_xml_writer.diff messages: 3045 nosy: berker.peksag priority

[Tracker-discuss] [issue556] Server error when trying to change homepage

2016-06-11 Thread Berker Peksag
Berker Peksag added the comment: This has been fixed recently. -- nosy: +berker.peksag status: chatting -> resolved ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/m

[Tracker-discuss] [issue598] Hide retired queries in "Your Queries" sidebar

2016-06-11 Thread Berker Peksag
New submission from Berker Peksag: This is one of my biggest annoyances of the current tracker. We should hide queries if they are marked as 'retired'. -- files: hide_retired_queries.diff messages: 3046 nosy: berker.peksag priority: bug status: unread title: Hide retired queries

[Tracker-discuss] [issue525] OpenID support for Meta Tracker

2016-06-09 Thread Berker Peksag
Berker Peksag added the comment: Duplicate of issue 387. -- nosy: +berker.peksag status: chatting -> resolved superseder: +Need OpenID login for this tracker ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za&

[Tracker-discuss] [issue571] Make the user form uneditable if current user is not authenticated and is not the owner of the profile

2016-06-09 Thread Berker Peksag
Berker Peksag added the comment: Duplicate of issue 551. -- assignedto: geosim -> nosy: +berker.peksag -geosim status: in-progress -> resolved superseder: +Make the user form uneditable if current user is not authenticated and is not the owner of the profile -"broken for

[Tracker-discuss] [issue599] Strip content when replying to an issue via email

2016-06-13 Thread Berker Peksag
New submission from Berker Peksag: Here is an example http://bugs.python.org/issue25413#msg268427 -- messages: 3048 nosy: berker.peksag priority: feature status: unread title: Strip content when replying to an issue via email ___ PSF

[Tracker-discuss] [issue598] Hide retired queries in "Your Queries" sidebar

2016-06-14 Thread Berker Peksag
Berker Peksag added the comment: So does that mean that the current 'Delete' button at query?@template=edit is sort of misnamed (it actually retires the query)? Instead of two steps (retire -> delete) can we just delete the query? ___

[Tracker-discuss] [issue598] Hide retired queries in "Your Queries" sidebar

2016-06-14 Thread Berker Peksag
Berker Peksag added the comment: Or maybe we can have two buttons: Retire (the current behavior) and Delete We can mark retired queries with a different background in the sidebar. ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co

[Tracker-discuss] [issue594] Fix ImportError: cannot import name rndstr in oic_login.py

2016-06-09 Thread Berker Peksag
New submission from Berker Peksag: I'm getting an import error with the latest version of oic. Here is a patch to fix this. -- files: oic.diff messages: 3040 nosy: berker.peksag priority: bug status: unread title: Fix ImportError: cannot import name rndstr in oic_login.py

[Tracker-discuss] [issue592] Show GitHub comments on b.p.o

2016-07-25 Thread Berker Peksag
Berker Peksag added the comment: Maciej, that sounds good to me but I agree with David. This needs to be discussed on the core-workflow list. It would be nice to have a some sort of mockup or flowchart to see what kind of information will be displayed in these combined comments. It's a bit

[Tracker-discuss] [issue552] Modules and interest no longer displayed in nosy list completion

2016-07-26 Thread Berker Peksag
Berker Peksag added the comment: It's broken because we've deleted the devguide repository from hg.python.org. Here is a patch. -- nosy: +berker.peksag status: unread -> chatting ___ PSF Meta Tracker <me

[Tracker-discuss] [issue592] Show GitHub comments on b.p.o

2016-07-13 Thread Berker Peksag
New submission from Berker Peksag: Thanks for the patches! :) GitHub already spams every single comment made on a pull request and this will make it worse. I'm -1 on this. It's fine if other core developers want to backup review comments, but it shouldn't be shown on bugs.python.org

[Tracker-discuss] [issue600] Convert patches to GitHub Pull Request

2016-07-13 Thread Berker Peksag
Berker Peksag added the comment: How do you get the correct author information of the patch? I don't think there is an easy way [1] to extract the author information to use it in the pull requests. [1] You could probably check the GitHub username field of the author but you could have

[Tracker-discuss] [issue586] Add GitHub Pull Request URL on issue page

2016-07-13 Thread Berker Peksag
Berker Peksag added the comment: Issue 589 is a different feature and it should be discussed there (by the way it would be really nice if you could give more information about the feature and the patch -- I had to read the whole patch to understand what it does). The problem

[Tracker-discuss] [issue586] Add GitHub Pull Request URL on issue page

2016-07-12 Thread Berker Peksag
Berker Peksag added the comment: Also, I'm not fan of such a manual work. I would prefer to have a JSON endpoint which queries open pull requests on python/cpython and match if the title of a pull request contains the issue number. You can see https://code.djangoproject.com/ticket/25227

[Tracker-discuss] [issue586] Add GitHub Pull Request URL on issue page

2016-07-12 Thread Berker Peksag
Berker Peksag added the comment: +url = newvalues.get('url', '') You should also return early if there is no 'url' key in newvalues. i18n:translate="" can be removed. I don't think we are going to support a non-English language. I would also prefer a 'remove' link instea

[Tracker-discuss] [issue602] automatic redirect to https

2016-08-02 Thread Berker Peksag
Berker Peksag added the comment: This is a duplicate of issue 463. -- nosy: +berker.peksag status: unread -> resolved superseder: +HTTPS only version for login for this tracker ___ PSF Meta Tracker <me

[Tracker-discuss] [issue590] Show Pull Request status on b.p.o

2016-07-13 Thread Berker Peksag
New submission from Berker Peksag: Do we need a separate issue for this? I think this can be done in issue 586. -- nosy: +berker.peksag ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthost

[Tracker-discuss] [issue586] Add GitHub Pull Request URL on issue page

2016-07-18 Thread Berker Peksag
Berker Peksag added the comment: I'm not sure I explained myself clearly so here is a quick and dirty patch, including a screenshot: https://dl.dropboxusercontent.com/u/166024/gh-pr.png Since I don't have meaningful data I chose Django as an example

[Tracker-discuss] [issue589] Add GitHub PR to b.p.o issues using GitHub webhooks (depends on issue586)

2016-07-19 Thread Berker Peksag
Berker Peksag added the comment: > And if the PR doesn't reference an issue number, it should create a new issue. Wouldn't that create too much noise for trivial pull requests like typo fixes, documentation tweaks and code style changes? Also how do we handle if the user doesn't h

[Tracker-discuss] [issue586] Add GitHub Pull Request URL on issue page

2016-07-19 Thread Berker Peksag
Berker Peksag added the comment: I don't have an objection to a general purpose webhook (I wrote such webhooks for GitHub before.) Using a webhook for a simple task like this will only make the implementation more complicated. I don't see a reason to store pull request URLs in database

[Tracker-discuss] [issue586] Add GitHub Pull Request URL on issue page

2016-07-20 Thread Berker Peksag
Berker Peksag added the comment: The API call in my patch was just an example. GitHub does provide a search API. However, the problem with my approach is that it ignores rate limiting of GitHub API: https://api.github.com/rate_limit So Anish's patch might be more reliable than mine

[Tracker-discuss] [issue611] Update issue with a commit information

2017-02-02 Thread Berker Peksag
Berker Peksag added the comment: The attached patch should fix the empty date issue. ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta

[Tracker-discuss] [issue595] Set stage to 'resolved' when an issue is closed

2017-02-02 Thread Berker Peksag
Berker Peksag added the comment: I tested this again and addressed David's review comment. Applied in https://hg.python.org/tracker/python-dev/rev/5b89f6f8abd3 -- status: chatting -> testing ___ PSF Meta Tracker <me

[Tracker-discuss] [issue611] Update issue with a commit information

2017-02-01 Thread Berker Peksag
Berker Peksag added the comment: > Also, automatic closure isn't the correct behavior, [...] I agree with Zachary. BTW, there is a separate issue to set appropriate fields when an issue is manually closed: http://psf.upfronthosting.co.za/roundup/meta/issue595 (I should probably ap

[Tracker-discuss] [issue611] Update issue with a commit information

2017-02-02 Thread Berker Peksag
Berker Peksag added the comment: Another alternative is to only send notifications for 2.7 and master branches for now [1] For example, see http://bugs.python.org/issue29407 we would only see the latest notification with this approach: http://bugs.python.org/msg286687 Since commit hashes

[Tracker-discuss] [issue619] Use author's name if committer is set to GitHub on commit notifications

2017-02-21 Thread Berker Peksag
New submission from Berker Peksag: New changeset 6336f0d156feec0f109a8d01da108cf96e3d9c60 by GitHub in branch '3.5': bpo-29554: Improve docs for pstat module and profile. (#88) (#228) https://github.com/python/cpython/commit/6336f0d156feec0f109a8d01da108cf96e3d9c60 I think we should use

[Tracker-discuss] [issue615] Set stage to 'patch review' when a PR is added

2017-02-19 Thread Berker Peksag
New submission from Berker Peksag: I wonder if we should be defensive and check the value of the stage field first. -- nosy: +berker.peksag status: unread -> chatting ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za&

[Tracker-discuss] [issue618] Allow developers to edit and unlink pull requests

2017-02-20 Thread Berker Peksag
New submission from Berker Peksag: I noticed that developer cannot edit or unlink pull requests. The attached patch should fix this. -- messages: 3272 nosy: berker.peksag, ezio.melotti priority: bug status: unread title: Allow developers to edit and unlink pull requests

[Tracker-discuss] [issue618] Allow developers to edit and unlink pull requests

2017-02-20 Thread Berker Peksag
Berker Peksag added the comment: Ezio gave his LGTM on #python-dev and I applied the patch in https://hg.python.org/tracker/python-dev/rev/545a7d7ef9e4. -- status: unread -> resolved ___ PSF Meta Tracker <me

[Tracker-discuss] [issue613] Commits notifications don't show up on bugs.p.o

2017-02-27 Thread Berker Peksag
Berker Peksag added the comment: I can reproduce this again, reopening. -- status: done-cbb -> chatting ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/m

[Tracker-discuss] [issue613] Commits notifications don't show up on bugs.p.o

2017-03-02 Thread Berker Peksag
Berker Peksag added the comment: See https://github.com/python/cpython/commit/0dadf56737f591c83d18db5e445960d39448583e for example. The commit message contains bpo-29655 and there should be a comment similar to http://psf.upfronthosting.co.za/roundup/meta/msg3247 at https://bugs.python.org

[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

2016-09-19 Thread Berker Peksag
Berker Peksag added the comment: I don't see a lot of C issues in the "easy issues" list. I agree that some of them (including a few pure Python ones) shouldn't be classified as "easy". I'd say we should remove the following issues from the list: * http://bugs.pyt

[Tracker-discuss] [issue594] Fix ImportError: cannot import name rndstr in oic_login.py

2016-11-18 Thread Berker Peksag
Berker Peksag added the comment: The patch also helped Ezio so I just committed it in https://hg.python.org/tracker/python-dev/rev/46237fce3bfe and pinged him. -- status: unread -> resolved ___ PSF Meta Tracker <me

[Tracker-discuss] [issue610] Hyperlink git hashes of 10 or 11 characters

2016-12-21 Thread Berker Peksag
Berker Peksag added the comment: Looks good to me too. I can do the merging if David or Ezio are busy. -- nosy: +berker.peksag ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/rou

[Tracker-discuss] [issue613] Commits notifications don't show up on bugs.p.o

2017-03-24 Thread Berker Peksag
Berker Peksag added the comment: I agree with Ned. Thanks, Ezio! ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta

[Tracker-discuss] [issue613] Commits notifications don't show up on bugs.p.o

2017-03-24 Thread Berker Peksag
Berker Peksag added the comment: I think you need to be an administrator on that repo to see the payloads. ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta

[Tracker-discuss] [issue619] Use author's name if committer is set to GitHub on commit notifications

2017-03-24 Thread Berker Peksag
Berker Peksag added the comment: Next time please let me push my own patches. If you have comments please left them in the issue first. Doing your own thing on my patches without even try to communicate is a bit rude. ___ PSF Meta Tracker

[Tracker-discuss] [issue613] Commits notifications don't show up on bugs.p.o

2017-03-17 Thread Berker Peksag
Berker Peksag added the comment: Note that there is an open issue for the committer name thing: http://psf.upfronthosting.co.za/roundup/meta/issue619 ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthost

[Tracker-discuss] [issue619] Use author's name if committer is set to GitHub on commit notifications

2017-03-15 Thread Berker Peksag
Berker Peksag added the comment: I might miss some other cases, but for example, when you edit a file on GitHub or when you merge your own PR. ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthost

[Tracker-discuss] [issue613] Commits notifications don't show up on bugs.p.o

2017-03-17 Thread Berker Peksag
Berker Peksag added the comment: I believe the 400 status code comes from one of the "raise Reject()" lines in roundup/github.py. I will try to add some descriptive messages to them to help debug the issue. ___ PSF Meta Tracker

[Tracker-discuss] [issue613] Commits notifications don't show up on bugs.p.o

2017-03-17 Thread Berker Peksag
Berker Peksag added the comment: Here is a patch that tweaks some exception messages and adds logging.error() calls in GitHubHandler class. ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.z

[Tracker-discuss] [issue613] Commits notifications don't show up on bugs.p.o

2017-03-17 Thread Berker Peksag
Berker Peksag added the comment: I converted Brett's payload example to a test case and I couldn't be able to create a failing test case. Here is a patch with a test. ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za>

[Tracker-discuss] [issue619] Use author's name if committer is set to GitHub on commit notifications

2017-03-17 Thread Berker Peksag
Berker Peksag added the comment: You can see an example of this in the patch I posted at http://psf.upfronthosting.co.za/roundup/meta/issue613: New changeset 9d07aceedabcdc9826489f8b9ba056283bb3 by GitHub (Brett Cannon) in branch '3.6': bpo-1: Mention coverage.py in trace module

[Tracker-discuss] [issue619] Use author's name if committer is set to GitHub on commit notifications

2017-03-17 Thread Berker Peksag
Berker Peksag added the comment: Here is a patch. ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta/issue619> ___diff --g

[Tracker-discuss] [issue613] Commits notifications don't show up on bugs.p.o

2017-03-03 Thread Berker Peksag
Berker Peksag added the comment: Update: It looks like it sometimes works for 3.6 branch: * http://bugs.python.org/issue28893#msg288853 (2017-03-03 06:16) But not for master branch: * https://bugs.python.org/issue9303#msg288877 (2017-03-03 13:11

[Tracker-discuss] [issue637] Exception SystemError: '..\\..\\Objects\\listobject.c:169: bad argument to internal function'

2017-07-28 Thread Berker Peksag
Berker Peksag added the comment: Thank you for the report, but this is not the correct place to report issues with third-party Python modules. The exception message suggests that your Python version is 2.7 and it comes from PyList_Size(): https://github.com/python/cpython/blob

[Tracker-discuss] [issue615] Set stage to 'patch review' when a PR is added

2017-07-24 Thread Berker Peksag
Berker Peksag added the comment: Thanks for the feedback. Here's a patch that updates 'stage' and 'keywords' fields. This patch updates the detector. I'll upload another one for the webhook. I'll commit it when I get a code review, thanks

[Tracker-discuss] [issue615] Set stage to 'patch review' when a PR is added

2017-07-24 Thread Berker Peksag
Berker Peksag added the comment: Here's the second patch. ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta/issue615> _

[Tracker-discuss] [issue636] 'patch' keyword not being set for PR-only issues

2017-07-24 Thread Berker Peksag
Berker Peksag added the comment: By the way, I can implement this in http://psf.upfronthosting.co.za/roundup/meta/issue615 -- nosy: +berker.peksag status: unread -> chatting ___ PSF Meta Tracker <metatrac...@psf.upfronthosting

[Tracker-discuss] [issue615] Set stage to 'patch review' when a PR is added

2017-08-04 Thread Berker Peksag
Berker Peksag added the comment: So after http://psf.upfronthosting.co.za/roundup/meta/msg3305 and http://psf.upfronthosting.co.za/roundup/meta/msg3306 I explicitly said "I'll commit it when I get a code review, thanks!" in my earlier comment, and you still did the same thing.

[Tracker-discuss] [issue631] Planet Python, https and rendering of the site.

2017-06-08 Thread Berker Peksag
Berker Peksag added the comment: https://github.com/python/planet is probably the better place to report 404 errors. -- nosy: +berker.peksag ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthost

[Tracker-discuss] [issue627] Please support "fix[es] bpo-xxxx" in addition to "close[s] bpo-xxxx"

2017-09-08 Thread Berker Peksag
Berker Peksag added the comment: issue627.diff looks good to me. I'd use assertIsNotNone instead of assertTrue but that's not a big deal. Thanks! -- nosy: +berker.peksag priority: wish -> feature ___ PSF Meta Tracker <me

[Tracker-discuss] [issue644] 'Random Issue' Button isn't working

2017-11-10 Thread Berker Peksag
Berker Peksag <berker.pek...@gmail.com> added the comment: Thank you for your quick response and for your detailed analysis, John. I will attach a patch to implement your suggestions. > My thought was that the random function wasn't so random. The new 1.5.1+ > (what will be 1.6)

[Tracker-discuss] [issue644] 'Random Issue' Button isn't working

2017-11-05 Thread Berker Peksag
Berker Peksag <berker.pek...@gmail.com> added the comment: >From >http://www.roundup-tracker.org/docs/customizing.html#extensions-adding-capabilities-to-your-tracker All files from this dir are loaded when tracker instance is created, [...] It's not clear to me when th

[Tracker-discuss] [issue644] 'Random Issue' Button isn't working

2017-11-09 Thread Berker Peksag
Berker Peksag <berker.pek...@gmail.com> added the comment: Hi John, do you know a workaround to make the random issue extension work again? -- nosy: +rouilj ___ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.

[Tracker-discuss] [issue634] Only link PR to the bpo that is in the PR title, not the body

2017-11-09 Thread Berker Peksag
Berker Peksag <berker.pek...@gmail.com> added the comment: I agree with Mariatta. We should just look for the PR title. As a fallback, we can check the body if we can't find an issue number in the title. -- nosy: +berker.

[Tracker-discuss] [issue456] Add user links to roundup users

2018-06-09 Thread Berker Peksag
Berker Peksag added the comment: This appears to be working now. I've just set it in my profile: https://bugs.python.org/user14674 Closing as 'resolved'. -- nosy: +berker.peksag status: in-progress -> resolved ___ PSF Meta Trac

[Tracker-discuss] [issue624] bpo emails contain useless non-github pull_request number - users want a link to actual github PR

2018-06-09 Thread Berker Peksag
Berker Peksag added the comment: Here's patch to fix this issue. Example output: -- components: +Tkinter versions: +Python 2.4 pull_request: https://github.com/python/cpython/pull/341 Old version: -- components: +Tkinter versions: +Python 2.4 pull_requests: +42

[Tracker-discuss] [issue654] Add triager icon

2018-06-09 Thread Berker Peksag
Berker Peksag added the comment: Ezio gave his LGTM on #python-dev and I just applied in https://hg.python.org/tracker/python-dev/rev/aac421fdfffb -- status: chatting -> resolved ___ PSF Meta Tracker &l

[Tracker-discuss] [issue599] Strip content when replying to an issue via email

2018-06-09 Thread Berker Peksag
Berker Peksag added the comment: Reading issue 491 again, I don't think this is exactly a duplicate of that issue. Reopening. -- status: resolved -> chatting superseder: -Ignore email signatures ___ PSF Meta Tracker &l

[Tracker-discuss] [issue645] Searching for open bugs sets the button to all

2018-06-09 Thread Berker Peksag
Berker Peksag added the comment: Here's a patch to fix this issue. -- nosy: +berker.peksag, ezio.melotti status: unread -> chatting ___ PSF Meta Tracker <http://psf.upfronthosting.co.za/roundup/meta/is

[Tracker-discuss] [issue599] Strip content when replying to an issue via email

2018-06-09 Thread Berker Peksag
Berker Peksag added the comment: This is a duplicate of issue491. -- status: chatting -> resolved superseder: +Ignore email signatures ___ PSF Meta Tracker <http://psf.upfronthosting.co.za/roundup/meta/is

[Tracker-discuss] [issue654] Add triager icon

2018-06-09 Thread Berker Peksag
Berker Peksag added the comment: Addressed Ezio's review comments in issue654_v2.diff. -- status: unread -> chatting ___ PSF Meta Tracker <http://psf.upfronthosting.co.za/roundup/meta/is

[Tracker-discuss] [issue603] update the SSL certificate

2018-06-09 Thread Berker Peksag
Berker Peksag added the comment: > * The server supports only older protocols, but not the current best TLS 1.2. > Grade capped to C. There is an open issue for this item: issue 578 I'm not sure whether we should close that as a duplicate of this one. -- nosy: +berker.

[Tracker-discuss] [issue624] bpo emails contain useless non-github pull_request number - users want a link to actual github PR

2018-06-10 Thread Berker Peksag
Berker Peksag added the comment: Note that the regex code can be probably be simplified, I'm open to suggestions. I'm not sure whether re.S is still needed. +pr_number = db.pull_request.get(pr_number, 'number') Also, I need to be more defensive here and don't do anything

[Tracker-discuss] [issue645] Searching for open bugs sets the button to all

2018-06-10 Thread Berker Peksag
Berker Peksag added the comment: Good catch, Nick. Fixed in issue645_v2.diff. Thanks! ___ PSF Meta Tracker <http://psf.upfronthosting.co.za/roundup/meta/issue645> ___diff --git

[Tracker-discuss] [issue624] bpo emails contain useless non-github pull_request number - users want a link to actual github PR

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: I just noticed that I probably need to update the clean_ok_message() function in pydevutils.py to remove pull_requests. ___ PSF Meta Tracker <http://psf.upfronthosting.co.za/roundup/meta/issue

[Tracker-discuss] [issue490] Review links crash after changing username

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: Thanks for the report and for the patch. The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: unread -> resol

[Tracker-discuss] [issue394] Better integration with Rietveld code review tool

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue365] No issue exists with that id

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue485] Autoclosing Rietveld issue

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: unread -> resol

[Tracker-discuss] [issue554] Add special mark to Rietvelds emails

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue645] Searching for open bugs sets the button to all

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: Applied in https://hg.python.org/tracker/python-dev/rev/9c6cedab723d Thanks for the review, Nick. -- status: chatting -> resolved ___ PSF Meta Tracker <http://psf.upfronthosting.co.za/roundu

[Tracker-discuss] [issue517] Issue Tracker crashes when replying to patch review

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue518] Plaintext connections when logging in

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: All HTTP requests now redirected to HTTPS: $ curl -I http://bugs.python.org HTTP/1.1 301 Moved Permanently Date: Tue, 12 Jun 2018 18:47:14 GMT Server: Apache/2.2.16 (Debian) Location: https://bugs.python.org/ Content-Type: text/html; charset=iso-8859-1

[Tracker-discuss] [issue156] Have a Core Bug Chaser Create a Bug Reporting Screencast

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: After 11 years, I think the better place to discuss this is the core-workflow list. Closing this issue. -- nosy: +berker.peksag status: chatting -> resolved ___ PSF Meta Tracker &l

[Tracker-discuss] [issue387] Need OpenID login for this tracker

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: I don't think it's worth to add OpenID login since the level of traffic and active users are pretty low here. -- nosy: +berker.peksag status: unread -> resolved ___ PSF Meta Tracker &l

[Tracker-discuss] [issue439] Email notifictations not received for rietveld review

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue484] AttributeError 'NoneType' object has no attribute 'issue' when replying to issue

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue410] More useful filenames for patches generated from hg

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue432] Rietveld traceback

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue435] Rietveld Code Review Tool bugs

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue434] ProgrammingError while deleting patch set

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue404] Personal comment rating

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: I agree with Serhiy. Closing this issue. -- nosy: +berker.peksag status: chatting -> resolved ___ PSF Meta Tracker <http://psf.upfronthosting.co.za/roundup/meta/is

[Tracker-discuss] [issue424] Rietveld: AssertionError when trying to reply to comments

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue382] Bad CC on review

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resol

[Tracker-discuss] [issue654] Add triager icon

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: Ezio has just deployed 9363c06cda40 and confirmed that the bug is fixed. Closing as 'resolved' again. -- status: in-progress -> resolved ___ PSF Meta Tracker <http://psf.upfronthosting

[Tracker-discuss] [issue654] Add triager icon

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: I tried to copy is_coordinator() first, but request.client.userid gives the ID of the user who made the request, so it would return invalid results. Did you get the traceback on production? Is it possible to add a print to see the userid? Also, I can

[Tracker-discuss] [issue654] Add triager icon

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: Applied issue654_followup.diff in https://hg.python.org/tracker/python-dev/rev/9363c06cda40 ___ PSF Meta Tracker <http://psf.upfronthosting.co.za/roundup/meta/issue

[Tracker-discuss] [issue615] Set stage to 'patch review' when a PR is added

2018-06-04 Thread Berker Peksag
Berker Peksag added the comment: This has already been deployed. Closing as 'resolved'. -- status: chatting -> resolved ___ PSF Meta Tracker <http://psf.upfronthosting.co.za/roundup/meta/is

[Tracker-discuss] [issue593] Small improvements to issue.item.html

2018-06-04 Thread Berker Peksag
Berker Peksag added the comment: > 1. Add a 't' mark to mark our triagers Ezio's suggestion in msg3197 is much better than mine. I will open a new issue when I have a patch. > 2. List only core developers in the 'assigned to' field It seems too late to change this one. Othe

[Tracker-discuss] [issue599] Strip content when replying to an issue via email

2018-06-04 Thread Berker Peksag
Berker Peksag added the comment: We can use https://github.com/zapier/email-reply-parser to solve this issue. -- nosy: +ezio.melotti status: unread -> chatting ___ PSF Meta Tracker <http://psf.upfronthosting.co.za/roundu

[Tracker-discuss] [issue593] Small improvements to issue.item.html

2018-06-04 Thread Berker Peksag
Berker Peksag added the comment: > Ezio's suggestion in msg3197 is much better than mine. I will open a new > issue when I have a patch. I've opened issue654. ___ PSF Meta Tracker <http://psf.upfronthosting.co.za/roundup/meta

[Tracker-discuss] [issue654] Add triager icon

2018-06-04 Thread Berker Peksag
New submission from Berker Peksag : Here's patch that implements Ezio's suggestion in msg3197. -- files: add_triager_icon.diff messages: 3461 nosy: berker.peksag, ezio.melotti, r.david.murray priority: feature status: unread title: Add triager icon

[Tracker-discuss] [issue644] 'Random Issue' Button isn't working

2018-05-31 Thread Berker Peksag
Berker Peksag added the comment: Thank you for taking a look at this again, John. I will incorporate your suggestions and prepare a patch this weekend. ___ PSF Meta Tracker <http://psf.upfronthosting.co.za/roundup/meta/issue

[Tracker-discuss] [issue644] 'Random Issue' Button isn't working

2018-06-01 Thread Berker Peksag
Berker Peksag added the comment: I've just committed John's suggested approach in https://hg.python.org/tracker/python-dev/rev/9e1d65b4927c but it needs to be deployed by bugs.p.o maintainers. Thank you, again! > I'll keep poking at it to try to figure out why random seems to be >

[Tracker-discuss] [issue644] 'Random Issue' Button isn't working

2018-06-02 Thread Berker Peksag
Berker Peksag added the comment: Ezio has just deployed 9e1d65b4927c and I've confirmed that it works on bugs.python.org. Closing as 'resolved'. Thanks for the report, Cheryl. -- status: testing -> resolved ___ PSF Meta Trac

  1   2   >