Is there a trick for making the bugzilla bug entry form come up faster? E.g., is there a way to specify the fields that have huge drop-down lists as parameters in the URL and prevent the drop-down lists from being loaded? I discovered that I could specify the initial value of the component list by adding "component=/whatever/" to the URL, but it still loads the whole list.
It's rather annoying that I have to sit around twiddling my thumbs for 40 seconds (yes, it's really that long; I just timed it) waiting for the page to load every time I want to report a bug.
jik
On 08/26/2009 12:02 PM, Jonathan Kamens wrote:
Is there a trick for making the bugzilla bug entry form come up faster? E.g., is there a way to specify the fields that have huge drop-down lists as parameters in the URL and prevent the drop-down lists from being loaded? I discovered that I could specify the initial value of the component list by adding "component=/whatever/" to the URL, but it still loads the whole list.
It's rather annoying that I have to sit around twiddling my thumbs for 40 seconds (yes, it's really that long; I just timed it) waiting for the page to load every time I want to report a bug.
http://bugz.fedoraproject.org/<source rpm name>
Will save you tons of time and pain.
Rahul
On 08/26/2009 05:00 AM, Rahul Sundaram wrote:
On 08/26/2009 12:02 PM, Jonathan Kamens wrote:
It's rather annoying that I have to sit around twiddling my thumbs for 40 seconds (yes, it's really that long; I just timed it) waiting for the page to load every time I want to report a bug.
http://bugz.fedoraproject.org/<source rpm name>
Will save you tons of time and pain.
Thta's neat, but it doesn't solve the problem I wrote about. It still takes 38 seconds to load the bug report form when you click on the "Report a new bug" link from the bugz.fedoraproject.org page for a particular RPM.
jik
On Wed, Aug 26, 2009 at 08:12:10AM -0400, Jonathan Kamens wrote:
On 08/26/2009 05:00 AM, Rahul Sundaram wrote:
On 08/26/2009 12:02 PM, Jonathan Kamens wrote:
It's rather annoying that I have to sit around twiddling my thumbs for 40 seconds (yes, it's really that long; I just timed it) waiting for the page to load every time I want to report a bug.
http://bugz.fedoraproject.org/<source rpm name>
Will save you tons of time and pain.
Thta's neat, but it doesn't solve the problem I wrote about. It still takes 38 seconds to load the bug report form when you click on the "Report a new bug" link from the bugz.fedoraproject.org page for a particular RPM.
I don't have a fix per se for this problem, but I've started working around it by using the command-line 'bugzilla' client:
$ bugzilla login $ bugzilla new -p Fedora -v rawhide -c <component_name> -s 'short summary' -l "component-0.0.1-1.fc11.x86_64 \nBlah blah blah this doesn't work and here's what I've already done to try fixing it"
Maybe Will is listening -- one RFE I was thinking about, but not sure if it's worthwhile, would be allowing people to use $EDITOR to fill in the comment (-l) field.
On 08/26/2009 08:00 PM, Paul W. Frields wrote:
Maybe Will is listening -- one RFE I was thinking about, but not sure if it's worthwhile, would be allowing people to use $EDITOR to fill in the comment (-l) field.
Kushal has a bug reporting client with a text UI (that uses newt) that is currently being used to build the underlying functionality for
https://fedoraproject.org/wiki/Bugzilla_Desktop_Client
I am working with him on this. We would release this soon as soon as we get Red Hat Legal to sign off on the name.
Rahul
On Wed, 2009-08-26 at 22:38 +0530, Rahul Sundaram wrote:
On 08/26/2009 08:00 PM, Paul W. Frields wrote:
Maybe Will is listening -- one RFE I was thinking about, but not sure if it's worthwhile, would be allowing people to use $EDITOR to fill in the comment (-l) field.
Kushal has a bug reporting client with a text UI (that uses newt) that is currently being used to build the underlying functionality for
https://fedoraproject.org/wiki/Bugzilla_Desktop_Client
I am working with him on this. We would release this soon as soon as we get Red Hat Legal to sign off on the name.
You can also use python-bugzilla, which can do querying and reporting with a command-line interface. works very nicely.
On Wed, Aug 26, 2009 at 11:06:07AM -0700, Adam Williamson wrote:
On Wed, 2009-08-26 at 22:38 +0530, Rahul Sundaram wrote:
On 08/26/2009 08:00 PM, Paul W. Frields wrote:
Maybe Will is listening -- one RFE I was thinking about, but not sure if it's worthwhile, would be allowing people to use $EDITOR to fill in the comment (-l) field.
Kushal has a bug reporting client with a text UI (that uses newt) that is currently being used to build the underlying functionality for
https://fedoraproject.org/wiki/Bugzilla_Desktop_Client
I am working with him on this. We would release this soon as soon as we get Red Hat Legal to sign off on the name.
You can also use python-bugzilla, which can do querying and reporting with a command-line interface. works very nicely.
Right, that's what provides the /usr/bin/bugzilla I mentioned. Keen!
On Wed, 2009-08-26 at 14:13 -0400, Paul W. Frields wrote:
On Wed, Aug 26, 2009 at 11:06:07AM -0700, Adam Williamson wrote:
On Wed, 2009-08-26 at 22:38 +0530, Rahul Sundaram wrote:
On 08/26/2009 08:00 PM, Paul W. Frields wrote:
Maybe Will is listening -- one RFE I was thinking about, but not sure if it's worthwhile, would be allowing people to use $EDITOR to fill in the comment (-l) field.
Kushal has a bug reporting client with a text UI (that uses newt) that is currently being used to build the underlying functionality for
https://fedoraproject.org/wiki/Bugzilla_Desktop_Client
I am working with him on this. We would release this soon as soon as we get Red Hat Legal to sign off on the name.
You can also use python-bugzilla, which can do querying and reporting with a command-line interface. works very nicely.
Right, that's what provides the /usr/bin/bugzilla I mentioned. Keen!
Oh yes, now I see your mail :) sorry to duplicate!
rahulsundaram wrote:
http://bugz.fedoraproject.org/<source rpm name>
Will save you tons of time and pain.
I just tried this for http://bugz.fedoraproject.org/xorg-x11-server
Firstly it failed to list https://bugzilla.redhat.com/show_bug.cgi?id=512111 which should be included for this component, and secondly there seems no way to list the bugs by bug number i.e. a numerically monotonic increasing set....
On Wed, 26 Aug 2009, Mike Cloaked wrote:
rahulsundaram wrote:
http://bugz.fedoraproject.org/<source rpm name>
Will save you tons of time and pain.
I just tried this for http://bugz.fedoraproject.org/xorg-x11-server
Firstly it failed to list https://bugzilla.redhat.com/show_bug.cgi?id=512111
1. bugz.fp.o doesn't list closed bugs.
and secondly there seems no way to list the bugs by bug number i.e. a numerically monotonic increasing set....
2. Taking patches.
-sv
On 08/26/2009 10:34 PM, Mike Cloaked wrote:
I just tried this for http://bugz.fedoraproject.org/xorg-x11-server
Firstly it failed to list https://bugzilla.redhat.com/show_bug.cgi?id=512111
It won't list closed bugs. That's the same as bugzilla itself by default.
which should be included for this component, and secondly there seems no way to list the bugs by bug number i.e. a numerically monotonic increasing set....
If you know the bug number, you just go to bugzilla.redhat.com/number
Rahul
On Wed, Aug 26, 2009 at 10:41:57PM +0530, Rahul Sundaram wrote:
On 08/26/2009 10:34 PM, Mike Cloaked wrote:
I just tried this for http://bugz.fedoraproject.org/xorg-x11-server
Firstly it failed to list https://bugzilla.redhat.com/show_bug.cgi?id=512111
It won't list closed bugs. That's the same as bugzilla itself by default.
which should be included for this component, and secondly there seems no way to list the bugs by bug number i.e. a numerically monotonic increasing set....
If you know the bug number, you just go to bugzilla.redhat.com/number
I think what he was looking for was a way to have the output sorted purely by bug number, rather than sorted on status first and some unseen keys following that. Anyway, the project code is at:
https://fedorahosted.org/packagedb/
Thankfully Python based, so not hard to hack if someone's interested.
Paul W. Frields <stickster <at> gmail.com> writes:
I think what he was looking for was a way to have the output sorted purely by bug number, rather than sorted on status first and some unseen keys following that. Anyway, the project code is at:
https://fedorahosted.org/packagedb/
Thankfully Python based, so not hard to hack if someone's interested.
Yes indeed that would be useful - you can do this in bugzilla.redhat.com once you have a list in the browser...
Jonathan Kamens wrote:
Is there a trick for making the bugzilla bug entry form come up faster? E.g., is there a way to specify the fields that have huge drop-down lists as parameters in the URL and prevent the drop-down lists from being loaded? I discovered that I could specify the initial value of the component list by adding "component=/whatever/" to the URL, but it still loads the whole list.
It's rather annoying that I have to sit around twiddling my thumbs for 40 seconds (yes, it's really that long; I just timed it) waiting for the page to load every time I want to report a bug.
Smells like an Apache config issue. We serve tons of stuff ourselves and have fallen back to Apache using mpm workers and a mod_fastcgi interface to external PHP processes (managed by php-fpm). Works a treat and is much less load on the server. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - "I'd explain it to you, but your brain might explode." - ----------------------------------------------------------------------
-
Adam Williamson -
Jonathan Kamens -
mike cloaked -
Paul W. Frields -
Rahul Sundaram -
Rick Stevens -
Seth Vidal