-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
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
Running family displayed without any tasks #2095
Comments
@ColemanTom what tasks are under the |
I should mention, ui 2.5.0 I think, and cylc-flow 8.3.6. First I've seen it, and it's been months of running many workflow. I'm not able to update versions as we are essentially in a freeze in prep forva release to operations. |
I dont have a complete list, but at a guess, 100+.no refresh does not change anything. |
It's possible this is already fixed on 8.4.x, or even possibly might be fixed by cylc/cylc-flow#6589 |
How does GraphQL get its information? When I look at the DB, I can't see any mention of running tasks in the |
It's probably due to a bug in constructing the datastore that feeds the UI, and probably already fixed as noted above. At least, I think a suspiciously similar problem was fixed. Have you tried stopping and restarting the workflow, to force reconstruction of the datastore? |
Not intentionally, but a colleague did happen to stop and update it today, and there is no permanent running task. |
Sorry, does that mean the problem remains, after the restart? |
After stop/play, the problem is not present. I am always hesitant to stop/play things in case there is debug information you want extracted. I do have the DB, scheduler logs and job logs saved for reference purposes, but it sounds like they wouldn't be that useful if it is a transient data store in memory. |
Yes, I don't think any of the routine stored info would help much to debug this (unless perhaps it happened as a result of a series of logged interventions). Good to know that the restart fixed it - that pretty much confirms it's the datastore (perhaps with a small chance of it being a bug in how the UI applies the data feed). There's probably not much we can do unless we have a reproducible case to examine, and then the first thing would be to run it with the latest Cylc code to check if it's fixed already. |
Originally posted by @ColemanTom in #1999
GraphQL
Query:
Response:
The text was updated successfully, but these errors were encountered: