-
Notifications
You must be signed in to change notification settings - Fork 90
Expose lifecycle_node (#327) (with test) #482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: rolling
Are you sure you want to change the base?
Expose lifecycle_node (#327) (with test) #482
Conversation
Signed-off-by: Kenji Miyake <[email protected]>
Signed-off-by: SuperJappie08 <[email protected]>
|
@fujitatomoya, this is the updated version of #327, which you closed recently. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think this is lgtm.
@christophebedard @ahcorde i would like to have 2nd review on this. can you take a look when you have time?
|
Pulls: #482 |
|
@fujitatomoya, I think the CI failed on cloning the repos. |
|
I'll give this a quick review and take care of CI later today. |
|
Just to note this here: #236 mentions supporting event handlers (i.e., the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! We just need to wait for the CI jobs I retriggered to finish; CI queues are a bit full right now.
Original committer: @esteve
Original author: @kenji-miyake
Original reviewer: @ivanpauno
Description
Added the requested tests to #327, also exposed
autostart.Fixes #236
Is this user-facing behavior change?
Did you use Generative AI?
No
Additional Information
Rebased original pull request on rolling.