-
Notifications
You must be signed in to change notification settings - Fork 260
chore: migrate from exit/err channels to context #900
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
Conversation
9c396a7 to
b8d0e6a
Compare
Signed-off-by: Evan Baker <rbtr@users.noreply.github.com>
neaggarwMS
left a comment
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.
![]()
neaggarwMS
left a comment
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.
🕐
6e3c0c0 to
b97f731
Compare
neaggarwMS
left a comment
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.
🕐
neaggarwMS
left a comment
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.
![]()
* chore: migrate from exit/err channels to context Signed-off-by: Evan Baker <rbtr@users.noreply.github.com> * pass context instead of storing * rename controller packages * comment init
Signed-off-by: Evan Baker rbtr@users.noreply.github.com
Reason for Change:
Migrates from a variety of exit and err channels to a runtime context. In this PR, the root context is passed directly to the child contexts (since the previous exit channels where never closed independently, only when the parent scope was exiting), but this could serve as a basis to derive cancellable or timeout child contexts in the future.
Issue Fixed:
Requirements:
Notes: