-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
emscripten issue on runtime - Failed to load 'http://localhost:6931/stdio.html'. #8227
Comments
I see some discussion here: |
Check my PR for emscripten it had a fix and readme changes for this. Maybe
merge
…On Mon, 9 Dec 2024 at 8:12 am, Theodore Watson ***@***.***> wrote:
I see some discussion here:
#8067 <#8067> which
is connected to this issue:
emscripten-core/emscripten#14128
<emscripten-core/emscripten#14128>
—
Reply to this email directly, view it on GitHub
<#8227 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGK2HE6RUWBKF46A3WRORT2ESY23AVCNFSM6AAAAABTHSEXBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRWGM4DGNRYGY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@ofTheo Hello.
|
Actually I get the same error after getting rid of the error above (by just returning a 3 as gl version(?)):
I can only say, that |
I'm seeing the next set of errors in apothecary related to ofxOpenCv
all errors: |
@danoli3 's PR here: I tried adding but I still get the error |
I'll check it out again, it was close last time it did work at some point was running so much faster to. I think the last commit on that PR I still had some issues to fix. |
for ref a backup make that might have worked in July:
|
This is all working now just CSP changes required |
Awesome! When you say working, do you mean you can call emrun and it loads without the stdio error?
The goal is that people should be able to run locally without setting up any cors stuff etc.
|
@danoli3 thanks! I think the goal should be that users can at the least to It was until recently, so I am not sure if this is a recent emscripten change or something at the browser level. I Haven't seen any CSP errors but also haven't got past the stdio.html error. Are you able to push the changes for the |
Following up on this, it looks like emscripten newer the 3.1.60 has the issues with stdio.html I think until we can find a solution we should revert apothecary runner and OF/OF to 3.1.50 which has been confirmed to work and then point people to 3.1.50 in the setup guides. I see this PR was merged, but the emrun / stdio issue was mentioned about not being resolved. @danoli3 I tried the above LD flags and they didn't seem to make any difference to the error |
It works without the error on the PR!
Just CSP stuff
…On Fri, 13 Dec 2024 at 3:03 pm, Theodore Watson ***@***.***> wrote:
Following up on this, it looks like emscripten newer the 3.1.60 has the
issues with stdio.html
I think until we can find a solution we should revert apothecary runner
and OF/OF to 3.1.50 which has been confirmed to work and then point people
to 3.1.50 in the setup guides.
I see this PR was merged, but the emrun / stdio issue was mentioned about
not being resolved.
#8067 <#8067>
@danoli3 <https://github.com/danoli3> I tried the above LD flags and they
didn't seem to make any difference to the error
@Jonathhhan <https://github.com/Jonathhhan> have you been able to get OF
running on >= 3.1.65 locally without the emrun stdio error?
—
Reply to this email directly, view it on GitHub
<#8227 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGK2HDKZMZDDWOZAEYV7ND2FJL7LAVCNFSM6AAAAABTHSEXBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBQGUYDIMBVGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks @danoli3 I think something else is broken in the nightly for emscripten aside from the CORS stuff etc Going to try an older ofxEmscriptenWindow |
PLATFORM_LDFLAGS += -s ASSERTIONS=2 Also we should implement this GLFW port for our uses: I had started to but got stuck in the mud with the libs |
|
Due to CSP block it seems |
After all the other svg / libfmt / texture issues are fixed, I get the above message.
Wonder if it's related to cross domain? or if there is a way to disable?
@Jonathhhan - any idea what this could be related to?
The text was updated successfully, but these errors were encountered: