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

Port forward multiple ports #1250

Merged
merged 1 commit into from Nov 8, 2018

Conversation

dgageot
Copy link
Contributor

@dgageot dgageot commented Nov 7, 2018

Fixes #1249

Signed-off-by: David Gageot david@gageot.net

@r2d4
Copy link
Contributor

r2d4 commented Nov 7, 2018

I think we still want to log the error? Maybe wrap this in a sync Group and return an error at the end if any of them errored (but still port forward?)

Signed-off-by: David Gageot <david@gageot.net>
@dgageot
Copy link
Contributor Author

dgageot commented Nov 8, 2018

@r2d4 Good point! Should be ok now

@codecov-io
Copy link

codecov-io commented Nov 8, 2018

Codecov Report

Merging #1250 into master will increase coverage by 0.05%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1250      +/-   ##
==========================================
+ Coverage   42.18%   42.24%   +0.05%     
==========================================
  Files          96       96              
  Lines        4238     4242       +4     
==========================================
+ Hits         1788     1792       +4     
  Misses       2276     2276              
  Partials      174      174
Impacted Files Coverage Δ
pkg/skaffold/kubernetes/port_forward.go 42.85% <100%> (+2.62%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0badfef...d0452a8. Read the comment docs.

@r2d4
Copy link
Contributor

r2d4 commented Nov 8, 2018

So if we port forward some but then fail and return an error, I’m not sure we’ll clean up the rest properly.

I guess this was also an issue before when the first port forward in a pod succeeded and the second one failed.

Let’s merge for now and keep an eye out for any forwards that don’t get cleaned up properly

@dgageot dgageot merged commit a8db96e into GoogleContainerTools:master Nov 8, 2018
@dgageot dgageot deleted the fix-port-forwarding branch December 28, 2018 07:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants