New dev server buggy on windows

[lhovon]

The new dev server doesn't cleanly exit after Ctrl-C on Windows, and leaves orphaned processes behind.

[timonweb]

@lhovon I don't use Windows, so I can't help here. If anyone with Windows could troubleshoot this and submit a PR, it would be much appreciated!

[EricE]

I may be seeing the same problem (4.2.0, django-tailwind[reload] + daisyUI), after hitting Ctrl-C on Windows 10, the window stops accepting keyboard input, e.g. the Y for Terminate batch job, and I have to close and reopen the window. Happens with both cmd and pwsh windows. I'm a HW guy and Unfortunately I don't know how to troubleshoot this, just wanted to add the data point (though happy to be remotely controlled by somebody who does know how to troubleshoot it).

##########################################################
🚀 Starting Tailwind watcher and Django development server
You can access the server at: http://127.0.0.1:8000/
Press Ctrl+C to stop the servers
##########################################################
18:56:02 system | django.1 started (pid=42400)
18:56:02 system | tailwind.1 started (pid=46732)
18:56:03 tailwind.1 |
18:56:03 tailwind.1 | > theme@4.2.0 start
18:56:03 tailwind.1 | > npm run dev
18:56:03 tailwind.1 |
18:56:03 django.1 | Watching for file changes with StatReloader
18:56:03 tailwind.1 |
18:56:03 tailwind.1 | > theme@4.2.0 dev
18:56:03 tailwind.1 | > cross-env NODE_ENV=development postcss ./src/styles.css -o ../static/css/dist/styles.css --watch
18:56:03 tailwind.1 |
18:56:04 tailwind.1 | /*! 🌼 daisyUI 5.0.50 */

Just checked process explorer and I think it is showing the orphaned processes:
Before ctrl-C (last column, blue, are the PIDs):

After ctrl-c (orphans):

[Abhiojiki]

I am also facing the same issue. If I run Django and tailwind separately they will close gracefully without any issue.

[timonweb]

Unfortunately, this issue won't be fixed due to Windows and Honcho incompatibility. I've added an error message that appears when running python manage.py tailwind dev under Windows, suggesting to use python manage.py tailwind start instead.