Bypass spurious reload button #32
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reload button does nothing which I think must mean there is some logic somewhere that is supposed to load these extensions locally that is not working or not implemented. Until we find it bypassing is probably a good move because otherwise it makes it look like the extension is not running and working even though it really is (it is just running remotely). This will be a temporary measure to solve coder/code-server#4600.
jsjoeio
approved these changes
Dec 23, 2021
|
Good point! I checked and they do indeed have the same problem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reload button does nothing which I think must mean there is some
logic somewhere that is supposed to load these extensions locally that
is not working or not implemented.
Until we find it bypassing is probably a good move because otherwise it
makes it look like the extension is not running and working even though
it really is (it is just running remotely).
This will be a temporary measure to solve
coder/code-server#4600.
As an aside, I tried upgrading to VS Code 1.63.2 but the problem persisted.