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

Add folder to workspace results in grey screen #309

Closed
Muruloki opened this issue Mar 21, 2019 · 8 comments · Fixed by #317
Closed

Add folder to workspace results in grey screen #309

Muruloki opened this issue Mar 21, 2019 · 8 comments · Fixed by #317
Assignees
Labels
bug Something isn't working

Comments

@Muruloki
Copy link

Muruloki commented Mar 21, 2019

  • code-server version: code-server-1.32.0-310-linux-x64
  • OS Version: Ubuntu 16.04.6 LTS

Description

First of all, thanks a lot for this prioject, it's awesome! :)

I'm running binary on remote server; when i try to add a folder to the workspace (even if i assign keyboard shortcut) all i see is grey screen; have to edit workspace.json to remove 2nd folder and reload client in the browser to make it work again. Is this a feature or bug? Changing folders using ctrl-k ctrl-o works fine. However using UI it doesn't work.

Some other issues i've noticed:

  • can't install extensions; however it's fine since i can just install then on my local instance and then copy folders over to remote. When trying to install using UI i'm getting this:

Cannot read property 'local' of undefined
Failed to install 'compulim.compulim-vscode-closetag'.

  • Markdown preview doesn't work: command 'markdown.showPreviewToSide' not found. However makdown preview enhanced extension works fine so again, not a big deal.

Thanks.

@Muruloki Muruloki added the bug Something isn't working label Mar 21, 2019
@nol166
Copy link
Contributor

nol166 commented Mar 21, 2019

@Muruloki it's a bug for sure

@nol166
Copy link
Contributor

nol166 commented Mar 21, 2019

What version of compulim.compulim-vscode-closetag are you using?

@Muruloki
Copy link
Author

@nol166 oh, that was just random extension; it happens to any of them. For example just tried Angular 7 Snippets - TypeScript, Html, Angular Material, i think it's v7.2.5

Cannot read property 'local' of undefined
Failed to install 'mikael.angular-beastcode'.

I'm using UI to install. If i try to use extensions: isntall from file it will complain about improper tar format or something like that. Reading other comments here it looks i have to install bsd tar since gnutar has some issues unpacking the vscode extensions but again, i didn't try to do that since there is a relatively easy workaround.

@foresthoffman
Copy link
Contributor

Hello @Muruloki, there is a pending PR (#245) which will fix the bug prohibiting installation from VSIX. The difference between bsdtar and gnutar shouldn't matter. The problem was the assumption that the VSIX is in TAR format rather than the standard ZIP.

Extensions:

It's unusal that the markdown.showPreviewToSide command isn't working, since the extension default is included under lib/vscode-default-extensions/extensions/markdown-language-features, but i'm seeing the unregistered command error as well. Good to hear that there is an alternative.

Thanks,
Forest

@Muruloki
Copy link
Author

Muruloki commented Mar 21, 2019

@foresthoffman Great, thank you. As for markdown, i think it was already reported, #296

What about adding folder to workspace, do you know why it's resulting in blank grey screen? :)

@foresthoffman
Copy link
Contributor

foresthoffman commented Mar 21, 2019

I'm not certain as to the root of the issue, but I do receive the following error:

ERROR  Failed "Start workbench" duration=1002ms
13:04:28.756 main.js?f92d:1 duration (i): i {expected: 1000, ms: 1553191467376}
13:04:28.757 main.js?f92d:1 error (Error): Error: [UriError]: Scheme contains illegal characters.
    at _validateUri (uri.ts?336c:38)
    at _URI.URI (uri.ts?336c:175)
    at new _URI (uri.ts?336c:391)
    at Function.URI.revive (uri.ts?336c:367)
    at Object.reviveWorkspaceIdentifier (workspaces.ts?067d:38)
    at CodeRendererMain.reviveUris (main.ts?bd53:89)
    at CodeRendererMain.init (main.ts?bd53:70)
    at new CodeRendererMain (main.ts?bd53:61)
    at main (main.ts?bd53:331)
    at Workbench.eval (workbench.ts?f527:192)

The issue appears to be coming from lib/vscode/src/vs/base/common/uri.ts, which is odd.

You can recover from the failed workspace load, by clearing your cache.

@nol166
Copy link
Contributor

nol166 commented Mar 21, 2019

You can also delete workspace entry from local storage until the actual issue is fixed.

@foresthoffman
Copy link
Contributor

Should be fixed by #317.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants