I’m certainly not trying “to win”, but we must get to a baseline of understanding:
- it’s supposed to auto-restart on back-end code changes.
d/shutdown_dev; d/boot_devshould only be necessary when you change the population of plugins not just individual lines of code.
This should reduce where you need to look to fix things.
I just git pulled and tried a change, it restarts, so it’s not a build regression.
The even weirder part for me is that being a docker setup, it’s actually harder to inadvertently override the packaged behaviour, so it should be more reliable.
I will try this out on my docker build when I get home.
Appreciate this is frustrating and annoying as a workflow at present, it would certainly annoy and frustrate me.
If you’ve fully cleared your cache I’m not sure what to suggest at this stage.
Note that initializers only run once when you open the page for the first time. So the server processes restarting is moot (and only covers the back-end code).