Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFE] Surface the Task Manager in the UI #171

Closed
rromannissen opened this issue Apr 9, 2024 · 4 comments
Closed

[RFE] Surface the Task Manager in the UI #171

rromannissen opened this issue Apr 9, 2024 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/normal Higher priority than priority/minor. Nice to have. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@rromannissen
Copy link
Contributor

rromannissen commented Apr 9, 2024

What is the problem?

There's no way for the user to understand which tasks are being executed and the queue of pending tasks.

Why is this a problem?

By not knowing what is being executed and scheduled at a given moment, users might feel like the system is unresponsive, especially in multi-user environments.

Proposed solution

Surface information about what is queued for execution by the task manager. This view should provide a way for users to:

  • Browse the task queue. For each task the following information should be provided:
    • Task ID.
    • Task type: Analysis, discovery...
    • User that created the task.
    • Status: Scheduled, In progress...
  • Cancel background tasks like automatic language/technology stack discovery (see [RFE] Automatic language and technology discovery for applications #170 for more information about this). Cancelled background tasks will be rescheduled again automatically at the end of the queue.
  • Cancel the tasks created by the current user. Tasks created by other users can't be cancelled.
@rromannissen
Copy link
Contributor Author

@jortel @mansam @JustinXHale for your consideration.

@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. labels Apr 9, 2024
@dymurray dymurray added this to the v0.5.0 milestone Apr 19, 2024
@sjd78 sjd78 added kind/feature Categorizes issue or PR as related to a new feature. priority/normal Higher priority than priority/minor. Nice to have. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. labels May 30, 2024
@jortel
Copy link
Contributor

jortel commented Jun 6, 2024

@dymurray dymurray closed this as completed Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/normal Higher priority than priority/minor. Nice to have. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: ✅ Done
Development

No branches or pull requests

4 participants