GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||
GeezerVison is showing github.com — fix(cli): exit port-forward when workspace agent becomes unreachable by zertosh · Pull Request #24011 · coder/coder ConversationFixes #10626 Previously This adds a watchdog that calls
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
|
There was an error while loading. Please reload this page.
|
All contributors have signed the CLA ✍️ ✅ |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I have read the CLA Document and I hereby sign the CLA |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
recheck |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Looks good for the most part, @zertosh do you have cycles to address the changes? I can take over the branch push it through to merge if you're busy as well.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| wg.Add(1) | ||
| go func() { |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
It'd be good to refactor this out into its own method so that we can write some unit tests for it.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| case <-ticker.C: | ||
| } | ||
| pingCtx, pingCancel := context.WithTimeout(ctx, timeout) | ||
| reachable := conn.AwaitReachable(pingCtx) |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I think we may want to use Ping() here instead of
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@codex review |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Codex Review: Didn't find any major issues. 👍 ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Please feel free to take this 😄 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
All of our networking commands are intended to survive network connectivity loss, since the tailnet will seamlessly restore connectivity. If we make a change like this, it will mean that slept computers could terminate port forward commands even if they were still functional. Are you seeing the connectivity break after the network is restored? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Yeah. And it's not clear from port-forward that that is going on. The only way to know is looking for CLOSE_WAIT connections |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@zertosh is it enough if we log whenever we lose connectivity? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
coder port-forward hangs upon workspace restart, ssh -L exits cleanly
There was an error while loading. Please reload this page.