I've tried it again. It looks really good now. The SQL error is gone, and "Additional constraint" as well as "Modified Since" date is stored correctly.
Thank you very much for your help!!
|
This was a newer bug, I think now I've fixed it.
|
Hmmm, something went wrong.
The SQL error has disappeared.
But it seems that the "modified since" field is not retained. If I click on "Bugs" or "Bugs->Brows", the current date will be written into the date field. All 1300+ active errors will be shown.
|
All cited SQL queries are for the case when the additional constraint is activated and it selects items that are not modified; I've just pushed and installed a fix.
Thank you!
|
To narrow down the problem:
- I'm using the tracker under four different systems.
- Different browsers (IE, Firefox, SeaMonkey, Safari)
- Different OS (Windows XP, 7, 10, iOS 11)
- Different internet providers
- If I screwed up my user profile on the iOS system, it will be also wrong on the Windows system. The error is traveling with the user profile.
So, obviously it has nothing to do with
- OS
- Browser
- Cookies
- Windows / Linux / MacOS
It has to do, however, with
- The ticket system on savannah.gnu.org
- The user profile on savannah.gnu.org
- The options "Additional constraint" = "activated" and "Any modified since" = "[any date]"
- Maybe the customization that has been done for the project "GNU Octave"
|
Same problem here on another project (quilt):
db_query: SQL query error Unknown column 'bugs.bug_id' in 'on clause' in [SELECT count(DISTINCT bugs.bug_id) AS count FROM bugs ,user user_assigned_to LEFT JOIN bugs_history ON ((bugs_history.bug_id = bugs.bug_id ) AND (bugs_history.date >= 0) AND (bugs_history.field_name = NULL)) WHERE bugs.group_id='3520' AND (bugs.spamscore < '5' OR submitted_by='12366') AND user_assigned_to.user_id=bugs.assigned_to AND bugs_history.bug_id IS NULL]
I think it is caused by previous search criteria which are remembered but no longer valid. Using "Bugs > Reset to open" as advised by Armin works around the problem (thanks Armin!) However it is not exactly user-friendly.
Ideally, the old query should be transparently converted to the equivalent query for the new model. If that is not possible or is considered too much work for a transitory issue, then invalid queries should be automatically forgotten. In other words, when a query fails, instead of spitting the database error in the browser, you should redirect to the same page as "Bugs > Reset to open".
|
Still doesn't reproduce for me, with URL
|
When I read the other two cases, it seems that the settings are important:
Default for Octave:
Open/Closed = "Open"
Additional constraint = "deactivated"
Failure Case for Octave:
Open/Closed = "Any"
Additional constraint = "activated" <= this one is relevant
Any modified since = "[any date]"
The setting "Additional constraint = activated" will lead to the bug.
|
...and to sr #109187.
|
Looks similar to sr #107979.
|
I just tried to clear all cookies in connection with "gnu" and "savannah". However, the effect still does happen.
|
I did encounter such errors, but I can't reproduce this one. Does it still happen after you clear your Savannah cookies?
|
For some reason, and for some weeks now, the bug tracker in Octave is broken when I'm using it. An SQL error is appearing when browsing the bug list.
https://savannah.gnu.org/bugs/?group=octave
Example:
"Bugs => Browse" gives
db_query: SQL query error Unknown column 'bugs.bug_id' in 'on clause' in [SELECT count(DISTINCT bugs.bug_id) AS count FROM bugs ,user user_assigned_to LEFT JOIN bugs_history ON ((bugs_history.bug_id = bugs.bug_id ) AND (bugs_history.date >= 0) AND (bugs_history.field_name = NULL)) WHERE bugs.group_id='1925' AND (bugs.spamscore < '5' OR submitted_by='94238') AND user_assigned_to.user_id=bugs.assigned_to AND bugs_history.bug_id IS NULL]
"Bugs => Reset to open"
... then gives results as expected, again. I have to restore my settings manually, however.
Posted before as Octave bug #54355
|