Comments (3)
What is the problem with how it is currently?
from cylc-flow.
There are four related things:
- Outputs - sometimes used to mean trigger:message pairs, but sometimes used to refer to triggers or messages.
- Triggers - the things you can use in the graph or satisfy with
cylc set
. These are often referred to as "labels". - Messages - the strings you can send through
cylc message
. - Events - kinda like messages that come from within the system like
submission failed
orretry
, but confusingly, alsostarted
,succeeded
andfailed
which are also task outputs.
Whilst working on #5658 it was discovered that triggers/messages were sometimes mislabelled as their opposite and outputs was sometimes used ambiguously to refer to one or the other. No functional problems, it all works fine, just confusing when you need to work on this code.
Cheat Sheet:
- DB - messages
- Data Store - messages & triggers
TaskOutputs
- messages & triggerscylc set
- triggerscylc message
- messagescylc trigger
- trick questionScheduler.message_queue
- messages & eventsTaskEventsManager.process_message
- messages & events
from cylc-flow.
I've been diving into this code over the past few days whilst working on the optional outputs and struggling with this a bit (completion expressions need triggers, most of the rest of the code needs messages, trying to avoid storing surplus maps whilst keeping it efficient). I'm coming to the conclusion that messages should be mapped onto triggers in the task events code, from there on it would be simpler to stick to triggers.
Triggers are the more fundamental and user facing concept. They are used in the graph, the completion expression, cylc show
, universal ID, etc. Messages can be used to provide supplementary detail and may be patterns, great for sending supplementary information back to the scheduler (not that anyone does sadly, I've checked!), but not so good for internal interfaces where it's not clear whether we're dealing with raw messages or matching message patterns. Note raw messages may not be unique and the mapping between raw messages and patterns may be broken by reload/restart.
from cylc-flow.
Related Issues (20)
- job script `mkdir` tweak HOT 2
- internals: task "output" vs "message" HOT 1
- remote: zero installation remote client HOT 1
- Contact file getting removed when host self-id is hardwired to localhost HOT 5
- Cylc 8 not properly matching hostnames given in global.cylc HOT 4
- cylc message and : inconsistencies HOT 4
- runahead update on manual trigger
- Cycling over a list of strings HOT 2
- `cylc config -i` traceback HOT 1
- Scheduler command arg validation HOT 5
- better `cylc set --output` logging
- The `is_queued` task status attribute != "is queued"
- resolvers: handle the UISTask field or come up with a better approach
- clock-expire: prevent active tasks from being clock-expired HOT 9
- lint: use entry points to load rulesets HOT 1
- workflow_state xtrigger and CLI command do not work across users HOT 3
- Setting final outputs on active tasks: should kill first HOT 4
- store: add queue information
- tutorial: sleep if not doing anything HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cylc-flow.