Continue is throwing an error and not working on startup about continue HOT 5 CLOSED

Ahh yep that does appear to have worked thanks!

Shall I leave this issue open for enhancement references? or would you like me to create two new feature request issues for your points?

from continue.

Let's leave this issue open, and I'll close once I've made the updates (they're all small enough that I'm comfortable not creating a new issue). First is already done, and I'll take a look at the second soon. A third is adding this to the troubleshooting docs

from continue.

Closing now that better error handling has been added, troubleshooting docs have been expanded, and I haven't spotted a zombie process since adjusting the setup of Meilisearch. If there are still problems feel free to re-open!

from continue.

Continue is trying to kill an old meilisearch process to set up a new one, but the old process is for some reason detached. What you can do is: lsof -i :7700 to get the process ID of the currently running meilisearch process and then kill -9 <PID> to kill it. I would expect this to solve the issue

from continue.

And on our end there's a) better error handling to add here, and b) a need to stop zombie processes from being created

from continue.