Latest download hangs

[gganapat]

Describe the bug The start up hangs on start up at server: 2 after downloading latest version of wolfram-js-frontend.

To Reproduce

Expected behavior

clean start up

Desktop (please complete the following information):

• OS: MacOS
• Browser (Firefox)

[JerryI]

Have you tried to remove wl*, .wl and wljs_, .wljs_* in the project repo?

[gganapat]

Yes, I did what you suggested and removed all files and folders with the above prefixes. (before running wolframscript -f Scripts/start.wl) Still hanging.

[JerryI]

Hm... I am running the same one on my Air M1. It might be occupied port issue. Could you please try

wolframscript -f Scripts/start.wls http 8080 ws 8081 ws2 8082 docs 8085

and a full log might also give additional hints

[gganapat]

Ok, I will do what you suggest. Also, this seems to work on my M1 Mac but not on my M2 Mac. I don;t think it has anything to do with the Mac model. Is is possibly linked to my M2 Mac being work computer and something is blocking now which was the case before? I guess we will know once I run the above on my M2.

thanks, gani -

[JerryI]

It might be somewhat related to permissions. But frankly speaking, I have never seen something like that on Mac. Odd...

[gganapat]

I did what you suggested - still hangs in the same place. Where would the log file be? g-

[JerryI]

Only Electron wrapper can collect logs to a file. Here it must be printed directly to the terminal app you are using.

[gganapat]

How would I collect this info?

[JerryI]

How would I collect this info?

In principle once you start it in the terminal it prints prints... and prints. I believe simple Cmd+A in the text field should do the job

[gganapat]

ok, here is the log file. Do what you can.

Thx! log.txt

[gganapat]

If this helps on my M1 Mac, the next message is:

`

Starting HTTP server for docs... Staring WS/HTTP server...

` Does that mean anything to you?

thx, gani -

[EDIT]: On closer examination, I see a few instances of server: 2, and this was the earliest one matching on my M2 Mac.

[JerryI]

It looks like it hands on self test procedure. Autotest relies on URLFetch, which was reported to be buggy. I would suggest to fetch the changes I made #219 and #218 (no need in removing any folders), which allows to bypass autotest and get more information

wolframscript -f Scripts/start.wls http 8080 ws 8081 ws2 8082 docs 8085 bypasstest True

[gganapat]

Didn't work unfortunately. I cleared cache, downloaded latest version and ran above command. Page is blank and spinning on tab trying to load.

[JerryI]

Oh... The worst case scenario seems to be true. 😢 It is related to CSockets package, I believe. It is based on libuv and written in C.

We need to think about it together with @KirillBelovTest on how to debug this and provide some tools for you.

[JerryI]

Ok. If you like, you can help us with investigating this issue. For this reason, there is a simple demo to check the area of it

clone this repository

git clone https://github.com/JerryI/wl-wlx
cd wl-wlx

and then try to run an example (just plain HTTP server + Sockets + template engine)

wolframscript -f Examples/Basic/Basic.wls

if it shows something on a page.

PS: If not, no pressure. Someone else could do it as well

[gganapat]

Didn't work --

gani-

[JerryI]

Sorry for that, I made a mistake. I pushed changes to WLX repo. Now it should work

[gganapat]

still the same as before - hangs.

[JerryI]

still the same as before - hangs.

This is the same Basic/Basic.wls example (after fetching the recent commit i made to wlx repo), right?..

[gganapat]

No, it was the full one. I will try try the basic one. g-

On Sat, Jun 29, 2024 at 4:32 AM Kirill Vasin @.***> wrote:

still the same as before - hangs.

This is the same Basic/Basic.wls example (after fetching the recent commit i made to wlx repo), right?..

— Reply to this email directly, view it on GitHub https://github.com/JerryI/wolfram-js-frontend/issues/217#issuecomment-2198113404, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK7NNIQVJMIQYBCAHBMZMQ3ZJ2LNXAVCNFSM6AAAAABJ4IBAK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGEYTGNBQGQ . You are receiving this because you authored the thread.Message ID: @.***>

[gganapat]

still hangs.

[JerryI]

Then, confirmed. It is a malfunctioning sockets interface. We will have a meeting soon with co-developers and discuss this issue.