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
Going forward, we should use the following definitions:
Component: A software unit managed by launch manager that has dependencies and active/inactive states
Active: A component state that indicates the component has been activated, all configured readiness conditions were met, and no failure has occurred since those conditions were satisfied.
Process: A specialized component representing a single POSIX process
Run target: A specialized component that represents a collection of components that are managed together and can be activated or deactivated as a group.
Transition: An operation that activates a specified run target. As part of this operation, the required component state changes are evaluated, and the necessary components are activated or deactivated accordingly.
Some legacy terms that should be updated if encountered:
State/Process group state: This most closely matches with run targets, but could not depend on other run targets/states
Process group: A collection of states. Previously, more than one could be active at a time. At present, there is only one process group (known as "MainPG" or machine_process_group)
Acceptance Criteria (DoD)
Graph class is renamed
ProcessGroupManager directory & class renamed
Methods & attributes with names that are no longer accurate in former ProcessGroupManager directory updated
What
After #392, some existing names have become outdated.
handleNonTransitionExecutionactually finalizes a failed transitionabort()is a really bad name for a class member functionGoing forward, we should use the following definitions:
Some legacy terms that should be updated if encountered:
machine_process_group)Acceptance Criteria (DoD)
How
No response