Bug#549439: pkgreport.cgi - internal server errors when using include= parameter
clone 549439 -1 retitle -1 propogate users= cgi option to further queries in pkgreport.cgi clone 549439 -2 retitle -2 some include options screw up the summary counts in pkgreport.cgi thanks On Mon, 05 Oct 2009, vincent.mcint...@csiro.au wrote: sure, I realised I could use that method. However I was interested to check whether for example this URL (taken from [1]) would/could ever work: http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=debian-b...@lists.debian.org;include=alpha which amounts to wondering what the include= keyword does for you. I don't know who wrote that url, but presumably what they were actually looking for was http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=debian-b...@lists.debian.org;include=tags:alpha What form would be most useful? A distinct file or a patch to e.g. [2]? It actually will have to be entirely new html documentation, ideally written in wml against the web pages, which you can see in the webwml CVS repository for the Debian website. The documentation in 2 is really outdated, and I haven't been keeping it up to date. I tried the obvious http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214790;users=debian-b...@lists.debian.org and got a 500 error. This is the right query; there was a bug which I've fixed in my source copy, which will be fixed when I next merge my changes. It actually already does that at the top of the display: Ah. I am pretty sure it wasn't doing that for me before, when I started asking all these dumb questions. I tried again just now, and got the list of tags. Yay. Have you updated the running code in between? Nope. So now I think I am starting to get this. Then I tried: lynx -mime_header -source http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=alpha;users=debian-b...@lists.debian.org and got the attached file (pkgreport.cgi.usertag.test1.txt). I see the Summary and the Options sections but no, er, bug numbers listed. Yet the Summary says there are bugs to display. I'm not sure what the deal is with this; I'd have to look more carefully. If I do the obvious thing and hit the 'submit' button on the displayed page, the URL changes to http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=alpha and I get No reports found!. That's because the alpha tag is a user tag, and the url doesn't include the users= option any more. I need to fix this, but I haven't had a chance yet; cloned out as a sepearate bug. Don Armstrong -- We were at a chinese resturant. He was yelling at the waitress because there was a typo in his fortune cookie. -- hugh http://www.gapingvoid.com/Moveable_Type/archives/000321.html http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549439: pkgreport.cgi - internal server errors when using include= parameter
you're more patient than I realised. One thing I have been trying to figure out is how to get the usertags defined for a given bug report to be displayed in the browser. If you give the user in the users field, they're displayed as if they were actual tags. Really? I mean here when I am looking at one particular bug, eg the url http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214790 This is the first hit in the general search for usertags http://bugs.debian.org/cgi-bin/bugreport.cgi?users=debian-b...@lists.debian.org so it would seem there should be usertags to show. Yet I can't see any usertags in the display of the individual bug. I looked carefully again at the output of the general search http://bugs.debian.org/cgi-bin/bugreport.cgi?users=debian-b...@lists.debian.org and *finally* saw where the tags are displayed; appended to the 'table of contents' links, and at the top of each sublist. It's, erm, subtle. Which is fine. I do think it would help to use some slightly different formatting of the usertags' text, but looking at common.pl:htmlizebugs() I can see that this might be difficult to arrange; it's not obvious by that stage of execution which part of header string is tag text. So from this display I can conclude that bug #214790 has at least one usertag, 'not-di'. Correct? It still would be useful to have the usertags shown in the display of the individual bug. For one thing, I guess that if there are multiple usertags on a bug (eg i386,serial) only one of them is used to determine which subgroup the bug is shown in (the first one that was added?). I think it would be helpful to show all of them in the display of the individual bug. Kind Regards Vince -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549439: pkgreport.cgi - internal server errors when using include= parameter
They're actually in the information for each bug, too. If you click on the [i|N|ÿÿ] bits, you'll see them. Ah. Lovely! Well hidden, but then all the more rewarding when found. I do still think it would be useful to show them in the bug when it is fully displayed. Cheers Vince
Bug#549439: pkgreport.cgi - internal server errors when using include= parameter
On Mon, 05 Oct 2009, vincent.mcint...@csiro.au wrote: It's, erm, subtle. Which is fine. I do think it would help to use some slightly different formatting of the usertags' text, but looking at common.pl:htmlizebugs() I can see that this might be difficult to arrange; it's not obvious by that stage of execution which part of header string is tag text. They're actually in the information for each bug, too. If you click on the [i|N|☺] bits, you'll see them. [It's a bug that the bugreport.cgi script errors out, which, as I mentioned previously, has been fixed in my branch and will be deployed shortly.] Don Armstrong -- We must realize that today's Establishment is the New George III. Whether it will continue to adhere to his tactics, we do not know. If it does, the redress, honored in tradition, is also revolution. -- William O. Douglas _Points of Rebellion_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549439: pkgreport.cgi - internal server errors when using include= parameter
On Tue, 06 Oct 2009, vincent.mcint...@csiro.au wrote: They're actually in the information for each bug, too. If you click on the [i|N|ÿÿ] bits, you'll see them. Ah. Lovely! Well hidden, but then all the more rewarding when found. I do still think it would be useful to show them in the bug when it is fully displayed. They are supposed to be; it's just a small bug that caused them not to be, which (as I've said), I'll be fixing sometime later. Don Armstrong -- If it jams, force it. If it breaks, it needed replacing anyway. -- Lowery's Law http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549439: pkgreport.cgi - internal server errors when using include= parameter
On Tue, 6 Oct 2009, Don Armstrong wrote: Ah. Lovely! Well hidden, but then all the more rewarding when found. I do still think it would be useful to show them in the bug when it is fully displayed. They are supposed to be; it's just a small bug that caused them not to be, which (as I've said), I'll be fixing sometime later. oh, sorry. I misparsed your previous reply. It's too late here... Vince -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549439: pkgreport.cgi - internal server errors when using include= parameter
Thanks for your prompt reply. Neither of those are valid selection requests, unfortunatly. What exactly are you trying to do? I am experimenting with pulling out groups of bugs using usertags. Specifically I was attempting to make some of the urls in [2], that claim to pull out arch-specific bugs, actually work. I can't find any documentation for how to construct such URLs more advanced than setting users= and tag= in the URL. Reading the source of pkgreport.cgi[3] suggests not much of the vision actually ended up getting implemented, but I am having trouble following the code. I'm happy to help write something that documents the current functionality. One thing I have been trying to figure out is how to get the usertags defined for a given bug report to be displayed in the browser. Ubuntu have this feature in b.u.o and I think it's useful. I can't see any knob in the browser interface that lets me turn this on. Is there a reason they are not being displayed? I would also like to be able to display all the usertags set by a given user. If I just set users= in the URL, but omit tag=, I'd get all bugs tagged by that user but would then have to compile the usertags. It seems it would be easy for pkgreport.cgi to do that for me and show it as a line at the top of the summary display. Cheers Vince [2] http://wiki.debian.org/DebianInstaller/Bugs [3] http://bugs.debian.org/debbugs-source/mainline/cgi/pgkreport.cgi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549439: pkgreport.cgi - internal server errors when using include= parameter
On Sun, 04 Oct 2009, vincent.mcint...@csiro.au wrote: I am experimenting with pulling out groups of bugs using usertags. Specifically I was attempting to make some of the urls in [2], that claim to pull out arch-specific bugs, actually work. Assuming the architecture specific bits are done by usertags that are against the debian-b...@lists.debian.org user, you can just do the following: http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=debian-b...@lists.debian.org;tag=amd64;users=debian-b...@lists.debian.org I can't find any documentation for how to construct such URLs more advanced than setting users= and tag= in the URL. Reading the source of pkgreport.cgi[3] suggests not much of the vision actually ended up getting implemented, but I am having trouble following the code. The only bit that isn't implemented is the ability to enter users= and other bits in the url selection at the bottom. I'm happy to help write something that documents the current functionality. That'd be great. One thing I have been trying to figure out is how to get the usertags defined for a given bug report to be displayed in the browser. If you give the user in the users field, they're displayed as if they were actual tags. I would also like to be able to display all the usertags set by a given user. If I just set users= in the URL, but omit tag=, I'd get all bugs tagged by that user but would then have to compile the usertags. It seems it would be easy for pkgreport.cgi to do that for me and show it as a line at the top of the summary display. It actually already does that at the top of the display: Debian Bug report logs: Bugs (tagged netcfg or debootstrap or accessibility or network or floppy or sarge-ext or etch-beta1 or partman or daily or etch-beta3 or etch or mipsel or hw-sata or l10n or arm or hw-cdrom or serial or old-report or netinst or sarge-rc2 or full or boot or none or hw or netboot or tasksel or usability or sarge-r1 or alpha or ia64 or kfreebsd or sparc or bc or not-d-i or debian-edu or cd or reboot or mips or m68k or lenny-beta2 or hd-media or s390 or sarge-r0 or etch-rc1 or hppa or powerpc or amd64 or i386) See http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-b...@lists.debian.org Don Armstrong -- For those who understand, no explanation is necessary. For those who do not, none is possible. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549439: pkgreport.cgi - internal server errors when using include= parameter
Thanks for your patient answers. I am experimenting with pulling out groups of bugs using usertags. Specifically I was attempting to make some of the urls in [2], that claim to pull out arch-specific bugs, actually work. Assuming the architecture specific bits are done by usertags that are against the debian-b...@lists.debian.org user, you can just do the following: http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=debian-b...@lists.debian.org;tag=amd64;users=debian-b...@lists.debian.org sure, I realised I could use that method. However I was interested to check whether for example this URL (taken from [1]) would/could ever work: http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=debian-b...@lists.debian.org;include=alpha which amounts to wondering what the include= keyword does for you. I can't find any documentation for how to construct such URLs more advanced than setting users= and tag= in the URL. Reading the source of pkgreport.cgi[3] suggests not much of the vision actually ended up getting implemented, but I am having trouble following the code. The only bit that isn't implemented is the ability to enter users= and other bits in the url selection at the bottom. ok, that helps quite a bit. I'm happy to help write something that documents the current functionality. That'd be great. What form would be most useful? A distinct file or a patch to e.g. [2]? One thing I have been trying to figure out is how to get the usertags defined for a given bug report to be displayed in the browser. If you give the user in the users field, they're displayed as if they were actual tags. Really? I mean here when I am looking at one particular bug, eg the url http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214790 This is the first hit in the general search for usertags http://bugs.debian.org/cgi-bin/bugreport.cgi?users=debian-b...@lists.debian.org so it would seem there should be usertags to show. Yet I can't see any usertags in the display of the individual bug. I tried the obvious http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214790;users=debian-b...@lists.debian.org and got a 500 error. I tried a newer bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=326109;users=debian-b...@lists.debian.org; and I aslo get a 500 error. I would also like to be able to display all the usertags set by a given user. If I just set users= in the URL, but omit tag=, I'd get all bugs tagged by that user but would then have to compile the usertags. It seems it would be easy for pkgreport.cgi to do that for me and show it as a line at the top of the summary display. It actually already does that at the top of the display: Ah. I am pretty sure it wasn't doing that for me before, when I started asking all these dumb questions. I tried again just now, and got the list of tags. Yay. Have you updated the running code in between? I found also that this: http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-b...@lists.debian.org;include=alpha works, where it did not before. By works I mean that the Options section shows a whole stack of 'tagged' selectors, that I did not see before. So now I think I am starting to get this. Then I tried: lynx -mime_header -source http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=alpha;users=debian-b...@lists.debian.org and got the attached file (pkgreport.cgi.usertag.test1.txt). I see the Summary and the Options sections but no, er, bug numbers listed. Yet the Summary says there are bugs to display. If I do the obvious thing and hit the 'submit' button on the displayed page, the URL changes to http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=alpha and I get No reports found!. If I select unarchived archived in the Misc options - the URL changes to http://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;tag=alpha and I get No reports found!. If I do the same thing for the i386 architecture, I do get some bug numbers displayed, but far fewer than what the summary states. (pkgreport.cgi.usertag.test2.txt) The URLs http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-b...@lists.debian.org;tag=i386 http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-b...@lists.debian.org;tag=i386;archive=both; both yield the same result. Assuming there's not some reason for this behaviour, this should probably be broken out into a separate bug. Kind regards, Vince [1] http://wiki.debian.org/DebianInstaller/Bugs [2] http://bugs.debian.org/debbugs-source/mainline/html/Access.html.inHTTP/1.1 200 OK Date: Mon, 05 Oct 2009 05:07:30 GMT Server: Apache Connection: close Content-Type: text/html; charset=utf-8 !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN HTMLHEAD TITLEBugs tagged alpha -- Debian Bug report logs/TITLE link rel=stylesheet href=/css/bugs.css type=text/css/HEAD BODY onload=pagemain(); DIV id=status_mask/DIV H1Debian Bug report logs: Bugs tagged alpha/H1 HRH2No reports found!/H2/HR script
Bug#549439: pkgreport.cgi - internal server errors when using include= parameter
Package: bugs.debian.org
Severity: normal
I was reviewing what passes for documentation on the use of usertags [1]
to query the bts, via bugs.debian.org/pkgreport.cgi, and started
experimenting in order to find what does does not actually work,
inspired by the material in [2].
I put in this request:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-b...@lists.debian.org;include=i386;
and got a 500 error.
I then put almost the same thing (removed the trailing ';')
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-b...@lists.debian.org;include=i386
and again got a 500 error.
The time stamps are
Sat 03 Oct 2009 11:06:01 GMT and
Sat 03 Oct 2009 11:06:04 GMT
So the first issue to report is the 500 errors, as the error message asks.
I may well be abusing the 'include' parameter but surely this could be
handled more gracefully.
I doubt my map{}-fu is up to writing a patch.
Then I noticed something a little odd which I should report too.
Perhaps it is just collateral damage from content negotiations.
In the first case, the output was formatted as plain text,
(ie the HTTP Content-Type: header was text/plain)
while in the second it was normal HTML (text/html).
This behaviour doesn't seem to be entirely repeatable, but it
happened a few times at least. I expect one needs to clear browser
caches, etc first.
I tried the same urls with 'lynx -mime_header -source' and got the
same output (text/plain) in both cases, apart from the HTTP Date: header
of course.
A related issue which I should perhaps file separately.
I also submitted this URL,
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-b...@lists.debian.org;include=alpha
at Sat 03 Oct 2009 11:28:18 GMT
and got _no output_ at all sent to the browser (iceweasel from
'etch'/i386).
I tried the same url with lynx and got the expected internal server error
message, with Content-Type: text/plain.
Cheers
Vince
[1] http://wiki.debian.org/bugs.debian.org/usertags
[2] http://wiki.debian.org/DebianInstaller/Bugs
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549439: pkgreport.cgi - internal server errors when using include= parameter
retitle 549439 more informative error messages for invalid urls reassign 549439 debbugs thanks On Sat, 03 Oct 2009, Vincent McIntyre wrote: I was reviewing what passes for documentation on the use of usertags [1] to query the bts, via bugs.debian.org/pkgreport.cgi, and started experimenting in order to find what does does not actually work, inspired by the material in [2]. I put in this request: http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-b...@lists.debian.org;include=i386; and got a 500 error. I then put almost the same thing (removed the trailing ';') http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-b...@lists.debian.org;include=i386 and again got a 500 error. Neither of those are valid selection requests, unfortunatly. What exactly are you trying to do? So the first issue to report is the 500 errors, as the error message asks. I may well be abusing the 'include' parameter but surely this could be handled more gracefully. Right, it should probably produce a slightly more informative error message. Don Armstrong -- You could say to the Universe this is not /fair/. And the Universe would say: Oh it isn't? Sorry. -- Terry Pratchett _Soul Music_ p357 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
