Summit web frontend: Show the blocker tasks for blocked tasks.

[ermo]

This is a QoL improvement that will show which tasks need to be completed before a blocked task will be unblocked.

[ermo]

I am unsure how this would work in practice. Perhaps a floating tooltip when you hover over the Blocked status?

Any other ideas?

[flippedbits]

I did start to look into this and kinda rabbit holed trying to figure out what usable data I could get from where. The only thing i really found was this when added to the task_blockers table:
let blocker_id = format!( "{}_{}@{}/{}", removed.meta.source_id, removed.task.arch, removed.task.project_id, removed.task.repository_id );

So not super helpful from a users perspective.

I assume we would want to show something like (task_id, package_name). If i had those then I could either add a hover as mentioned above (simple) or with a little JS have the task expand with the blocker(s) listed (and if we wanted to get 'fancy' have them clickable so we can redirect to the task itself, would need to add a route like /tasks/[task_id] and probably recreate the existing summit 'Task Overview' page)

[ermo]

@flippedbits I like where you are taking this.

[ermo]

@flippedbits I just did some sql experimenting:

If I do a query that looks like this on the service db:

SELECT task.task_id,package_id,task_blockers.blocker FROM task INNER JOIN task_blockers ON task.task_id = task_blockers.task_id WHERE task.status = 'blocked' AND task.task_id = 892;

I get output like:

892|zenity-4.0.5-2.x86_64|autocc_x86_64@1/1
892|zenity-4.0.5-2.x86_64|polkit_x86_64@1/1
892|zenity-4.0.5-2.x86_64|pulseaudio_x86_64@1/1

Is this useful to you?

If we were allowed to use JS, maybe we could have a pop-over enter from the right with the list of blockers and a scrollbar when the blocked UI element is clicked?

For context, I believe the @1/1 at the end refers to project, profile or repo dbs respectively (not entirely sure which is which at this stage)

@tarkah How close am I with ^?

[flippedbits]

I am not super clear on your pop over/scrolling description, maybe quick little drawing would help.

For the moment I have made a draft PR, that uses a left join to get the blockers and adds them as a title attribute on the blocker status element (screen shot in PR). Since we don't have any additional blocker data, like ids etc the title attribute seemed the simplest for now.

[ermo]

I am not super clear on your pop over/scrolling description, maybe quick little drawing would help.

Imagine clicking on the blocker button/link, and then an "overlay card" slides in from the right over the underlying layer, with a list of clickable blocker items.

The card should have a close button.