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

Running GUI via ./run watch gui will occasionally fail to serve the generated WASM file #5860

Closed
2 tasks
hubertp opened this issue Mar 8, 2023 · 1 comment
Closed
2 tasks
Labels
--bug Type: bug -build-script Category: build script good first issue s-invalid Status: not valid for some reason

Comments

@hubertp
Copy link
Collaborator

hubertp commented Mar 8, 2023

Discord username

No response

What type of issue is this?

Intermittent – Ocurring irregularly

Is this issue blocking you from using Enso?

  • Yes, I can't use Enso because of this issue.

Is this a regression?

  • Yes, previous version of Enso did not have this issue.

What issue are you facing?

Initially reported in the discussion.

Running via ./run gui watch --skip-wasm-opt will start the server but occasionally fail to serve the generated WASM file
hanging the loading of the page.
In the console we would get

Uncaught (in promise) CompileError: WebAssembly.instantiateStreaming(): section (code 10, "Code") extends past end of the module (length 29962350, remaining bytes 27208289) @+185753

The only workaround is to restart the command.

Expected behaviour

Should always serve generated WASM files.

How we can reproduce it?

No response

Screenshots or screencasts

image

Enso Version

develop

Browser or standalone distribution

Chrome

Browser Version or standalone distribution

110.0.5481.100

Operating System

Linux

Operating System Version

No response

Hardware you are using

No response

@JaroslavTulach
Copy link
Member

Obsoleted with GUI rewrite.

@github-project-automation github-project-automation bot moved this from ❓New to 🟢 Accepted in Issues Board Mar 25, 2024
@farmaazon farmaazon added the s-invalid Status: not valid for some reason label Mar 25, 2024
@farmaazon farmaazon moved this from 🟢 Accepted to 🗄️ Archived in Issues Board Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
--bug Type: bug -build-script Category: build script good first issue s-invalid Status: not valid for some reason
Projects
Archived in project
Development

No branches or pull requests

3 participants