starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-03-04 04:10:03 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

Log(WARN) interferes with "--output json". #537

New Issue
Closed
opened 2025-12-29 02:19:38 +01:00 by adam · 0 comments
adam commented 2025-12-29 02:19:38 +01:00
Owner
Copy Link

Originally created by @linsomniac on GitHub (Aug 4, 2023).

Why

I'm using 10.* addresses and recently headscale changed to emit a warning about not using 100. addresses. I have some scripts which use "headscale node list --output json", that started failing because this warning was causing the output to not be JSON. I'm thinking that it would be nice if warnings were written to stderr, particularly in the cast of JSON output, so that warnings don't interfere with JSON parsing.

Errors could also go to stderr, but I'm assuming in an error the JSON output will probably be faulty anyway, so it's a slightly different use case (more of a feature request than bug report).

I'm able to fix it by passing the headscale output through an AWK range pattern: awk '/^\[/,/^\]/ { print }'

Description

Change logging output, particular of WRN level, to go to stderr.

Originally created by @linsomniac on GitHub (Aug 4, 2023). ## Why I'm using 10.* addresses and recently headscale changed to emit a warning about not using 100. addresses. I have some scripts which use "headscale node list --output json", that started failing because this warning was causing the output to not be JSON. I'm thinking that it would be nice if warnings were written to stderr, particularly in the cast of JSON output, so that warnings don't interfere with JSON parsing. Errors could also go to stderr, but I'm assuming in an error the JSON output will probably be faulty anyway, so it's a slightly different use case (more of a feature request than bug report). I'm able to fix it by passing the headscale output through an AWK range pattern: `awk '/^\[/,/^\]/ { print }'` ## Description Change logging output, particular of WRN level, to go to stderr.
adam added the enhancement label 2025-12-29 02:19:38 +01:00
adam closed this issue 2025-12-29 02:19:39 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#537
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?