Endpoints not working as expected - Intermitent 500 errors + ghost endpoints

[CRBroughton]

Hi there, just been playing around with Encore as I'm looking for a new back-end solution. Started with your built in hello world example and copied over the endpoint to create a new one in the same hello.ts service file, but I'm getting the following issue:

Screencast.from.10-12-24.08.47.48.webm

Seemingly any endpoint I create can cause this behaviour. I've also noticed that endpoints I create, and then delete will sometimes still appear in the list of endpoints despite no longer existing. Just started using Encore today so presumably I'm on the latest version.

Edit: The part about the endpoints randomly returning 500's only seems to happen through the Encore UI. When I restart my PC the issue disappears, which to me suggests that there's some sort of background service that isn't properly restarting or taking into account the new endpoints / code generation issues.

Edit II: Can confirm killing the encore processes results in the same proper behaviour; The endpoints now properly return 200's and are no longer flaky (seems to be the daemon process that's left running in the background, maybe this should reboot on code change?). Obviously isn't a good solution to have to manually kill the process.

Bit of a side note (something I just noticed) but after closing down the running application, the front end seems to continue to believe the application is still running (the green dot in the top-left never changes, has this an active Websocket or SSE connection?).

Ghost endpoints video:

Screencast.from.10-12-24.12.34.10.webm