This message was deleted.
# ask-for-help
s
This message was deleted.
🍱 1
👀 1
s
That's expected behavior; do we not log that it doesn't work?
t
We say this it looks like:
Copy code
[WARNING] [cli] Due to circus limitations, output from the reloader plugin will not be shown on Windows.
which I take to mean, it's working, we're just not showing the output?
s
Oh, maybe I'm wrong then. @Aaron Pham do you know?
a
So
--reload
will still work on windows, but the logs from the plugin wouldn’t be shown.
s
This doesn't seem to be true; reload doesn't work for me either.
a
ah I just checked with circus, seems like stdout and stderr stream aren’t supported on Windows, which means that the reloader plugins watcher won’t work. This has to do with we are sending a reload signals whenever files are changes, which depends on whether the stdout and stderr streams are setup or not. In windows case, none of the streams are setup, so reload aren’t working on windows Probably a sensible solution for this is to error out when user use
--reload
on windows?
Or we can support
--reload
windows, but maybe not through circus
s
I don't really understand what you mean
are the signals dependent on std* being setup?
a
yes
s
why does it use stdout anyway?
a
stderr
s
sure, why does it use those streams?
I was under the impression that circus used rabbitmq normally
a
circus use zmq, but I’m not entire sure why this is the behaviour
s
right
b
--reload
doesn't work for me as well on ubuntu 18.04 and with firefox browser
s
You might want to start a separate thread for that, this one is specifically about Windows.
b
sure. Thanks for pointing out.