#on a similar context around this issue
1 messages · Page 1 of 1 (latest)
haven't heard this reported no, but also wonder if https://github.com/dagger/dagger/pull/6354 fixes this too
This PR changes how services are stopped:
Calls to Service.Stop now block until the service exits
Services are now stopped using SIGTERM instead of SIGKILL
This can be changed by setting the new...
@wind chasm I reproduced this if you call svc.Stop only. If I add tunnel.Stop then I can re-run the dagger up command without any issues. I think that in the version you were testing you did not have the tunnel.Stop. I don't think it should hang if a user forgets to call Stop on the tunnel, but I thought the clarification was worth it
ok, that's good to know. I'll create an issue about this in v0.9.6 and reference the above issue just to make sure it's under @wraith mountain 's radar
we should also do the same for the double Stop thing @hidden python
awesome 🎉
hmm I think this only happens with dagger-in-dagger. I need more time to get a basic repro. In the meantime I'll open Matia's issue