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 value of the argument event will be a value in the above example. There is also caching and the function my_event is not run when the argument's value is set (as it was already run for the condition check). Futhermore, there is a check_cond that can be customized in order to decrease the amount of function call in case it is expensive (ie. if the event is inspected from a database).
Logging improvements
The logging works well and it has been moderately documented. However, the documentation could be improved and setting up the logging could be made more natural.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi!
I think Rocketry version 2.5 will be again a significant update in terms of what one can do with Rocketry.
Here is the feature set I aim for the release:
Multi-launch (implemented)
The multi-launch system enables running the same task multiple times. The runs are tracked in run stacks. Here is an example:
This task can run four times parallel. Multilaunch can also be set on session config to apply to all tasks by default.
The
rocketry.conds.running
was also refactored in order to be useful with multi-launch. For example, this will start four parallel runs:And this will terminate if there are over 4 runs at the same time:
Event system (close to be done)
The event system enables an easy way to trigger tasks based on some datetimes.
For example, an event notification example:
The above will run only when it has not run after the event happened (the datetime in the event).
This also supports event carried state transfer:
The value of the argument
event
will bea value
in the above example. There is also caching and the functionmy_event
is not run when the argument's value is set (as it was already run for the condition check). Futhermore, there is acheck_cond
that can be customized in order to decrease the amount of function call in case it is expensive (ie. if the event is inspected from a database).Logging improvements
The logging works well and it has been moderately documented. However, the documentation could be improved and setting up the logging could be made more natural.
Beta Was this translation helpful? Give feedback.
All reactions