From metatracker at psf.upfronthosting.co.za Tue May 4 12:50:10 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=) Date: Tue, 04 May 2010 10:50:10 +0000 Subject: [Tracker-discuss] [issue337] Support any OPenID provider In-Reply-To: <1272970210.59.0.790870688738.issue337@psf.upfronthosting.co.za> Message-ID: <1272970210.59.0.790870688738.issue337@psf.upfronthosting.co.za> New submission from Jes?s Cea Avi?n : Please, support arbitrary OpenID providers in the python bug tracker. For discussi?n about this issue, check http://www.mail-archive.com/catalog-sig at python.org/msg01847.html , http://mail.python.org/pipermail/catalog-sig/2009-November/002308.html threads, and other messages in the catalog-sig archive. ---------- messages: 1653 nosy: jcea priority: feature status: unread title: Support any OPenID provider _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 4 14:36:54 2010 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Tue, 04 May 2010 12:36:54 +0000 Subject: [Tracker-discuss] [issue337] Support any OpenID provider In-Reply-To: <1272970210.59.0.790870688738.issue337@psf.upfronthosting.co.za> Message-ID: <1272976614.63.0.389207639843.issue337@psf.upfronthosting.co.za> R David Murray added the comment: Martin can correct me if I'm wrong, but I believe he has said before that any OpenID provider (that adheres to the spec) should be supported. What error are you seeing? ---------- nosy: +r.david.murray status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 4 18:38:37 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=) Date: Tue, 04 May 2010 16:38:37 +0000 Subject: [Tracker-discuss] [issue337] Support any OpenID provider In-Reply-To: <1272970210.59.0.790870688738.issue337@psf.upfronthosting.co.za> Message-ID: <1272991117.16.0.773491404409.issue337@psf.upfronthosting.co.za> Jes?s Cea Avi?n added the comment: OK, now it works. I am puzzled. Sorry for wasting your time. Anyway, we need to indicate "someway" that you can put any OpenID URL in the "username", beside clicking on the recommended provider icons. Shoudl I open a new bug?. ---------- status: chatting -> unread _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 4 18:44:00 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=) Date: Tue, 04 May 2010 16:44:00 +0000 Subject: [Tracker-discuss] [issue337] Support any OpenID provider In-Reply-To: <1272970210.59.0.790870688738.issue337@psf.upfronthosting.co.za> Message-ID: <1272991440.9.0.144024255908.issue337@psf.upfronthosting.co.za> Jes?s Cea Avi?n added the comment: I must remember to to shif+reload in the browser. Reload seems not to be enough :-? ---------- status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 4 19:07:16 2010 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Tue, 04 May 2010 17:07:16 +0000 Subject: [Tracker-discuss] [issue337] Support any OpenID provider In-Reply-To: <1272970210.59.0.790870688738.issue337@psf.upfronthosting.co.za> Message-ID: <1272992836.55.0.869953721993.issue337@psf.upfronthosting.co.za> R David Murray added the comment: I don't understand. I'm using one of the standard providers, but through my own URL. I just type my URL into the login box, hit enter, and it logs me in. _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 4 19:17:58 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=) Date: Tue, 04 May 2010 17:17:58 +0000 Subject: [Tracker-discuss] [issue337] Support any OpenID provider In-Reply-To: <1272970210.59.0.790870688738.issue337@psf.upfronthosting.co.za> Message-ID: <1272993478.72.0.513627209207.issue337@psf.upfronthosting.co.za> Jes?s Cea Avi?n added the comment: And how do you know you can write the URL in the login box?. Intuition? :) _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 4 20:30:08 2010 From: metatracker at psf.upfronthosting.co.za (R David Murray) Date: Tue, 04 May 2010 18:30:08 +0000 Subject: [Tracker-discuss] [issue337] Support any OpenID provider In-Reply-To: <1272970210.59.0.790870688738.issue337@psf.upfronthosting.co.za> Message-ID: <1272997808.95.0.627978121376.issue337@psf.upfronthosting.co.za> R David Murray added the comment: I suppose. The openid is a login id, so I just assumed that the correct place to put it was in the userid box. That assumption is so strongly embedded in my brain that I didn't understand that your message was asking to make it clear that this worked; I thought you were saying that it didn't work :) Clearly, however, it isn't a universally intuitive interface. Do you have a suggestion for how to improve the interface so that this is clearer? _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 4 22:42:10 2010 From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=) Date: Tue, 04 May 2010 20:42:10 +0000 Subject: [Tracker-discuss] [issue337] Support any OpenID provider In-Reply-To: <1272970210.59.0.790870688738.issue337@psf.upfronthosting.co.za> Message-ID: <1273005730.65.0.869571243578.issue337@psf.upfronthosting.co.za> Martin v. L?wis added the comment: bugs.python.org uses the attribute name="openid_identifier" for the username field. According to the OpenID spec, this is the official way of indicating (to the browser) that this is the field where the OpenID should be entered. If your browser supports OpenID, it will know to fill the form automatically (but I understand that few browsers actually do support that API). As a further visual clue, putting an OpenID favicon next the login box might help. If so: what icon URL? left or right? ---------- nosy: +loewis _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Tue May 4 22:59:34 2010 From: metatracker at psf.upfronthosting.co.za (Eric Smith) Date: Tue, 04 May 2010 20:59:34 +0000 Subject: [Tracker-discuss] [issue337] Support any OpenID provider In-Reply-To: <1272970210.59.0.790870688738.issue337@psf.upfronthosting.co.za> Message-ID: <1273006774.61.0.985148631961.issue337@psf.upfronthosting.co.za> Eric Smith added the comment: Looks like: http://wiki.openid.net/f/openid-16x16.gif which I got from: http://openid.net/foundation/news/logos/ It's not clear if they'd like you to use these directly, or copy them locally. No preference left or right. ---------- nosy: +eric.smith _______________________________________________________ PSF Meta Tracker _______________________________________________________ From gareth at upfrontsystems.co.za Wed May 12 17:14:06 2010 From: gareth at upfrontsystems.co.za (Gareth Allen) Date: Wed, 12 May 2010 17:14:06 +0200 Subject: [Tracker-discuss] PSF tracker causing heavy load Message-ID: <4BEAC5BE.2010306@upfrontsystems.co.za> Hi there, I have noticed that the roundup tracker is causing heavy load on the psf server. Would it be possible for someone who has access to the server to please take a look. Regards,, -- Gareth Allen Upfront Systems e-mail: gareth at upfrontsystems.co.za ph: +2721 880 2264/5 fax: +2721 880 1724 From rdmurray at bitdance.com Wed May 12 17:54:12 2010 From: rdmurray at bitdance.com (R. David Murray) Date: Wed, 12 May 2010 11:54:12 -0400 Subject: [Tracker-discuss] PSF tracker causing heavy load In-Reply-To: <4BEAC5BE.2010306@upfrontsystems.co.za> References: <4BEAC5BE.2010306@upfrontsystems.co.za> Message-ID: <20100512155412.683F9209894@kimball.webabinitio.net> On Wed, 12 May 2010 17:14:06 +0200, Gareth Allen wrote: > I have noticed that the roundup tracker is causing heavy load on the psf > server. Would it be possible for someone who has access to the server > to please take a look. I've been taking a look, but have so far been unable to identify anything triggering the load. It seems to come in bursts, and when it does, a bunch of roundup processes accumulate while the requests are dealt with, and the postgres CPU use goes up as well. I started a script to find the start of a spike so I can try to correlate it with events in the logs, but haven't been able to get a responsive enough shell to look at the results yet :) On thing that would at least cut down on the load on roundup (based on my perusing of the access logs) would be to block the msnbot temporarily. --David From rdmurray at bitdance.com Wed May 12 19:15:27 2010 From: rdmurray at bitdance.com (R. David Murray) Date: Wed, 12 May 2010 13:15:27 -0400 Subject: [Tracker-discuss] PSF tracker causing heavy load In-Reply-To: <20100512155412.683F9209894@kimball.webabinitio.net> References: <4BEAC5BE.2010306@upfrontsystems.co.za> <20100512155412.683F9209894@kimball.webabinitio.net> Message-ID: <20100512171527.A6F5520034D@kimball.webabinitio.net> Restarting roundup seems to have calmed things down for now. I haven't found any obvious correlation in the access logs with the load up-tick. On Wed, 12 May 2010 11:54:12 -0400, "R. David Murray" wrote: > On thing that would at least cut down on the load on roundup (based > on my perusing of the access logs) would be to block the msnbot temporarily. Looks like that was a red herring. Roundup was hit with a much more intense barrage of requests to the python tracker and the load maxed out at about 8. Then, a little after that barrage stopped, the load shot up to 50. --David From techtonik at gmail.com Wed May 12 19:18:58 2010 From: techtonik at gmail.com (anatoly techtonik) Date: Wed, 12 May 2010 20:18:58 +0300 Subject: [Tracker-discuss] PSF tracker causing heavy load In-Reply-To: <20100512155412.683F9209894@kimball.webabinitio.net> References: <4BEAC5BE.2010306@upfrontsystems.co.za> <20100512155412.683F9209894@kimball.webabinitio.net> Message-ID: On Wed, May 12, 2010 at 6:54 PM, R. David Murray wrote: > > I've been taking a look, but have so far been unable to identify anything > triggering the load. ?It seems to come in bursts, and when it does, a > bunch of roundup processes accumulate while the requests are dealt with, > and the postgres CPU use goes up as well. > > I started a script to find the start of a spike so I can try to correlate > it with events in the logs, but haven't been able to get a responsive > enough shell to look at the results yet :) Add timestamps to logs. I guess there is some monitoring tool that lists time of spikes as well. Is there any? Then map spikes to search queries at this time. I guess roundup doesn't have multilevel logging to turn on tracing of search queries and their time profiles, and dump them to separate file or socket. > On thing that would at least cut down on the load on roundup (based > on my perusing of the access logs) would be to block the msnbot temporarily. -- anatoly t. From martin at v.loewis.de Wed May 12 19:32:33 2010 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Wed, 12 May 2010 19:32:33 +0200 Subject: [Tracker-discuss] PSF tracker causing heavy load In-Reply-To: <4BEAC5BE.2010306@upfrontsystems.co.za> References: <4BEAC5BE.2010306@upfrontsystems.co.za> Message-ID: <4BEAE631.3000701@v.loewis.de> > I have noticed that the roundup tracker is causing heavy load on the psf > server. You do have access also, don't you? If not, you should (IMO). In any case, I put a robots exclusion file on the trackers. Regards, Martin From techtonik at gmail.com Wed May 12 20:23:02 2010 From: techtonik at gmail.com (anatoly techtonik) Date: Wed, 12 May 2010 21:23:02 +0300 Subject: [Tracker-discuss] PSF tracker causing heavy load In-Reply-To: <4BEAE631.3000701@v.loewis.de> References: <4BEAC5BE.2010306@upfrontsystems.co.za> <4BEAE631.3000701@v.loewis.de> Message-ID: On Wed, May 12, 2010 at 8:32 PM, "Martin v. L?wis" wrote: >> I have noticed that the roundup tracker is causing heavy load on the psf >> server. > > You do have access also, don't you? If not, you should (IMO). > > In any case, I put a robots exclusion file on the trackers. Are you sure tracker issues should not be searchable by Google? Searching for specific stacktraces usually gives the best results in bug reports. -- anatoly t. From rdmurray at bitdance.com Wed May 12 20:45:27 2010 From: rdmurray at bitdance.com (R. David Murray) Date: Wed, 12 May 2010 14:45:27 -0400 Subject: [Tracker-discuss] PSF tracker causing heavy load In-Reply-To: References: <4BEAC5BE.2010306@upfrontsystems.co.za> <4BEAE631.3000701@v.loewis.de> Message-ID: <20100512184527.510D11BA997@kimball.webabinitio.net> On Wed, 12 May 2010 21:23:02 +0300, anatoly techtonik wrote: >On Wed, May 12, 2010 at 8:32 PM, "Martin v. L??wis" wrote: >>> I have noticed that the roundup tracker is causing heavy load on the psf >>> server. >> >> You do have access also, don't you? If not, you should (IMO). >> >> In any case, I put a robots exclusion file on the trackers. > >Are you sure tracker issues should not be searchable by Google? >Searching for specific stacktraces usually gives the best results in >bug reports. The new robots.txt file just tells the robots to slow down, not to stop. -- R. David Murray www.bitdance.com From techtonik at gmail.com Thu May 13 15:24:05 2010 From: techtonik at gmail.com (anatoly techtonik) Date: Thu, 13 May 2010 16:24:05 +0300 Subject: [Tracker-discuss] PSF tracker causing heavy load In-Reply-To: <20100512184527.510D11BA997@kimball.webabinitio.net> References: <4BEAC5BE.2010306@upfrontsystems.co.za> <4BEAE631.3000701@v.loewis.de> <20100512184527.510D11BA997@kimball.webabinitio.net> Message-ID: http://bugs.python.org/robots.txt User-agent: * Crawl-delay: 20 Cool. Didn't know that is possible. -- anatoly t. On Wed, May 12, 2010 at 9:45 PM, R. David Murray wrote: > On Wed, 12 May 2010 21:23:02 +0300, anatoly techtonik wrote: >>On Wed, May 12, 2010 at 8:32 PM, "Martin v. L?wis" wrote: >>>> I have noticed that the roundup tracker is causing heavy load on the psf >>>> server. >>> >>> You do have access also, don't you? If not, you should (IMO). >>> >>> In any case, I put a robots exclusion file on the trackers. >> >>Are you sure tracker issues should not be searchable by Google? >>Searching for specific stacktraces usually gives the best results in >>bug reports. > > The new robots.txt file just tells the robots to slow down, not to stop. > > -- > R. David Murray ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?www.bitdance.com > From techtonik at gmail.com Thu May 13 17:16:15 2010 From: techtonik at gmail.com (anatoly techtonik) Date: Thu, 13 May 2010 18:16:15 +0300 Subject: [Tracker-discuss] PSF tracker causing heavy load In-Reply-To: <20100512171527.A6F5520034D@kimball.webabinitio.net> References: <4BEAC5BE.2010306@upfrontsystems.co.za> <20100512155412.683F9209894@kimball.webabinitio.net> <20100512171527.A6F5520034D@kimball.webabinitio.net> Message-ID: On Wed, May 12, 2010 at 8:15 PM, R. David Murray wrote: > Restarting roundup seems to have calmed things down for now. ?I haven't > found any obvious correlation in the access logs with the load up-tick. Just hit it. Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Apache/2.2.9 (Debian) mod_python/3.3.1 Python/2.5.2 mod_ssl/2.2.9 OpenSSL/0.9.8g Server at bugs.python.org Port 80 From martin at v.loewis.de Fri May 14 20:01:20 2010 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Fri, 14 May 2010 20:01:20 +0200 Subject: [Tracker-discuss] Sorting and grouping by multilink properties disabled Message-ID: <4BED8FF0.4080401@v.loewis.de> While investigating the load hit on roundup, we found that Google somewhy issued queries that group by "nosy". "nosy" being a multilink property, the implementation is a really lame "download the entire database, sort in Python" approach. Therefore, I have disabled sorting and grouping by multilink properties. If that causes problems, please let me know. Regards, Martin From metatracker at psf.upfronthosting.co.za Thu May 20 23:08:06 2010 From: metatracker at psf.upfronthosting.co.za (Giampaolo Rodola') Date: Thu, 20 May 2010 21:08:06 +0000 Subject: [Tracker-discuss] [issue339] Colored sintax for quoted text In-Reply-To: <1274389686.18.0.834229227802.issue339@psf.upfronthosting.co.za> Message-ID: <1274389686.18.0.834229227802.issue339@psf.upfronthosting.co.za> New submission from Giampaolo Rodola' : A common habit on the bug tracker is quoting text written by other people who comments on the issue, as for e-mails. I think it would be more clear if such text had a different color. Toughs? ---------- messages: 1663 nosy: giampaolo.rodola priority: wish status: unread title: Colored sintax for quoted text _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Fri May 21 08:18:39 2010 From: metatracker at psf.upfronthosting.co.za (techtonik) Date: Fri, 21 May 2010 06:18:39 +0000 Subject: [Tracker-discuss] [issue339] Colored sintax for quoted text In-Reply-To: <1274389686.18.0.834229227802.issue339@psf.upfronthosting.co.za> Message-ID: <1274422719.22.0.709996531142.issue339@psf.upfronthosting.co.za> techtonik added the comment: I don't see quote button at all. ---------- nosy: +techtonik status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From gareth at upfrontsystems.co.za Tue May 25 13:06:08 2010 From: gareth at upfrontsystems.co.za (Gareth Allen) Date: Tue, 25 May 2010 13:06:08 +0200 Subject: [Tracker-discuss] backups Message-ID: <4BFBAF20.2050900@upfrontsystems.co.za> Hi, I'm busy tuning our backup system. I see that the trackers are exported to /home/roundup/backups on a daily basis. Please give me a list of directories, other than /home/roundup/backups, you would like backed up. Can a nightly pgdump be done? Unfortunately we can't backup the whole virtual server on a daily basis. Thanks, -- Gareth Allen Upfront Systems e-mail: gareth at upfrontsystems.co.za ph: +2721 880 2264/5 fax: +2721 880 1724 From metatracker at psf.upfronthosting.co.za Wed May 19 12:39:38 2010 From: metatracker at psf.upfronthosting.co.za (Sebastian Lopez Buritica) Date: Wed, 19 May 2010 10:39:38 +0000 Subject: [Tracker-discuss] [issue338] file.next() break before the end of a file In-Reply-To: <1274265578.66.0.75044001054.issue338@psf.upfronthosting.co.za> Message-ID: <1274265578.66.0.75044001054.issue338@psf.upfronthosting.co.za> New submission from Sebastian Lopez Buritica : I'm trying to read a cvs format file but if i open it using the textpad it showme around 5100 lines but if i open the same file by the .next() command it show me only 4000 lines. i add the csv format file compres by winrar ---------- assignedto: izak files: TotalizadoresPTAP0.rar messages: 1662 nosy: Selobu, izak priority: urgent status: unread superseder: 1.4.8 fixes for other PSF trackers title: file.next() break before the end of a file _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: TotalizadoresPTAP0.rar Type: application/octet-stream Size: 43180 bytes Desc: not available URL: From metatracker at psf.upfronthosting.co.za Wed May 26 14:47:47 2010 From: metatracker at psf.upfronthosting.co.za (Ezio Melotti) Date: Wed, 26 May 2010 12:47:47 +0000 Subject: [Tracker-discuss] [issue338] file.next() break before the end of a file In-Reply-To: <1274265578.66.0.75044001054.issue338@psf.upfronthosting.co.za> Message-ID: <1274878067.11.0.709714197286.issue338@psf.upfronthosting.co.za> Ezio Melotti added the comment: Hi, this bug tracker is not the right place where to ask questions about Python. Try on comp.lang.python (possibly avoiding rar attachments). If the problem turns out to be a bug in Python you can then open a bug on the python bug tracker (bugs.python.org), but this is probably not the case. ---------- nosy: +ezio.melotti priority: urgent -> wish status: unread -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ From metatracker at psf.upfronthosting.co.za Wed May 26 18:46:31 2010 From: metatracker at psf.upfronthosting.co.za (Sebastian Lopez Buritica) Date: Wed, 26 May 2010 16:46:31 +0000 Subject: [Tracker-discuss] [issue338] file.next() break before the end of a file In-Reply-To: <1274878067.11.0.709714197286.issue338@psf.upfronthosting.co.za> Message-ID: Sebastian Lopez Buritica added the comment: thanks for your support best regards 2010/5/26 Ezio Melotti > > Ezio Melotti added the comment: > > Hi, > this bug tracker is not the right place where to ask questions about > Python. Try on comp.lang.python (possibly avoiding rar attachments). > If the problem turns out to be a bug in Python you can then open a bug on > the python bug tracker (bugs.python.org), but this is probably not the > case. > > ---------- > nosy: +ezio.melotti > priority: urgent -> wish > status: unread -> chatting > > _______________________________________________________ > PSF Meta Tracker > > _______________________________________________________ > ---------- status: resolved -> chatting _______________________________________________________ PSF Meta Tracker _______________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: