#`convex dev --start` leaves `next dev --turbopack` running after `Ctrl+C`

1 messages · Page 1 of 1 (latest)

heady jasper
#

Hi, I may have found an issue with convex dev --start where the command started via --start is not always killed on Ctrl+C.
I can reproduce it locally with Next.js/Turbopack on macOS, specifically when running through bun run dev, and I’m trying to figure out whether this is specific to my setup or something others can reproduce too.
Issue: https://github.com/get-convex/convex-backend/issues/441
PR: https://github.com/get-convex/convex-backend/pull/442
If anyone else has seen this too, a quick reply or reaction would be really helpful.

GitHub
`convex dev --start` leaves `next dev --turbopack` running after `C...

Summary When running convex dev with --start through Bun's script runner, pressing Ctrl+C stops the Convex dev process but does not always stop the command started via --start. In my case, the ...

GitHub
Fix `convex dev --start` exiting before cleanup finishes on Ctrl+C ...

Summary

forward SIGINT immediately to detached --start commands so sidecar shutdown begins as soon as convex dev receives Ctrl+C
keep the cleanup-time SIGTERM fallback for --start commands that do...

granite latchBOT
#

Thanks for posting in #1088161997662724167.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.

    - Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
    - Use [search.convex.dev](https://search.convex.dev) to search Docs, Stack, and Discord all at once.
    - Additionally, you can post your questions in the Convex Community's #1228095053885476985 channel to receive a response from AI.
    - Avoid tagging staff unless specifically instructed.

    Thank you!