2024 meetings - Githubissues

oliver-sanders commented 7 months ago

oliver-sanders commented 7 months ago

Agenda:

Cylc-8.3.0

aim for March, this is pretty urgent
triage: drop all non-essential issues back to 8.4 or 8.3.x
cylc set is essential, but we can push cylc remove and skip-mode back
the remaining optional outputs work is less critical, since we took expire out of the mix

Cylc-8.2.5

UK team still think this is worth releasing, before 8.3.0 gets out
(NIWA side: I don't mind either way, no pressing 8.2.4 bugs are affecting us that I'm aware of)
OS to review 8.2.x and 8.2.5 milestones tomorrow

Migration:

Open questions (link above)

Multi-user gscan

this is viewed as a requirement at BOM, due to a significant number of production role accounts
in principle the UI can manage multiple subscriptions to multiple (user-specific) UI Servers, and users would appear at the top level of the gscan hierarchy, but to date we've had to concentrate on efficiency and stability of the single-user subscription
to do multi-user properly there's quite a lot to consider, e.g. what determines which other users you can see, load on the UI for many users, etc. -- it may be an option for BOM to do this via a local UI extension (even a separate "gscan view" perhaps); but note that development and code review resources are currently very limited, so it might have to be maintained separately for a good while with no guarantee to be merged as-is

AWS Batch

some MO work going is going on now with Cylc on AWS
NIWA has a dev 1-day per week for a while, considering cloud platform support in Cylc (just starting)

oliver-sanders commented 5 months ago

8.3.0 release 😬
partially satisfied tasks in branched graphs
suicide triggers in the UI / datastore
Consider creating share/cycle/<cycle> dirs in Cylc? Would need a matching env var.
DS: NIWA operations conversion gotchas?
- show prerequisites in the GUI
- unset prerequisites? (n.b. comment in proposal)
- Easily get a task to "go back to waiting on prerequisites, and run when satisfied"
- jobs that are actually in one state, but reported to be in another by the job runner (really quite common) .. 1 move/action as opposed to several and an understanding of Cylc8 concepts
JR bug? https://cylc.discourse.group/t/possible-race-condition-in-global-cylc-reload/949/2
Open questions

hjoliver commented 4 months ago

5 June Meeting

Primarily: 8.3.0 release. The previous agenda still applies!

Other: ...

oliver-sanders commented 2 months ago

Agenda:

CYLC_SHARE_CYCLE_DIR
- Some concern on the FS impact of per-cycle directories.
- Is this legitimate? We are already doing this for the log directories.
  - (HO: not very legit; we can provide them, but they don't have to be used, and can be hand-rolled if not provided)
- Should we develop the housekeeping tools for this before implementing?
How to prevent a future sub-graph from running
- This is a new use case made possible by SoD allowing downstream tasks to be removed implicitly.
- At Cylc 7, only explicit task removal was possible (although users usually reset tasks to succeeded to skip them).
  - (HO: the above two points are only partly true. In Cylc 7 you have to explicity remove the first pre-spawned task of an unused branch but anything downstream of that would in fact be "implicitly removed")
- What are the use cases for implicit task removal (as opposed to removing/skipping by task/family/cycle)?
  - (HO: primarily the classic non-clock task expire use case: external circumstances say I don't need to run task-x and the sub-graph downstream of it)
- How should downstream impacts be handled (to avoid stall)?
BoM corrupted DB issue
- How are these databases getting corrupted? Need information from BoM.