Michael Lopez 3746ad20db cli: distinguish no match from ambiguous match when resolving users ...

resolveSingleUser reported every non-single result as "multiple users
match query", including zero matches. An explicit --identifier 0 was
sent to the API, which treats id=0 as no filter, so it listed every
user and failed as ambiguous. Return a not-found error for zero matches,
list the matching users when several match, and reject a non-positive
identifier before calling the API.

2026-09-25 20:00:15 +02:00

..

dev

docs: add changelog and refresh the API reference for the v1 API

2026-06-19 15:21:00 +02:00

gen-openapi

hscontrol, cli: serve the v2 API on the local socket and add the oauth-clients command

2026-06-26 09:18:06 +02:00

headscale

cli: distinguish no match from ambiguous match when resolving users

2026-09-25 20:00:15 +02:00

hi

hi: compare the stream error with errors.Is

2026-08-25 21:59:00 +02:00

mapresponses

all: fix golangci-lint issues (#3064)

2026-02-06 21:45:32 +01:00

vendorhash

all: apply godoc [Name] link conventions across comments

2026-05-19 09:55:22 +02:00