Bug #7625
closed
FilterForms throw error when 'no preference' is chosen
Added by Jakub Judiny almost 2 years ago.
Updated over 1 year ago.
Category:
Development - GUI
Description
In basic type of FilterForms, when <<no preference>> is chosen in detectors/categories field, the whole form throws:
pynspect.gparser.PynspectGrammarSyntaxError: Syntax error at 'LexToken(RBRACK,']',1,15)
because the parser wants to interpret the "" string as a detector/category.
- Status changed from In Progress to Resolved
- Category set to Development - GUI
- Status changed from Resolved to In Review
- Target version changed from Backlog to 2.11
- To be discussed deleted (
Yes)
Merged into devel and deployed on mentat-alt.
- Status changed from In Review to In Progress
Based on what Pavel Kácha said on today's meeting, I tried sending the POST request by myself. If 'detectors' is specified in the parameters, the filter is created and when I try to edit the filter, I get Internal Server Error. I believe it will be the same for 'categories'. So the issue is only solved in the GUI.
...group=5&name=TEST+FILTER+%28TO+BE+DELETED%29&description=test+filter&type=basic&filter=&detectors=&sources=&enabled=False&valid_from=&valid_to=&...
- Status changed from In Progress to Resolved
- Status changed from Resolved to In Review
- Status changed from In Review to Closed
Also available in: Atom
PDF