Task #2753 (closed)
Opened 9 years ago
Closed 4 years ago
RenderingSettings Service, Channel w/o stats info
| Reported by: | jburel | Owned by: | jburel |
|---|---|---|---|
| Priority: | minor | Milestone: | 5.1.0 |
| Component: | General | Version: | 5.0.8 |
| Keywords: | n.a. | Cc: | jamoore, cxallan |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Add control to the methods so that channels w/o stats info do not return exception. Just ignore them
Stats info is not required in db so we cannot rely on it
Change History (9)
comment:1 Changed 9 years ago by jburel
- Owner set to jburel
- Status changed from new to assigned
comment:2 Changed 9 years ago by jburel
- Owner jburel deleted
- Status changed from assigned to new
comment:3 Changed 9 years ago by jburel
- Sprint 2010-08-26 (15) deleted
comment:4 Changed 9 years ago by jburel
- Milestone changed from OMERO-Beta4.2.1 to Unscheduled
comment:5 Changed 9 years ago by cxallan
comment:6 Changed 4 years ago by jburel
- Cc jamoore cxallan added
- Milestone changed from Unscheduled to 5.1.0
- Version set to 5.0.8
Found this old ticket. Moving to 5.1.0 cf. Friday's discussion.
comment:7 Changed 4 years ago by jburel
comment:9 Changed 4 years ago by jburel
- Milestone changed from 5.1.2 to 5.1.0
- Resolution set to fixed
- Status changed from new to closed
All good now.
Closing
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
(In [8288]) Reverting r7441 and adding some more sanity checks to the Renderer. With r7441 it's possible that Images without channel statistics will get to the Renderer via the ThumbnailBean? and/or RenderingBean?. This can cause problems and the previous strategy of assigning min/max PixelType? range also causes the user to have to trigger a "resetDefaults()" if he/she attempted to view the Image while it was importing. We're sure that Jean-Marie made the changes for a good reason and we may need to review this again if there are further bugs that expose the issue outlined in #2545. (See #2545 and #2753; Fixes #3011)