Skip to content

Conversation

@npentrel
Copy link
Collaborator

No description provided.

@npentrel npentrel requested a review from aldenh-viam October 23, 2025 12:14
@netlify
Copy link

netlify bot commented Oct 23, 2025

Deploy Preview for viam-docs ready!

Name Link
🔨 Latest commit ed99bf4
🔍 Latest deploy log https://app.netlify.com/projects/viam-docs/deploys/68fa1e805705370008b3e7c4
😎 Deploy Preview https://deploy-preview-4722--viam-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 36 (🔴 down 16 from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 92 (no change from production)
PWA: 70 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@viambot viambot added the safe to build This pull request is marked safe to build from a trusted zone label Oct 23, 2025
Copy link

@aldenh-viam aldenh-viam left a comment

Choose a reason for hiding this comment

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

I think the main thing here is to just verify your internet connection is stable and usable (outside of Viam software, e.g. confirm you can browse the web, ping, etc.). The socks-forwarder bits will not be relevant to the majority of users.

**Description**:
This error occurs due to congestion while different machine processes compete for bandwidth.

Choose a reason for hiding this comment

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

This is only my hypothesis that error appears when your internet connection becomes flaky (and socks-forwarder, if you choose to connect through it, by design will be), but it's not 100% verified.

Copy link
Collaborator Author

@npentrel npentrel Oct 23, 2025

Choose a reason for hiding this comment

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

OK, what do you suggest we should tell the user about this then?

Should I just close the PR and we leave it out or would you like to confirm your hypothesis?

Choose a reason for hiding this comment

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

Best I have for now is just to verify your internet connection is stable and if it's not, the error should go away once it is. Up to you if you feel that's sufficient, or just leave it out for now.

Copy link
Collaborator Author

@npentrel npentrel Oct 24, 2025

Choose a reason for hiding this comment

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

ok I'll leave it out for now since we can't describe the error

This error is usually harmless and may resolve on its own.
To get more logs, you can enable forwarding system logs for SOCKS, by adding the following to your [`viam-agent` system configuration](/manage/reference/viam-agent/#system-configuration):

Choose a reason for hiding this comment

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

Not everyone will be running socks-forwarder.

**Solution:**
This error is usually harmless and may resolve on its own.

Choose a reason for hiding this comment

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

Going with the hypothesis, yes this appears to resolve on its own once the internet connection returns to a stable/usable state.

@npentrel npentrel closed this Oct 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

safe to build This pull request is marked safe to build from a trusted zone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants