Skip to content
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

Fix workgroup AddContext bug #4783

Merged
merged 1 commit into from
Oct 17, 2022
Merged

Fix workgroup AddContext bug #4783

merged 1 commit into from
Oct 17, 2022

Conversation

chattarajoy
Copy link
Contributor

In case functions are added to workgroup using AddContext method, the AddContext method doesn't exit if the corresponding function exits. This change makes sure the Run flow exits in case the function running has exited.

@chattarajoy chattarajoy requested a review from a team as a code owner October 10, 2022 11:28
@chattarajoy chattarajoy requested review from tsaarni and sunjayBhatia and removed request for a team October 10, 2022 11:28
Signed-off-by: Joy Lal Chattaraj <8450903+chattarajoy@users.noreply.github.com>
@codecov
Copy link

codecov bot commented Oct 10, 2022

Codecov Report

Merging #4783 (e4f85a6) into main (aa741b0) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #4783   +/-   ##
=======================================
  Coverage   76.04%   76.04%           
=======================================
  Files         140      140           
  Lines       16859    16861    +2     
=======================================
+ Hits        12820    12822    +2     
  Misses       3787     3787           
  Partials      252      252           
Impacted Files Coverage Δ
internal/workgroup/group.go 100.00% <100.00%> (ø)

@skriss
Copy link
Member

skriss commented Oct 10, 2022

Thanks for the PR @chattarajoy, however what I would really like to do is drop the workgroup package entirely since it's only being used by test code at this point and I don't think we need our own custom goroutine manager anymore -- see #4206. Would you be interested in taking that work on?

Copy link
Member

@sunjayBhatia sunjayBhatia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep agreed, we should focus on possibly removing the package since it's only used in tests

@chattarajoy
Copy link
Contributor Author

Hi @skriss , since I was using this module in my own project (copied the code, not importing using go mod) I found this bug and fixed it in my project as well as thought of raising a fix here. I am sorry I won't be able to pick up the deletion of this model and remove its usage.

@skriss
Copy link
Member

skriss commented Oct 17, 2022

Hi @skriss , since I was using this module in my own project (copied the code, not importing using go mod) I found this bug and fixed it in my project as well as thought of raising a fix here. I am sorry I won't be able to pick up the deletion of this model and remove its usage.

@chattarajoy fair enough - I think we can merge this as-is and still look to do #4206 subsequently.

@skriss skriss added the release-note/none-required Marks a PR as not requiring a release note. Should only be used for very small changes. label Oct 17, 2022
@skriss skriss merged commit caefe66 into projectcontour:main Oct 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note/none-required Marks a PR as not requiring a release note. Should only be used for very small changes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants