-
Notifications
You must be signed in to change notification settings - Fork 19
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
troubleshooting #638
troubleshooting #638
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good.
This is on an upstream branch, please contribute!
Erm, what do you mean by this? Are you suggesting we don't just merge individual PRs to master as usual, to incrementally upgrade the troubleshooting section?
The branch this PR is on is a cylc/cylc-doc branch NOT an oliver-sanders/cylc-doc branch, that means you can push new commits to this PR. I.E. I have intended this PR to be collaborative. |
Roger that (well, I think we tend to allow pushes to each other's branch too, but I guess a central branch is more clearly for that purpose). |
Should add "Disk IO Error" (ran out of disk space)
|
Addressed feedback, fleshed this out a bit. I think there's enough here to make it worthwhile merging this now so changed the milestone. |
(rebased) |
d38d8c4
to
e3ed685
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I was going to add a couple of things, but it might be better to get it in then I'll propose those additions.
For the record my other thoughts were:
- Did your script fail because you needed to
chmod
? log/config/flow-processed.cylc
shows you the effect of Jinja2 templating.log/config/01-start-01.cylc
shows you the effect of Jinja2 and task parameter expansions.
For the record my other thoughts were:
Good idea.
Good idea, we could do with a general Jinja2 debugging section including
I'm not sure we expand task params, or maybe just in runtime? Can't remember. Good to raise awareness of the config log directory, explain the file numbers and names and why they are useful. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely need this in 8.3.0
@wxtim - do you want to (or have you) posted another issue for your additional points above? #638 (review) |
It's #725 |
Comments addressed bar a couple. |
Co-authored-by: Hilary James Oliver <[email protected]>
The beginnings of a Cylc 8 troubleshooting section, mostly aimed at users as opposed to sys-admins.
This is on an upstream branch, please contribute!
Specific troubleshooting for platform setup issues (sys-admin targetted content) is probably better placed in
src/reference/config/writing-platform-configs.rst
.Requirements check-list
CONTRIBUTING.md
and added my name as a Code Contributor.