From metatracker at psf.upfronthosting.co.za Fri Sep 1 13:25:14 2017 From: metatracker at psf.upfronthosting.co.za (INADA Naoki) Date: Fri, 01 Sep 2017 17:25:14 +0000 Subject: [Tracker-discuss] [issue638] Base URL for bugs.python.org should use https: Message-ID: <1504286714.03.0.11542344582.issue638@psf.upfronthosting.co.za> New submission from INADA Naoki: original thread: https://mail.python.org/pipermail/python-dev/2017-September/149107.html Sometime bugs.python.org creates link starts with http://bugs.python.org/ I think tracker.web config value starts with 'http://'. (ref https://hg.python.org/tracker/python-dev/file/tip/config.ini.template#l118 ) Could you change it to https? I'm sorry if my guess is wrong. ---------- messages: 3383 nosy: inada.naoki priority: urgent status: unread title: Base URL for bugs.python.org should use https: _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Sep 7 20:22:11 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Fri, 08 Sep 2017 00:22:11 +0000 Subject: [Tracker-discuss] [issue463] HTTPS only version for login for this tracker In-Reply-To: <1337666026.16.0.0159243982051.issue463@psf.upfronthosting.co.za> Message-ID: <1504830131.86.0.713968009251.issue463@psf.upfronthosting.co.za> 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 _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Sep 7 20:25:51 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Fri, 08 Sep 2017 00:25:51 +0000 Subject: [Tracker-discuss] [issue635] Information on meta-tracker server migration In-Reply-To: <1500883975.73.0.767118106632.issue635@psf.upfronthosting.co.za> Message-ID: <1504830351.85.0.939245642563.issue635@psf.upfronthosting.co.za> Ezio Melotti added the comment: What's the status on this? ---------- nosy: +ezio.melotti _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Sep 7 20:28:39 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Fri, 08 Sep 2017 00:28:39 +0000 Subject: [Tracker-discuss] [issue638] Base URL for bugs.python.org should use https: In-Reply-To: <1504286714.03.0.11542344582.issue638@psf.upfronthosting.co.za> Message-ID: <1504830519.79.0.14691056448.issue638@psf.upfronthosting.co.za> 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 _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Sep 7 20:30:28 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Fri, 08 Sep 2017 00:30:28 +0000 Subject: [Tracker-discuss] [issue634] Only link PR to the bpo that is in the PR title, not the body In-Reply-To: <1497060629.6.0.388698227929.issue634@psf.upfronthosting.co.za> Message-ID: <1504830628.11.0.817152717345.issue634@psf.upfronthosting.co.za> Ezio Melotti added the comment: Maciej, didn't we fix this? ---------- nosy: +ezio.melotti, maciej.szulik _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Sep 7 21:08:18 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Fri, 08 Sep 2017 01:08:18 +0000 Subject: [Tracker-discuss] [issue634] Only link PR to the bpo that is in the PR title, not the body In-Reply-To: <1497060629.6.0.388698227929.issue634@psf.upfronthosting.co.za> Message-ID: <1504832898.02.0.40201118635.issue634@psf.upfronthosting.co.za> 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.murray _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Sep 7 22:36:43 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Fri, 08 Sep 2017 02:36:43 +0000 Subject: [Tracker-discuss] [issue627] Please support "fix[es] bpo-xxxx" in addition to "close[s] bpo-xxxx" In-Reply-To: <1495045990.62.0.0176750718532.issue627@psf.upfronthosting.co.za> Message-ID: <1504838203.24.0.260382169239.issue627@psf.upfronthosting.co.za> 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 create files, but that's a separate issue. ---------- nosy: +ezio.melotti, maciej.szulik status: unread -> in-progress _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- diff --git a/roundup/github.py b/roundup/github.py --- a/roundup/github.py +++ b/roundup/github.py @@ -16,7 +16,7 @@ return a == b URL_RE = re.compile(r'https://github.com/python/cpython/pull/(?P\d+)') -VERBS = r'(?:\b(?Pclose[sd]?|closing|)\s+)?' +VERBS = r'(?:\b(?Pclose[sd]?|closing|fix(?:e[sd])?|)\s+)?' ISSUE_RE = re.compile(r'%sbpo-(?P\d+)' % VERBS, re.I|re.U) BRANCH_RE = re.compile(r'(2\.\d|3\.\d|master)', re.I) diff --git a/test/test_github.py b/test/test_github.py --- a/test/test_github.py +++ b/test/test_github.py @@ -7,7 +7,7 @@ from roundup.cgi import client from roundup.backends import list_backends from roundup.date import Date -from roundup.github import GitHubHandler +from roundup.github import GitHubHandler, ISSUE_RE from roundup.exceptions import * NEEDS_INSTANCE = 1 @@ -53,6 +53,18 @@ self.db.issue.create(title="Issue 1") return dummy_client + + def testVERBS(self): + """Check that all these messages contain a "closing verb".""" + messages = [ + 'close bpo-1', 'closes bpo-1', 'closed bpo-1', 'closing bpo-1', + 'fix bpo-1', 'fixes bpo-1', 'fixed bpo-1', + ] + for message in messages: + for match in ISSUE_RE.finditer(message): + data = match.groupdict() + self.assertTrue(data.get('verb')) + def testMissingSecretKey(self): os.environ.pop('SECRET_KEY') dummy_client = self._make_client("pingevent.txt") From metatracker at psf.upfronthosting.co.za Fri Sep 8 02:18:53 2017 From: metatracker at psf.upfronthosting.co.za (Berker Peksag) Date: Fri, 08 Sep 2017 06:18:53 +0000 Subject: [Tracker-discuss] [issue627] Please support "fix[es] bpo-xxxx" in addition to "close[s] bpo-xxxx" In-Reply-To: <1495045990.62.0.0176750718532.issue627@psf.upfronthosting.co.za> Message-ID: <1504851533.37.0.0382759818416.issue627@psf.upfronthosting.co.za> 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 _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat Sep 9 20:27:25 2017 From: metatracker at psf.upfronthosting.co.za (Mark Mangoba) Date: Sun, 10 Sep 2017 00:27:25 +0000 Subject: [Tracker-discuss] [issue635] Information on meta-tracker server migration In-Reply-To: <1500883975.73.0.767118106632.issue635@psf.upfronthosting.co.za> Message-ID: <1505003245.64.0.466336928869.issue635@psf.upfronthosting.co.za> Mark Mangoba added the comment: We have started the initial process. At the moment, we are getting the necessary accounts setup, DockerHub and RH OpenShift. maciej.szulik has done work with his team on the database and have an estimated timeline in the next 2 months to complete. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Sep 11 15:02:21 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Mon, 11 Sep 2017 19:02:21 +0000 Subject: [Tracker-discuss] [issue627] Please support "fix[es] bpo-xxxx" in addition to "close[s] bpo-xxxx" In-Reply-To: <1495045990.62.0.0176750718532.issue627@psf.upfronthosting.co.za> Message-ID: <1505156541.37.0.372764920925.issue627@psf.upfronthosting.co.za> 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 -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Sat Sep 16 13:17:00 2017 From: metatracker at psf.upfronthosting.co.za (Terry Reedy) Date: Sat, 16 Sep 2017 17:17:00 +0000 Subject: [Tracker-discuss] [issue639] "All text" search limited to 2 words? Message-ID: <1505582220.98.0.414806842837.issue639@psf.upfronthosting.co.za> New submission from Terry Reedy: Enter 'idle crash caret' in the title box, apparently in any order, select "don't care" or "closed" for Status, select [search], and #31438 and #24170 are displayed. Move 'idle crash caret' to the 'All text' box, and instead of a wider search, nothing is returned. Remove any of the 3 search terms and the 2 issues above and others are returned. I have experienced before that I have had to cut back to 2 words to get anything, but I never before tried 3 in the title box to discover that the original empty result is a bug. Until this is fixed, could 'limit: 2 words' be added to the form? ---------- messages: 3393 nosy: terry.reedy priority: bug status: unread title: "All text" search limited to 2 words? _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Sep 21 03:31:48 2017 From: metatracker at psf.upfronthosting.co.za (Marc-Andre Lemburg) Date: Thu, 21 Sep 2017 07:31:48 +0000 Subject: [Tracker-discuss] [issue640] Problem with email replies for tickets which use [...] in the subject Message-ID: <1505979108.02.0.195706139994.issue640@psf.upfronthosting.co.za> New submission from Marc-Andre Lemburg: Issue https://bugs.python.org/issue31530 use a title "[2.7] Python 2.7 readahead feature of file objects is not thread safe" for the ticket. When trying to reply to ticket items via email, roundup sent back an error message stating: """ There were problems handling your subject line argument list: - not of form [arg=value,value,...;arg=value,value,...] Subject was: "Re: [issue31530] [2.7] Python 2.7 readahead feature of file objects is not thread safe" """ Apparently, it was picking up the "[2.7]" as an argument indicator. Removing the "[2.7]" from the title made the problem go away. Since I don't think anyone (apart from maybe Roundup itself) is using [...] for passing arguments to it, it would probably be better to disable such parsing logic for email messages altogether or at least filter/quote and such occurrences in ticket titles so that they are not parsed. Thanks. ---------- messages: 3394 nosy: lemburg priority: bug status: unread title: Problem with email replies for tickets which use [...] in the subject _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Sep 22 21:24:44 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Sat, 23 Sep 2017 01:24:44 +0000 Subject: [Tracker-discuss] [issue640] Problem with email replies for tickets which use [...] in the subject In-Reply-To: <1505979108.02.0.195706139994.issue640@psf.upfronthosting.co.za> Message-ID: <1506129884.74.0.276390721111.issue640@psf.upfronthosting.co.za> 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 -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Sep 25 15:10:31 2017 From: metatracker at psf.upfronthosting.co.za (Viktor Kovtun) Date: Mon, 25 Sep 2017 19:10:31 +0000 Subject: [Tracker-discuss] [issue641] Can not finish CLA agreement Message-ID: <1506366631.83.0.889360053354.issue641@psf.upfronthosting.co.za> New submission from Viktor Kovtun: 3 days ago 2017-09-22 I've created as issue on https://bugs.python.org/issue31556 then submitted pull request https://github.com/python/cpython/pull/3703 as well filled CLA agreement via Adobe Sign, but after 3 days it seems I've haven't been verified yet. I am not sure is right place to put this issue. Sorry if I missed something. I can attach PDF version of agreement if needed. Thanks for understanding! ---------- messages: 3396 nosy: hellysmile priority: wish status: unread title: Can not finish CLA agreement _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Mon Sep 25 18:29:00 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Mon, 25 Sep 2017 22:29:00 +0000 Subject: [Tracker-discuss] [issue641] Can not finish CLA agreement In-Reply-To: <1506366631.83.0.889360053354.issue641@psf.upfronthosting.co.za> Message-ID: <1506378540.19.0.0348256870551.issue641@psf.upfronthosting.co.za> 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 nosy: +ezio.melotti status: unread -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Sep 26 22:25:38 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 27 Sep 2017 02:25:38 +0000 Subject: [Tracker-discuss] [issue203] user pages should not show SHA1 hashes In-Reply-To: <1209072398.1.0.40054942592.issue203@psf.upfronthosting.co.za> Message-ID: <1506479138.25.0.964931712716.issue203@psf.upfronthosting.co.za> 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 Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Sep 26 22:27:14 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 27 Sep 2017 02:27:14 +0000 Subject: [Tracker-discuss] [issue203] user pages should not show SHA1 hashes In-Reply-To: <1209072398.1.0.40054942592.issue203@psf.upfronthosting.co.za> Message-ID: <1506479234.23.0.964931712716.issue203@psf.upfronthosting.co.za> Ezio Melotti added the comment: See https://hg.python.org/tracker/python-dev/rev/dec273514fa7 _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Sep 26 22:28:29 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 27 Sep 2017 02:28:29 +0000 Subject: [Tracker-discuss] [issue448] Cannot log into search results page In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za> Message-ID: <1506479309.12.0.964931712716.issue448@psf.upfronthosting.co.za> Ezio Melotti added the comment: This has been included in https://hg.python.org/tracker/python-dev/rev/182a21789df5 _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Sep 27 16:37:53 2017 From: metatracker at psf.upfronthosting.co.za (Oren Milman) Date: Wed, 27 Sep 2017 20:37:53 +0000 Subject: [Tracker-discuss] [issue642] meta issue: bugs.python.org search shows only issues with recent activity Message-ID: <1506544673.94.0.154975027568.issue642@psf.upfronthosting.co.za> New submission from Oren Milman : For example, when I search for 'ctypes', I get only two results. Just in case, i checked and got the same results in multiple browsers, and also on Ubuntu and on Windows. I am not 100% sure that issues are shown because they had a recent activity, but ISTM like the reason.. Also, i am not familiar with http://psf.upfronthosting.co.za, but ISTM that here also there is the same search problem. (note that i originally opened this issue in bpo - https://bugs.python.org/issue31605) ---------- messages: 3401 nosy: orenmn priority: critical status: unread title: meta issue: bugs.python.org search shows only issues with recent activity _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Sep 27 16:53:41 2017 From: metatracker at psf.upfronthosting.co.za (Oren Milman) Date: Wed, 27 Sep 2017 20:53:41 +0000 Subject: [Tracker-discuss] [issue642] meta issue: bugs.python.org search shows only issues with recent activity In-Reply-To: <1506544673.94.0.154975027568.issue642@psf.upfronthosting.co.za> Message-ID: <1506545621.34.0.273299129313.issue642@psf.upfronthosting.co.za> Oren Milman added the comment: ISTM that the issue was fixed in bpo, but not here in http://psf.upfronthosting.co.za... ---------- status: -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Sep 27 21:06:02 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Thu, 28 Sep 2017 01:06:02 +0000 Subject: [Tracker-discuss] [issue642] meta issue: bugs.python.org search shows only issues with recent activity In-Reply-To: <1506544673.94.0.154975027568.issue642@psf.upfronthosting.co.za> Message-ID: <1506560762.53.0.466225441844.issue642@psf.upfronthosting.co.za> 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 affect config.ini.template, since the config.ini are not under version control. I modified manually the config.ini on all the instances (including the meta instance). ---------- assignedto: -> ezio.melotti nosy: +ezio.melotti status: chatting -> resolved _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Sep 27 21:23:35 2017 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Thu, 28 Sep 2017 01:23:35 +0000 Subject: [Tracker-discuss] [issue448] Cannot log into search results page In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za> Message-ID: <1506561815.9.0.466225441844.issue448@psf.upfronthosting.co.za> 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 _______________________________________________________