search

gitpod-io / gitpod

The developer platform for on-demand cloud development environments to create software faster and more securely.
https://www.gitpod.io
GNU Affero General Public License v3.0
12.57k stars 1.2k forks source link

On workspace restart: browser tabs don't reopen non-default workspaces #1647

Open havogt opened 4 years ago

havogt commented 4 years ago

Describe the bug

This is probably between bug report and feature request as I couldn't find documentation for my workflow: I have a project with one main language (python) and a subproject in a different language (C++). For plugins to work nicely I open the subproject in a separate tab (/mysubfolder). This works nicely. However, if the gitpod workspace is stopped and restarted, both browser tabs open the root workspace and the state (e.g. open files) of the subproject-workspace is lost. (workspace is used for two different things in gitpod? for the gitpod workspace instance and the theia workspace?)

Steps to reproduce

  1. Start a workspace
  2. Open a sub-folder of the root workspace in a new browser tab and open some files
  3. Stop and restart the gitpod workspace (keeping browser tabs open)
  4. Both browser tabs open the root workspace and only the state of the root workspace is persisted

Expected behavior

Instead of 4 above, I would expect that each browser tab re-opens with the correct (sub-)workspace and previous state of each workspace.

corneliusludmann commented 4 years ago

Indeed, this is not supported yet. Thanks for this feature request.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

havogt commented 3 years ago

Ping.

(Also, does it make sense to stale a feature request by a bot, after it was recognized as such by a friendly human? The effect on me is changing my perception of the gitpod team from "great community, they instantly reply, even if they cannot work on everything the user wants" to "in the end they don't care, and outsource the dirty work to a bot". ;) But maybe it's the only way to deal with > 1k issues at this point.)

corneliusludmann commented 3 years ago

Hey @havogt,

Thanks for your feedback. We recently introduced this bot because a huge amount of legacy issues have accumulated over time. Most of them are issues like "Hey my workspace does not start!" where we asked for some details but never heard back from the reporter. This causes us to lose track of truly relevant issues. After a controversial debate, we decided to introduce this bot hoping that meaningful issues will emerge as a result of people like you responding to the stale bot for relevant issues. Thanks a lot for your support! :heart: