From metatracker at psf.upfronthosting.co.za Thu Nov 1 23:03:02 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Thu, 01 Nov 2007 22:03:02 -0000 Subject: [Tracker-discuss] [issue149] 1523853 was not converted Message-ID: <1193954582.57.0.489281625934.issue149@psf.upfronthosting.co.za> Martin v. L?wis added the comment: It appears that SF has now fixed their exporter. I've done an export, and computed a list of items that are in SF, but not in roundup (according to export_csv). This list has 432 items, and is attached. It would be good if these missing items could be imported soon. Please let me know what if any help would be useful. ---------- priority: bug -> urgent _______________________________________________________ Meta Tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: missing Type: application/octet-stream Size: 3289 bytes Desc: not available Url : http://mail.python.org/pipermail/tracker-discuss/attachments/20071101/cccac0e6/attachment.obj From metatracker at psf.upfronthosting.co.za Fri Nov 2 20:37:43 2007 From: metatracker at psf.upfronthosting.co.za (Georg Brandl) Date: Fri, 02 Nov 2007 19:37:43 -0000 Subject: [Tracker-discuss] [issue166] document user roles Message-ID: <1194032263.5.0.875018203025.issue166@psf.upfronthosting.co.za> New submission from Georg Brandl: See http://bugs.python.org/msg57026 -- I know that there is a User, a Developer and a Coordinator role, but I don't know exactly what the rights for each role are. Can someone document them somewhere? ---------- messages: 843 nosy: gbrandl priority: urgent status: unread title: document user roles _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Nov 2 20:59:21 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Fri, 02 Nov 2007 19:59:21 -0000 Subject: [Tracker-discuss] [issue166] document user roles Message-ID: <1194033561.22.0.197011083092.issue166@psf.upfronthosting.co.za> Martin v. L?wis added the comment: Notice that this information is not secret; anybody could create that information, form the sources at http://svn.python.org/projects/tracker/instances/python-dev/schema.py ---------- status: unread -> chatting _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Nov 2 21:53:24 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Fri, 02 Nov 2007 20:53:24 -0000 Subject: [Tracker-discuss] [issue166] document user roles Message-ID: <1194036804.07.0.886418279198.issue166@psf.upfronthosting.co.za> Martin v. L?wis added the comment: I just created http://wiki.python.org/moin/TrackerAccessControl which summarizes all access control in a table; I hope I didn't mess it up somehow. _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Nov 2 23:11:37 2007 From: metatracker at psf.upfronthosting.co.za (Georg Brandl) Date: Fri, 02 Nov 2007 22:11:37 -0000 Subject: [Tracker-discuss] [issue166] document user roles Message-ID: <1194041497.53.0.867269911664.issue166@psf.upfronthosting.co.za> Georg Brandl added the comment: Many thanks! _______________________________________________________ Meta Tracker _______________________________________________________ From izak at upfrontsystems.co.za Mon Nov 5 14:04:23 2007 From: izak at upfrontsystems.co.za (Izak Burger) Date: Mon, 05 Nov 2007 15:04:23 +0200 Subject: [Tracker-discuss] Hardware reset Message-ID: <472F14D7.10500@upfrontsystems.co.za> Hi all, This is a message to notify you that the machine that the tracker runs on went down earlier this morning. We were left with no other option but to perform a hardware reset. Everything seems to be in order after the reboot. The only evidence is an enormous amount of interrupts from the hard drive controller along with a sharp drop in inode usage right before she went down. No kernel oopses, nothing in the log. We'll keep an eye on it. regards, Izak From seefeld at sympatico.ca Mon Nov 5 17:54:04 2007 From: seefeld at sympatico.ca (Stefan Seefeld) Date: Mon, 05 Nov 2007 11:54:04 -0500 Subject: [Tracker-discuss] issue tracker for Roundup (the project) itself ? Message-ID: <472F4AAC.2070503@sympatico.ca> Hello, in the early phase of the new-tracker-for-python.org work, we talked about the possibility to host the Roundup project's own issue tracker on the same machine as python.org's tracker. Is this still an option ? If so, what would be the next steps ? Thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin... From roche at upfrontsystems.co.za Mon Nov 5 18:34:04 2007 From: roche at upfrontsystems.co.za (=?ISO-8859-1?Q?Roch=E9?= Compaan) Date: Mon, 05 Nov 2007 19:34:04 +0200 Subject: [Tracker-discuss] issue tracker for Roundup (the project) itself ? In-Reply-To: <472F4AAC.2070503@sympatico.ca> References: <472F4AAC.2070503@sympatico.ca> Message-ID: <1194284044.18060.9.camel@localhost> On Mon, 2007-11-05 at 11:54 -0500, Stefan Seefeld wrote: > Hello, > > in the early phase of the new-tracker-for-python.org work, we talked > about the possibility to host the Roundup project's own issue tracker on > the same machine as python.org's tracker. Is this still an option ? If > so, what would be the next steps ? If it depends on us as hosts, then yes! We would love to host Roundup tracker :-) The next steps would be to simply add another tracker instance and do the necessary configuration in Apache and Postfix. Shout if you need help or want us to do the initial setup. -- Roch? Compaan Upfront Systems http://www.upfrontsystems.co.za From martin at v.loewis.de Mon Nov 5 21:53:34 2007 From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=) Date: Mon, 05 Nov 2007 21:53:34 +0100 Subject: [Tracker-discuss] issue tracker for Roundup (the project) itself ? In-Reply-To: <1194284044.18060.9.camel@localhost> References: <472F4AAC.2070503@sympatico.ca> <1194284044.18060.9.camel@localhost> Message-ID: <472F82CE.3080602@v.loewis.de> > The next steps would be to simply add another tracker instance and do > the necessary configuration in Apache and Postfix. Shout if you need > help or want us to do the initial setup. There is also the DNS issue: what name should the tracker get? It would be certainly easy to call it http://psf.upfronthosting.co.za/something, if that's fine for roundup. If some other DNS name would be preferred, one would have to arrange that somehow (I don't think it should be available through bugs.python.org). Regards, Martin From martin at v.loewis.de Mon Nov 5 22:54:44 2007 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Mon, 05 Nov 2007 22:54:44 +0100 Subject: [Tracker-discuss] Hardware reset In-Reply-To: <472F14D7.10500@upfrontsystems.co.za> References: <472F14D7.10500@upfrontsystems.co.za> Message-ID: <472F9124.7010504@v.loewis.de> > This is a message to notify you that the machine that the tracker runs > on went down earlier this morning. We were left with no other option > but to perform a hardware reset. Everything seems to be in order after > the reboot. Thanks for the notice! Regards, Martin From forsberg at efod.se Tue Nov 6 07:24:08 2007 From: forsberg at efod.se (Erik Forsberg) Date: Tue, 6 Nov 2007 07:24:08 +0100 Subject: [Tracker-discuss] issue tracker for Roundup (the project) itself ? In-Reply-To: <1194284044.18060.9.camel@localhost> References: <472F4AAC.2070503@sympatico.ca> <1194284044.18060.9.camel@localhost> Message-ID: <20071106072408.50309bfb@uterus> On Mon, 05 Nov 2007 19:34:04 +0200 Roch? Compaan wrote: > On Mon, 2007-11-05 at 11:54 -0500, Stefan Seefeld wrote: > > Hello, > > > > in the early phase of the new-tracker-for-python.org work, we talked > > about the possibility to host the Roundup project's own issue > > tracker on the same machine as python.org's tracker. Is this still > > an option ? If so, what would be the next steps ? > > If it depends on us as hosts, then yes! We would love to host Roundup > tracker :-) > > The next steps would be to simply add another tracker instance and do > the necessary configuration in Apache and Postfix. Shout if you need > help or want us to do the initial setup. I have some thoughts on separation of tracker instances for security and stability reasons, but apart from that, I would also enjoy if roundup could get its own tracker! I'd like each tracker to run as its own user, for two main reasons: 1) Security. Breakin to one tracker due to misconfiguration or perhaps badly written detector should not affect other trackers. 2) More important: Stability of one tracker should not be affected because someone makes a mistake for another tracker. A 'rm -rf' in the wrong place can cause so much wasted time. With tracker permissions separated, we can have "per tracker admins" that don't have the ability to destroy for example bugs.python.org. I also see it as neccesary that all trackers run the same anti-spam measures as bugs.python.org and the meta tracker. One tracker should not be able to get the IP of psf.upfronthosting.co.za blacklisted. Just as we can run a central postgresql instance, we can run a central spambayes XMLRPC server instance. To summarize - I think hosting a tracker for roundup itself is a great idea, and I hope someone can do the actual schema/template/import work. I'm willing to help with the setup of the tracker/apache/user separation, etc, once we have a working tracker instance. Regards, \EF -- Erik Forsberg http://efod.se GPG/PGP Key: 1024D/0BAC89D9 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://mail.python.org/pipermail/tracker-discuss/attachments/20071106/c272dea6/attachment.pgp From forsberg at efod.se Tue Nov 6 07:25:00 2007 From: forsberg at efod.se (Erik Forsberg) Date: Tue, 6 Nov 2007 07:25:00 +0100 Subject: [Tracker-discuss] issue tracker for Roundup (the project) itself ? In-Reply-To: <472F82CE.3080602@v.loewis.de> References: <472F4AAC.2070503@sympatico.ca> <1194284044.18060.9.camel@localhost> <472F82CE.3080602@v.loewis.de> Message-ID: <20071106072500.39131e40@uterus> > (I don't think it should be available through > bugs.python.org). I agree. \EF -- Erik Forsberg http://efod.se GPG/PGP Key: 1024D/0BAC89D9 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://mail.python.org/pipermail/tracker-discuss/attachments/20071106/5b137075/attachment.pgp From izak at upfrontsystems.co.za Tue Nov 6 08:09:43 2007 From: izak at upfrontsystems.co.za (Izak Burger) Date: Tue, 06 Nov 2007 09:09:43 +0200 Subject: [Tracker-discuss] issue tracker for Roundup (the project) itself ? In-Reply-To: <20071106072408.50309bfb@uterus> References: <472F4AAC.2070503@sympatico.ca> <1194284044.18060.9.camel@localhost> <20071106072408.50309bfb@uterus> Message-ID: <47301337.7030909@upfrontsystems.co.za> Erik Forsberg wrote: > I also see it as neccesary that all trackers run the same anti-spam > measures as bugs.python.org and the meta tracker. One tracker should > not be able to get the IP of psf.upfronthosting.co.za blacklisted. Just > as we can run a central postgresql instance, we can run a central > spambayes XMLRPC server instance. It is easy to bind another ip to the same virtual host. What I am unsure about is how you'd tell postfix to bind to a specific ip when it sends mail for a specific domain. This is the difficult bit, as the ip you connect FROM is the one that gets blacklisted, so it is not as simple as just pointing the MX records at the right ip. Some research is required in this department. Everything else seems in order though. We can simply run the new tracker as a different user in a different home directory. The apache bit will still run as www-data though, but it will forward to the correct roundup-server instance of course. I doubt this will be a problem, apache is really very very stable. regards, Izak From martin at v.loewis.de Tue Nov 6 18:55:24 2007 From: martin at v.loewis.de (=?ISO-8859-15?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Tue, 06 Nov 2007 18:55:24 +0100 Subject: [Tracker-discuss] issue tracker for Roundup (the project) itself ? In-Reply-To: <20071106072408.50309bfb@uterus> References: <472F4AAC.2070503@sympatico.ca> <1194284044.18060.9.camel@localhost> <20071106072408.50309bfb@uterus> Message-ID: <4730AA8C.5060209@v.loewis.de> > To summarize - I think hosting a tracker for roundup itself is a great > idea, and I hope someone can do the actual schema/template/import work. > I'm willing to help with the setup of the tracker/apache/user > separation, etc, once we have a working tracker instance. In case it isn't clear: if people want to check in this instance into the same subversion repository that holds the Python instance - that's fine with me. Let me know, and I'll provide subversion access to anybody who needs to work on it. Regards, Martin From metatracker at psf.upfronthosting.co.za Fri Nov 9 17:47:38 2007 From: metatracker at psf.upfronthosting.co.za (Christian Heimes) Date: Fri, 09 Nov 2007 16:47:38 -0000 Subject: [Tracker-discuss] [issue167] Added resolution keyword "confirmed" Message-ID: <1194626858.37.0.770894714995.issue167@psf.upfronthosting.co.za> New submission from Christian Heimes: Please add a new keyword "confirmed" to the list of resolutions. Guido just explained to me that "accepted" means that the patch is accepted. I like to have a flag to show other developers that somebody has verified the existence of a bug. ---------- messages: 847 nosy: tiran priority: feature status: unread title: Added resolution keyword "confirmed" _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Nov 9 18:09:30 2007 From: metatracker at psf.upfronthosting.co.za (Georg Brandl) Date: Fri, 09 Nov 2007 17:09:30 -0000 Subject: [Tracker-discuss] [issue167] Added resolution keyword "confirmed" Message-ID: <1194628170.17.0.834833235363.issue167@psf.upfronthosting.co.za> Georg Brandl added the comment: The question is if this isn't a status instead of a resolution... ---------- status: unread -> chatting _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Nov 9 18:11:30 2007 From: metatracker at psf.upfronthosting.co.za (Georg Brandl) Date: Fri, 09 Nov 2007 17:11:30 -0000 Subject: [Tracker-discuss] [issue167] Added resolution keyword "confirmed" Message-ID: <1194628290.05.0.651133304455.issue167@psf.upfronthosting.co.za> Georg Brandl added the comment: (rationale: a bug can't be "closed - confirmed"). _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Nov 9 18:15:00 2007 From: metatracker at psf.upfronthosting.co.za (Christian Heimes) Date: Fri, 09 Nov 2007 17:15:00 -0000 Subject: [Tracker-discuss] [issue167] Added resolution keyword "confirmed" Message-ID: <1194628500.21.0.484488535638.issue167@psf.upfronthosting.co.za> Christian Heimes added the comment: Oh ... good point :) Yeah, it makes more sense to add it to "status" than to resolution. On the other hand it makes it harder to search for open and confirmed bugs. If you are going to add confirmed to status then the default view should be changed from open to not closed, too. _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Nov 22 00:52:15 2007 From: metatracker at psf.upfronthosting.co.za (Paul Moore) Date: Wed, 21 Nov 2007 23:52:15 -0000 Subject: [Tracker-discuss] [issue168] Tracker summary emails are arriving daily Message-ID: <1195689135.62.0.321021656301.issue168@psf.upfronthosting.co.za> New submission from Paul Moore: The tracker summary emails sent to the python-dev list are being sent daily, even though they contain a week's worth of summary data. They should be changed to be sent daily. ---------- messages: 851 nosy: pmoore priority: bug status: unread title: Tracker summary emails are arriving daily _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Nov 22 01:08:01 2007 From: metatracker at psf.upfronthosting.co.za (Paul Dubois) Date: Thu, 22 Nov 2007 00:08:01 -0000 Subject: [Tracker-discuss] [issue168] Tracker summary emails are arriving daily Message-ID: <1195690081.19.0.464259246311.issue168@psf.upfronthosting.co.za> Paul Dubois added the comment: Someone had changed the cron table I guess. I fixed it back to day "5" instead of "*". I had not noticed this since the line that sends one to *me* was not changed. ---------- assignedto: -> dubois nosy: +dubois status: unread -> resolved _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Thu Nov 22 13:59:24 2007 From: metatracker at psf.upfronthosting.co.za (Erik Forsberg) Date: Thu, 22 Nov 2007 12:59:24 -0000 Subject: [Tracker-discuss] [issue168] Tracker summary emails are arriving daily In-Reply-To: <1195690081.19.0.464259246311.issue168@psf.upfronthosting.co.za> Message-ID: <20071122135916.056ddd88@impertigo.lkpg.cendio.se> Erik Forsberg added the comment: On Thu, 22 Nov 2007 00:08:01 -0000 Paul Dubois wrote: > > Paul Dubois added the comment: > > Someone had changed the cron table I guess. I fixed it back to day > "5" instead of "*". I had not noticed this since the line that sends > one to *me* was not changed. *Waving a flag that says "guilty!"* I changed the cron entry while trying to figure out why the messages didn't get through. My intention was to restore it later, but I seem to have forgotten that. Regards \EF -- Erik Forsberg http://efod.se GPG/PGP Key: 1024D/0BAC89D9 _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Nov 23 15:53:40 2007 From: metatracker at psf.upfronthosting.co.za (Georg Brandl) Date: Fri, 23 Nov 2007 14:53:40 -0000 Subject: [Tracker-discuss] [issue149] 1523853 was not converted Message-ID: <1195829620.26.0.419506439209.issue149@psf.upfronthosting.co.za> Georg Brandl added the comment: Is there any progress on this? How many of the lost issues were still open? _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Nov 23 19:19:44 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Fri, 23 Nov 2007 18:19:44 -0000 Subject: [Tracker-discuss] [issue149] 1523853 was not converted Message-ID: <1195841984.64.0.304726051618.issue149@psf.upfronthosting.co.za> Martin v. L?wis added the comment: No progress, AFAICT. Somebody would have to do the export again, and then import all issues that are listed in my missing file (or validate that missing file directly against the database first). I could do the export again, but I see little point in doing so if there is no commitment to then also add the missing reports. _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue Nov 27 19:35:31 2007 From: metatracker at psf.upfronthosting.co.za (Guido van Rossum) Date: Tue, 27 Nov 2007 18:35:31 -0000 Subject: [Tracker-discuss] [issue169] Improve gmail interaction Message-ID: <1196188531.28.0.84959205083.issue169@psf.upfronthosting.co.za> New submission from Guido van Rossum: I love the email integration of the bug tracker! But I also love gmail. There are two issues with the email from the bug tracker in gmail: (a) Threading doesn't always work. I believe that in order to make it work, you should use an in-reply-to header listing the message-id of at least one previous message in the thread. (b) When threading *does* work, in gmail's Inbox display, it looks like all messages were sent by the first author in the thread. This is because the tracker uses the same email address (reports at bugs.python.org) for all email it sends, only varying the "real name" part. Somehow the inbox decides that all mail from the same email address comes from the same real name. (Usually a fair assumption. :-) A solution for this might be to use the username as the email address, or if that's too complicated, perhaps something like reports+@bugs.python.org. (Many MTAs these days have support for funneling all mail to x+y at domain to x at domain, making this an attractive solution.) ---------- messages: 856 nosy: guido priority: feature status: unread title: Improve gmail interaction _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Nov 28 00:00:25 2007 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=) Date: Tue, 27 Nov 2007 23:00:25 -0000 Subject: [Tracker-discuss] [issue169] Improve gmail interaction Message-ID: <1196204425.49.0.46861003351.issue169@psf.upfronthosting.co.za> Martin v. L?wis added the comment: If you follow up through the web interface (which I do here right now), what in-reply-to message ID would you like to see in this message (assuming there had been several messages already submitted for this issue)? Should it perhaps prefer References: over In-reply-to:? ---------- status: unread -> chatting _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Nov 28 00:09:10 2007 From: metatracker at psf.upfronthosting.co.za (Guido van Rossum) Date: Tue, 27 Nov 2007 23:09:10 -0000 Subject: [Tracker-discuss] [issue169] Improve gmail interaction In-Reply-To: <1196204425.49.0.46861003351.issue169@psf.upfronthosting.co.za> Message-ID: Guido van Rossum added the comment: > If you follow up through the web interface (which I do here right now), what > in-reply-to message ID would you like to see in this message (assuming there had > been several messages already submitted for this issue)? Should it perhaps > prefer References: over In-reply-to:? Any one will do, so the last one would be fine -- or the first one. Gmail doesn't have a tree structure to the conversation, though other MUAs might. I'm unclear on the difference between References: and In-reply-to:; I suspect either would work. I know In-reply-to works because I used it before for this purpose. :-) _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed Nov 28 00:29:17 2007 From: metatracker at psf.upfronthosting.co.za (Georg Brandl) Date: Tue, 27 Nov 2007 23:29:17 -0000 Subject: [Tracker-discuss] [issue169] Improve gmail interaction In-Reply-To: Message-ID: <474CA8B6.308@python.org> Georg Brandl added the comment: Guido van Rossum schrieb: > Guido van Rossum added the comment: > >> If you follow up through the web interface (which I do here right now), what >> in-reply-to message ID would you like to see in this message (assuming there had >> been several messages already submitted for this issue)? Should it perhaps >> prefer References: over In-reply-to:? > > Any one will do, so the last one would be fine -- or the first one. > Gmail doesn't have a tree structure to the conversation, though other > MUAs might. In Thunderbird, I see comments sent by mail interface threaded under the comment in response to which the response was sent, and comments submitted through the web interface listed under the OP. That may be as good as it can get. Georg _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Nov 30 20:26:28 2007 From: metatracker at psf.upfronthosting.co.za (Guido van Rossum) Date: Fri, 30 Nov 2007 19:26:28 -0000 Subject: [Tracker-discuss] [issue170] Pagination sticks around when switching queries Message-ID: <1196450788.02.0.796545566766.issue170@psf.upfronthosting.co.za> New submission from Guido van Rossum: When I'm on page 2 of my "py3k" query and then click on "My issues" I am shown "page 2" of my issues (even though there really is only one page worth of issues in that query). I don't know if the pagination uses cookies or a URL parameter but this is clearly wrong. ---------- messages: 860 nosy: guido priority: bug status: unread title: Pagination sticks around when switching queries _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Nov 30 20:48:36 2007 From: metatracker at psf.upfronthosting.co.za (Erik Forsberg) Date: Fri, 30 Nov 2007 19:48:36 -0000 Subject: [Tracker-discuss] [issue170] Pagination sticks around when switching queries In-Reply-To: <1196450788.02.0.796545566766.issue170@psf.upfronthosting.co.za> Message-ID: <20071130204758.164c9022@uterus> Erik Forsberg added the comment: On Fri, 30 Nov 2007 19:26:28 -0000 Guido van Rossum wrote: > > New submission from Guido van Rossum: > > When I'm on page 2 of my "py3k" query and then click on "My issues" I > am shown "page 2" of my issues (even though there really is only one > page worth of issues in that query). I don't know if the pagination > uses cookies or a URL parameter but this is clearly wrong. Could you copy-paste 1) The URL you reference as being your "page 2 of my py3k query" 2) The URL that the link "My issues" link to. 3) The URL you end up on when you've clicked "my issues". ? Regards, \EF -- Erik Forsberg http://efod.se GPG/PGP Key: 1024D/0BAC89D9 ---------- status: unread -> chatting _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Nov 30 20:54:05 2007 From: metatracker at psf.upfronthosting.co.za (Guido van Rossum) Date: Fri, 30 Nov 2007 19:54:05 -0000 Subject: [Tracker-discuss] [issue170] Pagination sticks around when switching queries In-Reply-To: <20071130204758.164c9022@uterus> Message-ID: Guido van Rossum added the comment: (1) http://bugs.python.org/issue?@startwith=50&@pagesize=50&@columns=title,id,creator,activity,assignee,priority&@sort=-activity&@group=priority&@filter=versions,status&status=1&versions=12 (2) http://bugs.python.org/issue?status=-1,1,3&@sort=-activity&@search_text=&@dispname=Your%20Issues&@filter=status,assignee&@group=priority&@columns=id,activity,title,creator,status&assignee=5&@pagesize=50&@startwith=0 (3) http://bugs.python.org/issue?status=-1,1,3&@sort=-activity&@search_text=&@dispname=Your%20Issues&@filter=status,assignee&@group=priority&@columns=id,activity,title,creator,status&assignee=5&@pagesize=50&@startwith=50&versions=12 On Nov 30, 2007 11:48 AM, Erik Forsberg wrote: > > Erik Forsberg added the comment: > > On Fri, 30 Nov 2007 19:26:28 -0000 > Guido van Rossum wrote: > > > > > New submission from Guido van Rossum: > > > > When I'm on page 2 of my "py3k" query and then click on "My issues" I > > am shown "page 2" of my issues (even though there really is only one > > page worth of issues in that query). I don't know if the pagination > > uses cookies or a URL parameter but this is clearly wrong. > > Could you copy-paste > > 1) The URL you reference as being your "page 2 of my py3k query" > > 2) The URL that the link "My issues" link to. > > 3) The URL you end up on when you've clicked "my issues". > > ? > > Regards, > \EF > -- > Erik Forsberg http://efod.se > GPG/PGP Key: 1024D/0BAC89D9 > > ---------- > status: unread -> chatting > > > _______________________________________________________ > Meta Tracker > > _______________________________________________________ > _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Nov 30 21:33:28 2007 From: metatracker at psf.upfronthosting.co.za (Erik Forsberg) Date: Fri, 30 Nov 2007 20:33:28 -0000 Subject: [Tracker-discuss] [issue170] Pagination sticks around when switching queries In-Reply-To: Message-ID: <20071130213251.21be694a@uterus> Erik Forsberg added the comment: On Fri, 30 Nov 2007 19:54:05 -0000 Guido van Rossum wrote: > > Guido van Rossum added the comment: > > (1) > http://bugs.python.org/issue?@startwith=50&@pagesize=50&@columns=title,id,creator,activity,assignee,priority&@sort=-activity&@group=priority&@filter=versions,status&status=1&versions=12 > > (2) > http://bugs.python.org/issue?status=-1,1,3&@sort=-activity&@search_text=&@dispname=Your%20Issues&@filter=status,assignee&@group=priority&@columns=id,activity,title,creator,status&assignee=5&@pagesize=50&@startwith=0 > > (3) > http://bugs.python.org/issue?status=-1,1,3&@sort=-activity&@search_text=&@dispname=Your%20Issues&@filter=status,assignee&@group=priority&@columns=id,activity,title,creator,status&assignee=5&@pagesize=50&@startwith=50&versions=12 Oookay.. that's.. ODD! As we can see when looking for differences between 2) and 3), 2) has a startwith=0, and 3) has a startwith=50, which is the cause of the effect. If I click 2), I end up at 2), not at 3). What browser are you using? Could you try a different one? Regards, \EF -- Erik Forsberg http://efod.se GPG/PGP Key: 1024D/0BAC89D9 _______________________________________________________ Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri Nov 30 21:46:39 2007 From: metatracker at psf.upfronthosting.co.za (Guido van Rossum) Date: Fri, 30 Nov 2007 20:46:39 -0000 Subject: [Tracker-discuss] [issue170] Pagination sticks around when switching queries In-Reply-To: <20071130213251.21be694a@uterus> Message-ID: Guido van Rossum added the comment: This happens both on Firefox and on Safari. So I doubt it's the browser. _______________________________________________________ Meta Tracker _______________________________________________________