Task #9907 (closed)
Opened 12 years ago
Closed 10 years ago
Bug: Search results - two asterisks
| Reported by: | khgillen | Owned by: | wmoore |
|---|---|---|---|
| Priority: | major | Milestone: | 5.x |
| Component: | Web | Version: | 5.0.5 |
| Keywords: | n.a. | Cc: | ux@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by jmoore)
General Search for or *-* causes stacktrace.
A single asterisk is handled by the error message along the lines of "please enter at least two wildcards".. hence I added another asterisk, causing the stacktrace.
*---* works and produces results, but not or *-*
See also: https://www.openmicroscopy.org/qa2/qa/feedback/4801/ in which the ApiUsageException was thrown for a single asterisks. Such an exception isn't really a remarkable even since it points at a bad argument. Since the argument is coming directly from the client in this case, we have (at least) 3 choices:
- Just provide the AUE to them and say, "try again"
- Do parsing client side to prevent it (there is a pylucene index available for Python)
- Provide for AUE subclasses so that the error is more well-defined.
Attachments (3)
Change History (13)
Changed 12 years ago by khgillen
comment:1 Changed 12 years ago by khgillen
- Cc ux@… added; ux@… removed
comment:2 Changed 12 years ago by wmoore
- Sprint 2012-11-20 (2) deleted
comment:3 Changed 12 years ago by wmoore
- Sprint set to 2012-12-18 (3)
comment:4 Changed 11 years ago by wmoore
- Sprint 2012-12-18 (3) deleted
Going to tackle this alongside other search tickets at some later date. See #9857
comment:5 Changed 11 years ago by jmoore
- Description modified (diff)
comment:6 Changed 11 years ago by jmoore
- Description modified (diff)
- Priority changed from minor to major
comment:7 Changed 11 years ago by wmoore
Also reported https://www.openmicroscopy.org/qa2/qa/feedback/4840/
comment:8 Changed 11 years ago by khgillen
Search term comprising only two asterisks, e.g: causes a crash on 4.4.8 release (demo server at KIT).
comment:9 Changed 10 years ago by khgillen
Still seeing this behaviour with 5.0.2! If we expect people to use the search function, it shouldn't crash when they try.
Changed 10 years ago by jburel
comment:10 Changed 10 years ago by jburel
- Resolution set to fixed
- Status changed from new to closed
- Version set to 5.0.5
Fixed during work on Search in 5.0.x. See screenshot
Stacktrace (taken from Firefox where it displays the stacktraces)