Task #1526 (new)
Opened 15 years ago
Last modified 14 years ago
processor.py may too aggressively lock causing poll to return after wait
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | Scripting | Version: | 3.0-M1 |
| Keywords: | n.a. | Cc: | dzmacdonald |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.5d |
| Sprint: | n.a. |
Description
Currently the locking on ProcessI is fairly coarse. It may be necessary to move the state into a separate object to make it more fine-grained or introduce read/write semantics.
Change History (6)
comment:1 Changed 15 years ago by jmoore
- Milestone changed from OMERO-Beta4.1 to OMERO-Beta4.2
comment:2 Changed 14 years ago by jmoore
- Component changed from General to Scripting
- Owner changed from jmoore to dzmacdonald
comment:3 Changed 14 years ago by jmoore
- Owner changed from dzmacdonald to jmoore
comment:4 Changed 14 years ago by jmoore
- Type changed from Bug to Task
comment:5 Changed 14 years ago by jmoore
- Remaining Time set to 0.5
comment:6 Changed 14 years ago by jmoore
- Milestone changed from OMERO-Beta4.2 to Unscheduled
Again, shouldn't destabilize now. Moving to unscheduled. Can review for addition to 4.2.1
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
can't destabilize things now. Pushing.