We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is an unexpected delay before many cylc commands work after workflow startup.
If I run a workflow, cylc ping (and other commands) still fail after 20s.
cylc ping
$ cylc vip -n start-up-test; sleep 20s; cylc ping start-up-test ... WorkflowStopped: start-up-test/run1 is not running
However, if I run cylc scan first, cylc ping works immediately after start-up.
cylc scan
This needs run hosts enabled to reproduce; it is not reproduceable if using --host=localhost.
--host=localhost
All commands should be able to interact with workflows immediately after startup.
The text was updated successfully, but these errors were encountered:
(Edited for clarity around run hosts)
Sorry, something went wrong.
Superceded by #6506
No branches or pull requests
Description
There is an unexpected delay before many cylc commands work after workflow startup.
Reproducible Example
If I run a workflow,
cylc ping
(and other commands) still fail after 20s.However, if I run
cylc scan
first,cylc ping
works immediately after start-up.This needs run hosts enabled to reproduce; it is not reproduceable if using
--host=localhost
.Expected Behaviour
All commands should be able to interact with workflows immediately after startup.
The text was updated successfully, but these errors were encountered: