-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
VS HexEditor pane comes up blank #13532
Comments
I'm using ms-vscode.hexeditor, version 1.9.14, installed from the Extensions pane. Theia version 1.47.0, in a web browser. |
This seems fixed in 1.48.0. Please let us know if it's still a problem for you. |
FYI, preview is avilable here: https://download.eclipse.org/theia/ide-preview/1.48.0/ |
My development build still has obfuscated variable names and a single bundle.js. However, some searching around came up with a pretty good match on this: https://greasyfork.org/en/scripts/457386-scenexeutils/code (Do a search within the page for "could not find typed array for code") |
It seems the remaining problem is related to how
The script fails with the same error I get from the hex editor.
When I flip the flags |
I have filed kriszyp/msgpackr#135 |
Let's wait an see how they react to the issue. |
Fixes eclipse-theia#13532 Contributed on behalf of STMicroelectronics Signed-off-by: Thomas Mäder <t.s.maeder@gmail.com>
Fixes #13532 Contributed on behalf of STMicroelectronics Signed-off-by: Thomas Mäder <t.s.maeder@gmail.com>
I've installed the VS Hex Editor extension using the Extensions manager. Whenever I try to open a file using it, the pane is empty. It's using a webview, which from experience causes problems for some Theia installations. But webview works fine for things like image viewing. (I've had to set the webview endpoint to
{{hostname}}
in order to get it to work.)Attached is a screenshot of the two errors that appear in the JavaScript console.
Is there anything else I need to configure for the hex editor to function properly?
Originally posted by @profbbrown in #13519
The text was updated successfully, but these errors were encountered: