You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The extra log files configuration used to be used to allow the GUI to open job log files other than the standard job.out, job.err, etc.
For Cylc 8 we've taken a different approach, the cat-log command now lists the available files from the file system so the GUI can always see all log files without the need for them to be explicitly listed.
However, there is a little bit of legacy code left over:
The logfiles key in the job_config.
The extra_logs field in ProtoBuf.
The extraLogs field in GraphQL.
The jobLogNames field in GraphQL (which now just holds the standard job log names?)
All of which are essentially hardcoded to an empty list I think? We should rip this out.
Non-urgent, but as this implies schema changes it may be better to get it out the way sooner, hence the 8.3.0 milestone, but that can slide.
The text was updated successfully, but these errors were encountered:
The
extra log files
configuration used to be used to allow the GUI to open job log files other than the standardjob.out
,job.err
, etc.For Cylc 8 we've taken a different approach, the
cat-log
command now lists the available files from the file system so the GUI can always see all log files without the need for them to be explicitly listed.However, there is a little bit of legacy code left over:
logfiles
key in thejob_config
.extra_logs
field in ProtoBuf.extraLogs
field in GraphQL.jobLogNames
field in GraphQL (which now just holds the standard job log names?)All of which are essentially hardcoded to an empty list I think? We should rip this out.
Non-urgent, but as this implies schema changes it may be better to get it out the way sooner, hence the 8.3.0 milestone, but that can slide.
The text was updated successfully, but these errors were encountered: