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.

Sign up for GitHub

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

Jump to bottom

Study how to fix issue: Command in Runtime updated only after restarting workspace #12588

Closed
skabashnyuk opened this issue Feb 4, 2019 · 2 comments
Closed

Study how to fix issue: Command in Runtime updated only after restarting workspace #12588

skabashnyuk opened this issue Feb 4, 2019 · 2 comments
Assignees
@sleshchenko
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P2 Has a minor but important impact to the usage or development of the system. status/in-progress This issue has been taken by an engineer and is under active development.
Milestone
Backlog - Platform

Comments

@skabashnyuk
Copy link
Contributor

Description

According to @sleshchenko 's quick study of the issue #12333 Command in Runtime updated only after restarting workspace - there is no quick and easy solution.
The goal of this task is to describe the current situation, propose a possible solution and decided with stakeholders how to fix #12333.
@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. team/platform labels Feb 4, 2019
@skabashnyuk skabashnyuk mentioned this issue Feb 5, 2019
Closed
15 tasks
@sleshchenko sleshchenko self-assigned this Feb 6, 2019
@sleshchenko sleshchenko added the status/in-progress This issue has been taken by an engineer and is under active development. label Feb 6, 2019
@skabashnyuk skabashnyuk added the severity/P2 Has a minor but important impact to the usage or development of the system. label Mar 6, 2019
@che-bot
Copy link
Contributor

che-bot commented Sep 7, 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 Sep 7, 2019
@skabashnyuk skabashnyuk added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 7, 2019
@skabashnyuk skabashnyuk added this to the Backlog - Platform milestone Oct 10, 2019
@skabashnyuk skabashnyuk removed the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jul 23, 2021
@skabashnyuk
Copy link
Contributor Author

won't fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sleshchenko sleshchenko

Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P2 Has a minor but important impact to the usage or development of the system. status/in-progress This issue has been taken by an engineer and is under active development.
Projects
None yet
Milestone
Backlog - Platform
Development

No branches or pull requests
3 participants
@skabashnyuk @sleshchenko @che-bot