Skip to content

Conversation

code-asher
Copy link
Member

This fixes collisions where VS Code is serving a workspace with the same
name but on a different machine and hosted on the same domain.

I have an e2e test for this on the code-server side.

This fixes collisions where VS Code is serving a workspace with the same
name but on a different machine and hosted on the same domain.
@code-asher
Copy link
Member Author

Another way of fixing this would be to make the state stored server-side but this would be a much more intrusive patch and bring us (possibly permanently) out of alignment with upstream.

This will cause a loss of current state so users will have to reopen any files they had open but I was not sure if it was worth copying the old state into a new database.

Copy link

@jsjoeio jsjoeio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another way of fixing this would be to make the state stored server-side but this would be a much more intrusive patch and bring us (possibly permanently) out of alignment with upstream.

Based on this information, I agree. We should choose the least intrusive patch. Thanks for noting this!

minor nit about code comment

@code-asher code-asher requested a review from jsjoeio February 18, 2022 18:12
Copy link

@jsjoeio jsjoeio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@code-asher code-asher merged commit 6337ee4 into coder:main Feb 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants