Bug 291814 - [Progress] Blocked Job should have a link to the blocking job
Summary: [Progress] Blocked Job should have a link to the blocking job
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-08 14:25 EDT by Markus Keller CLA
Modified: 2019-09-06 16:07 EDT (History)
2 users (show)

See Also:

Attachments
Restore interrupts if interrupted during acquire() (1.02 KB, patch)
2009-10-26 09:46 EDT, Min Idzelis CLA 		no flags Details | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2009-10-08 14:25:27 EDT 
Blocked jobs are currently rendered with a suffix ' (Blocked: The user operation is waiting for "<jobname>" to complete.)', see e.g. attachment 80760 [details].

When I now want to cancel the blocking job, I have to manually search for it by name. Could the embedded job name be turned into a link so that I don't have to do the mapping by hand?

The blocking job should be available from IJobStatus.getJob() and could be read out and rendered in JobInfo.getDisplayStringWithStatus(boolean).
Comment 1 Min Idzelis CLA 2009-10-26 09:46:12 EDT 
Created attachment 150509 [details]
Restore interrupts if interrupted during acquire()

This patch is ready to be committed whenever it is reviewed/approved.
Comment 2 Min Idzelis CLA 2009-10-26 09:48:48 EDT 
Oops. This patch is for a different bug. (bug 293308) I can't figure out how to delete this patch. Please ignore it.
Comment 3 Paul Webster CLA 2009-10-26 10:14:38 EDT 
Comment on attachment 150509 [details]
Restore interrupts if interrupted during acquire()

We'll just mark it as obsolete ... patch for wrong bug.
Comment 4 Prakash Rangaraj CLA 2010-02-10 01:42:20 EST 
Not for 3.6
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:07:46 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.