Task #12449 (closed)
Opened 5 years ago
Closed 3 years ago
BUG: No error message in Insight
| Reported by: | pwalczysko | Owned by: | jburel |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | Insight | Version: | 5.0.2 |
| Keywords: | n.a. | Cc: | ux@…, rleigh, mlinkert |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
During testing of Mark's PR https://github.com/openmicroscopy/openmicroscopy/pull/2701#issuecomment-48031250 found out that in case of duplicate fs path, and a consequently failed import, Insight gives no clues as to what is happening.
See details in the comment on the PR. https://github.com/openmicroscopy/openmicroscopy/pull/2701#issuecomment-48030851
I think this is valid for a range of situations, not only for this one.
See Mark's comment
here are a few things where something bad happens on the server due to a client action and the client doesn't know how to recognize the exception well and reports something unfriendly instead -- in talking to pwalczysko just now, I wonder if perhaps there should be a general approach of, say, the ServerError? always trying to have a nice message and the clients trying to display that message semi-friendlily ... or something of the sort, anyway. So that for every new server error condition we don't have to do special coding in the clients for a not-horrifying result.
Change History (6)
comment:1 Changed 5 years ago by jburel
- Milestone changed from 5.1.0-m1 to 5.1.0-m2
comment:2 Changed 4 years ago by jburel
- Cc changed from ux@openmicroscopy.org.uk, rleigh, mlinkert, to ux@openmicroscopy.org.uk, rleigh, mlinkert
comment:3 Changed 4 years ago by jburel
- Milestone changed from 5.1.2 to 5.1.4
comment:4 Changed 4 years ago by jamoore
- Milestone changed from 5.1.4 to OMERO-5.1.4
Splitting 5.1.4 due to milestone decoupling
comment:5 Changed 3 years ago by jamoore
- Milestone changed from 5.x to Unscheduled
comment:6 Changed 3 years ago by jburel
- Resolution set to wontfix
- Status changed from new to closed
Reading the thread again. The fact that the "View exception" does nothing seems to indicate that nothing meaningful was actually returned.