Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#20074 - {bugtracker} search term ending with a space gives a 500 error

Attached to Project: Arch Linux
Opened by solsTiCe (zebul666) - Sunday, 04 July 2010, 13:27 GMT
Last edited by freswa (frederik) - Thursday, 20 February 2020, 21:08 GMT
Task Type Bug Report
Category Web Sites
Status Assigned
Assigned To Lukas Fleischer (lfleischer)
Giancarlo Razzolini (grazzolini)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 3
Private No

Details

Description:
when I search for something and leave a space at the end by mistake, and search for a closed bug, I get a 500 error

for example "test " and click "Advanced" and choose "All closed Tasks"
This task depends upon

Comment by Thomas Dziedzic (tomd123) - Wednesday, 07 July 2010, 18:43 GMT Comment by Thomas Dziedzic (tomd123) - Wednesday, 07 July 2010, 18:44 GMT
also it says to contact the webmaster, did you already do that?
Comment by solsTiCe (zebul666) - Thursday, 08 July 2010, 17:27 GMT
no.
it's a standard message (from apache ?) and I don't think it will help.
I found the bugtracker a better place. It is already assigned to someone and will be taken cared of if needed.
Comment by Allan McRae (Allan) - Saturday, 16 June 2012, 07:50 GMT
Well... it no longer appears to give that error, but the search just returns everything.
Comment by Ashley Whetter (AWhetter) - Thursday, 11 July 2013, 21:21 GMT
Weirdly Chrome gives me a 200 but a blank page (blank on "View Source" as well). Looking at the url it's putting a + at the end of the string because of the space, but of course there isn't anything after the space. Not sure if that's the issue? For me, removing the + gives me a 500.
I don't think this is a FlySpray issue (unless it's an old one). Their bugtracker behaves normally (even with the + in the string), plus there are no flyspray bugs reported about this issue.
Comment by mattia (nTia89) - Saturday, 15 November 2014, 12:30 GMT
on my own I get a blank page
Comment by Peter Liscovius (peterdd) - Friday, 11 January 2019, 07:43 GMT
I found this conversation today. It shows also too many results in Flyspray 1.0-rc7 and I made a fix. :-)

https://github.com/Flyspray/flyspray/commit/b43cf63cc3acc6bfc0081cca8d3181cf4ee74f5e

Related task on bugs.flyspray.org: https://bugs.flyspray.org/2532



Comment by solsTiCe (zebul666) - Wednesday, 12 February 2020, 14:08 GMT
so I posted this on the wrong flyspray ? how ironic
Comment by Giancarlo Razzolini (grazzolini) - Wednesday, 12 February 2020, 14:48 GMT
Wow, this bug is ancient. And it seems it was only fixed last year. Anyway, I can try bringing our version of flyspray to 1.0-rc9 and updating it. The bug is still present on our version of flyspray.
Comment by Peter Liscovius (peterdd) - Tuesday, 18 February 2020, 09:26 GMT
Related FS#38506

Loading...