Trunk serve stuck

[lpotthast]

Sometimes, a trunk serve just gets stuck at

INFO copying generated wasm-bindgen artifacts

Most of the time, issuing Ctrl+C to exit the process just does nothing.

Sometimes, closing the terminal where trunk was running and opening a new terminal resolves the issue, but sadly not every time. It then gets stuck at the same point, opening a browser window (if configured) but not showing the current state of the application.

I still have no idea why this happens.

[tiye]

similar issue observed, I killed process in Task Activities. CPU occupation looks fine. no idea how that happened.

[simbleau]

I've encountered similar issues, although rarely, where trunk continues to run after shell kill, and requires a process kill. I don't know if this is on my top priority list right now though, since there's a lot of issues right now. Hopefully someone can dive deeper. For now, process kill!

[Jupp56]

This is similar behaviour to https://github.com/thedodd/trunk/issues/321, where it also gets stuck before running into a timeout.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.