- Notifications
You must be signed in to change notification settings - Fork907
fix: fix broken troubleshooting link#16469
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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.
⚡ damn you're quick!
I think this is a more widespread issue, and probably something we should add a linter for somehow.
Looks like the same issue at
Line 256 in6117f46
| sw.Log(time.Now(),codersdk.LogLevelWarn,troubleshootingMessage(agent,fmt.Sprintf("%s/templates#agent-connection-issues",opts.DocsURL))) |
The linter idea is intriguing, I will think about it!
I believe you need to refresh your fork as it seems to befixed already. |
5fbedc7 intomainUh oh!
There was an error while loading.Please reload this page.
/cherry-pick release/2.19 |
Fixes:#16468
The troubleshooting link was not updated after moving around docs.