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

Can't run any of editor because of command 'visual-scxml-editor.*' not found #45

Open
filug opened this issue May 28, 2023 · 9 comments
Assignees
Labels
bug Something isn't working high-value Solving this provides large value medium-effort 4–8 hours of work

Comments

@filug
Copy link

filug commented May 28, 2023

Preconditions

  1. vscode version: 1.78.2 b3e4e68a0bc097f0ae7907b217c1119af9e03435 x64
  2. Visual SCXML Editor version: v0.5.0
  3. host: Linux Bullseye, amd64

Scenario

  1. Hit F1
  2. select: 'SCXML Editor: Create Blank State Machine'

Error

image

Notes

I get similar error in case when I'm trying to open existing SCXML file. Then error looks like

image

I've tested several configurations:

  • as standard (native project),
  • as Dev Container project,
  • Remote-SSH + Dev Container

erros are always the same.

@diabluz
Copy link

diabluz commented May 31, 2023

I had the same issue, I'm running it on Linux and looking at the Developer Tools console it said it could not find "./editorglue" and would fail to load the extension. "EditorGlue.js" indeed exists and I presume this works in Windows as it does not care about case, but in Linux it matters, to fix it: inside extension.js is I changed:
const editorglue_1 = require("./editorglue");
to
const editorglue_1 = require("./EditorGlue");

ps. This is a great extension by the way!

@Phrogz Phrogz self-assigned this Jun 28, 2023
@Phrogz Phrogz added bug Something isn't working medium-effort 4–8 hours of work high-value Solving this provides large value labels Jun 28, 2023
@Phrogz
Copy link
Owner

Phrogz commented Jun 28, 2023

Trying to figure out how to repro this. The extension works as installed for me on Linux, Windows, and macOS (two of which are case-sensitive). There is no place in the assets or code where EditorGlue is used with that casing as a file name; it only exists as a class name. The file extension.js described by @diabluz must be a generated file, compiled from the TypeScript.

@diabluz
Copy link

diabluz commented Jun 29, 2023

Hello Phrogz, thanks a lot for checking, some additional input, I run Visual Code on Windows for editing code on a remote target using the ssh (ms-vscode-remote.remote-ssh), so Visual Code installs the scxml plugin to the remote Linux (Fedora) server, maybe it adds those lines during the remote installation?
The full path for the file in the remote linux machine is:
~/.vscode-server/extensions/phrogz.visual-scxml-editor-0.5.0/out/extension.js

@Phrogz
Copy link
Owner

Phrogz commented Jun 29, 2023

@filug Are you also using it on a remote target when this error occurs?

@ste93
Copy link

ste93 commented Aug 29, 2023

Hello everyone,

I have the same problem, I've tried to use the solution proposed by @diabluz but it raises the following error

Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self' https://*.vscode-cdn.net". Either the 'unsafe-inline' keyword, a hash ('sha256-ICa0DhwZQJsOd/Rn0N8H6FdQ71GfNL+op2zhAQ+Y4mM='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.

Does anyone knows how to solve it?

@jwoillez
Copy link

Same error for me with a RemoteSSH target. Works fine when local.

@filug
Copy link
Author

filug commented Nov 18, 2023

@filug Are you also using it on a remote target when this error occurs?

In all cases.

I can reproduce this issue while I'm

  • opening project as a normal (native?) project,
  • and also when I'm using Devcontainers,
  • and also when I'm using Remote-SSH access and open project on remote host.

In other words, so far, I was not able (unfortunately) to use this plugin on Debian 11 based workstation (others were not tested by me).

That's what I was using today to test this issue

VS Code version

Version: 1.84.2
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:50:47.800Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Linux x64 5.10.0-26-amd64

Visual SCXML Editor extension

version v0.5.0

Published 2023-02-28, 01:42:33
Last released 2023-03-03, 04:09:57
Last updated 2023-11-18, 16:46:00
Identifier phrogz.visual-scxml-editor

@SanneMarx
Copy link

Same error here when using VS Code on Windows, connected to Windows Subsystem for Linux running on the same machine
No issue when doing it all within the Windows environment

@DAtek
Copy link

DAtek commented Oct 21, 2024

Same issue on LinuxMint 21.3, extension doesn't work at all

kép

Visual SCXML Editor extension: 0.5.0
VS Code version: 1.94.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working high-value Solving this provides large value medium-effort 4–8 hours of work
Projects
None yet
Development

No branches or pull requests

7 participants