Skip to content

[client] avoid parsing NB_NETSTACK_SKIP_PROXY if empty #4145

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

Merged
merged 1 commit into from
Jul 13, 2025

Conversation

iisteev
Copy link
Contributor

@iisteev iisteev commented Jul 13, 2025

This avoids to have in the logs:

ERRO client/iface/netstack/tun.go:46: failed to parse NB_NETSTACK_SKIP_PROXY: strconv.ParseBool: parsing "": invalid syntax

Describe your changes

When you run netbird client in rootless mode and in the absence of the var NB_NETSTACK_SKIP_PROXY, you get a parsing error in the logs. People would need to set the variable explicitly to avoid the parsing error in the logs which I don't think it was left like this on purpose?

Issue ticket number and link

Stack

Checklist

  • Is it a bug fix
  • Is a typo/documentation fix
  • Is a feature enhancement
  • It is a refactor
  • Created tests that fail without the change (if possible)
  • Extended the README / documentation, if necessary

By submitting this pull request, you confirm that you have read and agree to the terms of the Contributor License Agreement.

@CLAassistant
Copy link

CLAassistant commented Jul 13, 2025

CLA assistant check
All committers have signed the CLA.

This avoids to have in the logs:
```
 ERRO client/iface/netstack/tun.go:46: failed to parse NB_NETSTACK_SKIP_PROXY: strconv.ParseBool: parsing "": invalid syntax
```

Signed-off-by: iisteev <[email protected]>
@iisteev iisteev force-pushed the parse-bool-skip-proxy branch from 302fb65 to 3a534bf Compare July 13, 2025 10:35
Copy link

@lixmal lixmal merged commit e49bcc3 into netbirdio:main Jul 13, 2025
31 of 32 checks passed
@lixmal
Copy link
Collaborator

lixmal commented Jul 13, 2025

Thanks!

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.

3 participants