search

lustre-labs / dev-tools

Lustre's CLI and development tooling: zero-config dev server, bundling, and scaffolding.
45 stars 15 forks source link

Websocket connection issues #39

Closed mooreryan closed 3 months ago

mooreryan commented 3 months ago

I'm not sure if this is something that the dev_tools even has any control over, but if you run a project with gleam run -m lustre/dev start, then navigate google chrome to the http://localhost:1234, then force close the devtools with Ctrl-c Ctrl-c, after a couple of moments you get this:

lustre_dev_tools_bug_2

and eventually this:

lustre_dev_tools_bug

in which eventually 100% of the cpu is being used.

Is this just a browser issue, or something that dev_tools could address?

hayleigh-dot-dev commented 3 months ago

in which eventually 100% of the cpu is being used.

LOL that is not good. The client is supposed to periodically check to see if the connection is back (this is nice because if you restart the dev server you can pick up where you left off) but I guess there is a bug with the logic and maybe we have a memory leak or something.

I'll investigate :)

hayleigh-dot-dev commented 3 months ago

OK this should be solved now – if its still not working correctly after this release I will just remove the reconnect logic for the timebeing, please re-open the issue if you run into it again.