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

Interaction with Tasks when running multiple ones #13396

Closed
slemeur opened this issue May 22, 2019 · 4 comments
Closed

Interaction with Tasks when running multiple ones #13396

slemeur opened this issue May 22, 2019 · 4 comments
Labels
kind/question Questions that haven't been identified as being feature requests or bugs. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.

Comments

@slemeur
Copy link
Contributor

slemeur commented May 22, 2019

Description

When the user is starting multiple tasks, those could be running concurrently and the user might close the outputs tabs from few of those.
How the user can then come back to the outputs of currently running tasks?

@slemeur slemeur added kind/question Questions that haven't been identified as being feature requests or bugs. team/ide2 labels May 22, 2019
@azatsarynnyy
Copy link
Member

Theia provides Terminal > Attach Task... command for that purpose. But looks like it works with Theia's shell type tasks only.

I think it requires some investigation on how that command could be integrated with the functionality provided by the che-machine-exec server.

@evidolob evidolob mentioned this issue May 28, 2019
26 tasks
@evidolob
Copy link
Contributor

@slemeur Are you OK with Artem proposal?

@evidolob evidolob added the status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. label Jun 12, 2019
@slemeur
Copy link
Contributor Author

slemeur commented Jun 20, 2019

As a user, I would like to know all the tasks that are currently running.
Should we list those somewhere ?

@che-bot
Copy link
Contributor

che-bot commented Dec 30, 2019

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 30, 2019
@che-bot che-bot closed this as completed Jan 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Questions that haven't been identified as being feature requests or bugs. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Projects
None yet
Development

No branches or pull requests

5 participants