| Summary: | Allow to cancel tasks when leaving a page | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Tomasz Zarna <tomasz.zarna> |
| Component: | Server | Assignee: | Anthony Hunter <ahunter.eclipse> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P4 | CC: | ahunter.eclipse |
| Version: | 0.4 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Tomasz Zarna
I think it depends on what the task is. If it is just the one that populates the page, we should probably dismiss it. If it is Git clone started on the page, leave it. I don't think this is an enhancement request, having a bunch of these tasks running, could be a performance issue. (In reply to comment #2) > I don't think this is an enhancement request, having a bunch of these tasks > running, could be a performance issue. OK, but this is for sure not for 0.4. How do you see it? It's user that cancels the tasks, or are they cancelled by default on leaving the page? (In reply to comment #1) > I think it depends on what the task is. If it is just the one that populates > the page, we should probably dismiss it. If it is Git clone started on the > page, leave it. We have some tasks marked as idempotent that are removed from the task list when data is loaded. I think we could use this information to cancel and remove them. (In reply to comment #3) > How do you see it? It's user that cancels the tasks, or are they cancelled by > default on leaving the page? A task should be marked for cancel when there is no open page waiting for its result. On the other hand, once ETags[1] are implemented we could let the task finish, save the result and use it in the future. [1] bug 339846, bug 338121, bug 338122 (In reply to comment #4) > A task should be marked for cancel when there is no open page waiting for its > result. I can agree on that for git log, bug what about Git Clone, Git Fetch? User may schedule operation that is long running (I believe clone operation can take and hour or more for very large repositories and bad connection), close the page and then return the next day to check the operation status. Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg04002.html |