Oct 2020 Meeting Notes

• Re-evaluate how close we are to the beta release MVP. Still TODO (parentheses: essential for 8.0 but maybe for beta):

  • integrated mutations
  • n-edge window (n=1 scheduler, n=N UIS via DB)
  • (start stopped flows from UI) (but pretty easy)
  • (fine-grained authorization + cross-user functionality - e.g. for shared oper accounts)
  • more rose suite-run migration:
    • rose-suite.conf plugin
    • cylc install flow source to run directory
      • new cylc run and run-dir semantics (run1, run2 ,...) (not too much work, but lots to discuss and agree on)
    • symlink dirs (MH working on now)
  • more config changes
    • lots of minor stuff to come (we will knock this off for beta)
  • (delta-driven cylc tui - and back-end GraphQL subscriptions)
  • SoD follow-ups (not all essential - need to check)
  • (documentation)
  • finish implementing task status rationalization (including the retry-as-xtrigger PR)
  • (remove current "non-compliant" graph view - agreed to remove; toy view maybe not)
  • (UI display of xtriggers and queues - see the cylc-ui issue)
  • (restore "ssh messaging")
  • cylc review fallback? (also see JupyterLabs integration below)
  • TIMELINE: Dec if possible; Jan more realistic

• Drop the non delta-driven "POC" cytoscape graph view already?

  • (and replace with a trivial toy view, just so we retain multiple views)
  • (agreed to drop - see above)

• Intelligent platform and host selection fallback https://github.com/cylc/cylc-flow/issues/3827

  • TP to work on minimal ssh error version on return from leave (a few days)

• JupyterLabs integration

  • nice file browser; plugins for viewing and editing files
  • rose edit; cylc review?
  • (authorization too?)
  • (vue vs react? vue3 is more react-like - BK; can use vue and react together?)
  • can we integrate? (what interfaces can we support, then mount our stuff on them) - investigation needed
  • (J-Lab supports many mime-types across many components)
  • First action: remind ourselves of previous convo with J-Lab developer (BK, OS, HO) and go from there (if this is feasible, it would kill many birds with one stone) (not essential for the beta)

• Decide on sgaist's PR https://github.com/cylc/cylc-flow/pull/3467 (pre-commit hook and flake8)

  • agreed to merge

• Hacktoberfest labels

  • (need to update repo "topic" labels now)

• General UI status update from BK

• Back-end n-window update from DS

  • terminology? I suggest:
    • "n-edge window"
    • "n-0 window" == "active tasks"
    • ("n-max", if we have it, == max number of edges out from n-0)
    • "full cycle point window" == what it says

• (mutations integration update from OS)

  • (is a component at the moment, which isn't a long term solution - multiple line selection for example)
  • (good enough as a first cut)

• AOB:

  • JR: Altair code working solidly in Dev, then in stage and prod

Admin:

• Thank to TP for setting up all the meeting dates - should we share it around a bit now?
  • Ronnie to do it for a while.