Orphan `sst dev` processes about ion

[AlessandroVol23]

Not sure if connected but I had a same issue here: https://discord.com/channels/983865673656705025/1177071497974648952/1222858865515692162

An SST V2 app was running and I couldn't start sst dev
The output was the following:

time=2024-03-28T14:06:17.782+01:00 level=INFO msg="checking for pulumi" path="/Users/alessandrovolpicella/Library/Application Support/sst/bin/pulumi"
time=2024-03-28T14:06:18.034+01:00 level=INFO msg="checking for bun" path="/Users/alessandrovolpicella/Library/Application Support/sst/bin/bun"
time=2024-03-28T14:06:18.034+01:00 level=INFO msg=args args=[] length=0
time=2024-03-28T14:06:18.035+01:00 level=INFO msg="no existing server found, starting new one"
time=2024-03-28T14:06:18.036+01:00 level=INFO msg="waiting for server to start"

[VirtuaBoza]

I am currently experiencing sst dev exit/fail silently, and I don't have an orphaned sst process running. I just restarted my machine to be sure.
output:

➜  top git:(main) ✗ sst dev --verbose 'next dev -p 3000'
time=2024-03-28T14:41:27.627-04:00 level=INFO msg="checking for pulumi" path="/Users/aboza/Library/Application Support/sst/bin/pulumi"
time=2024-03-28T14:41:27.711-04:00 level=INFO msg="checking for bun" path="/Users/aboza/Library/Application Support/sst/bin/bun"
time=2024-03-28T14:41:27.711-04:00 level=INFO msg=args args="[next dev -p 3000]" length=4
time=2024-03-28T14:41:27.712-04:00 level=INFO msg="no existing server found, starting new one"
time=2024-03-28T14:41:27.712-04:00 level=INFO msg="waiting for server to start"
SST ❍ ion 0.0.229  ready!

➜  App:        stacks-ils-ion
   Stage:      aboza
   Console:    https://console.sst.dev/local/stacks-ils-ion/aboza

~  Deploying

Then it exits instead of running next dev (presumably)

[VirtuaBoza]

sst remove and then sst dev seemed to resolve my issue here, but ovbs i can't do that every time this happens.

[VirtuaBoza]

sst remove and then sst dev seemed to resolve my issue here, but ovbs i can't do that every time this happens.

Not a reliable remedy it turns out.

[VirtuaBoza]

here's a facsimile of my repo: https://github.com/VirtuaBoza/sst-repro-2

[VirtuaBoza]

sst.log
event.log

[thdxr]

i think we've fixed this in 0.0.240 but it might still happen in other situations - post a new issue if you see it