datumctl on Linux: failed to get active user from keyring

[drewr]

Getting this on an Ubuntu machine:

% ./result/bin/datumctl
panic: failed to get token source: failed to get active user from keyring: failed to unlock correct collection '/org/freedesktop/secrets/aliases/default'

goroutine 1 [running]:
go.datum.net/datumctl/internal/cmd.RootCmd()
        go.datum.net/datumctl/internal/cmd/root.go:38 +0xc3a
main.main()
        go.datum.net/datumctl/main.go:15 +0x32
% uname -a
Linux dev-a28a26 6.8.0-90-generic #91-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 18 14:14:30 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
% cat /etc/issue.net
Ubuntu 24.04.3 LTS

I had claude create a patch but wanted to verify if this is a generic go-keyring issue or I'm doing something wrong.

[gianarb]

Hello! Not an expert here about keychain yet but do you mind to try to reproduce this issue with previous version?

https://github.com/datum-cloud/datumctl/releases/tag/v0.6.0

Just trying to figure out if it is a regression

[drewr]

Looks like it's a regression somewhere after v0.6.0:

% for ver in v0.6.0 v0.7.0; do git co -f $ver 2>&1 | fgrep "is now at" && ( ( nix-shell -p go --run "go build" && ./datumctl ) >/dev/null 2>&1 && echo $ver good ) || echo $ver bad; done
HEAD is now at a4c6193 Merge pull request #30 from datum-cloud/add_datum_mcp
v0.6.0 good
HEAD is now at 05c9a8d Merge pull request #48 from ShippingBytes/feat/crud-and-basic-commands
v0.7.0 bad

After a closer look, it looks like 4d9d4ec is the culprit. Nothing jumped out at me in that commit as an obvious cause though.

src/datum-cloud/datumctl[main]% git bisect start
status: waiting for both good and bad commits
src/datum-cloud/datumctl (git)-[main|bisect]-% git bisect bad
status: waiting for good commit(s), bad commit known
src/datum-cloud/datumctl (git)-[main|bisect]-% git bisect good v0.6.0
Bisecting: 37 revisions left to test after this (roughly 5 steps)
[e44927fe8a8bdeab9ba4df17a3454111bda7e842] Merge pull request #38 from datum-cloud/renovate/github.com-coreos-go-oidc-v3-3.x
src/datum-cloud/datumctl (git)-[v0.7.0~4|bisect]-% git bisect run bash -c "nix-shell -p go --run 'go build' && ./datumctl >/dev/null 2>&1"
Bisecting: 17 revisions left to test after this (roughly 4 steps)
[...]
Bisecting: 9 revisions left to test after this (roughly 3 steps)
[...]
Bisecting: 4 revisions left to test after this (roughly 2 steps)
[...]
Bisecting: 2 revisions left to test after this (roughly 1 step)
[...]
Bisecting: 0 revisions left to test after this (roughly 1 step)
[...]
4d9d4ec63bf6eaf107404a5ce3577cd8a3343c97 is the first bad commit

[drewr]

Wondering why the testing.yaml GitHub Action hadn't been failing, tried running the same command on 4d9d4ec and that fails locally:

% nix-shell -p go --run "go test -timeout 5m ./..."
fetching github input 'github:NixOS/nixpkgs/nixpkgs-unstable'
# go.datum.net/datumctl/internal/cmd/auth
internal/cmd/auth/login.go:186:26: non-constant format string in call to fmt.Errorf
?       go.datum.net/datumctl   [no test files]
?       go.datum.net/datumctl/internal/authutil [no test files]
?       go.datum.net/datumctl/internal/client   [no test files]
?       go.datum.net/datumctl/internal/cmd      [no test files]
?       go.datum.net/datumctl/internal/cmd/api-resources        [no test files]
FAIL    go.datum.net/datumctl/internal/cmd/auth [build failed]
?       go.datum.net/datumctl/internal/cmd/get  [no test files]
?       go.datum.net/datumctl/internal/cmd/get/v2       [no test files]
?       go.datum.net/datumctl/internal/cmd/mcp  [no test files]
?       go.datum.net/datumctl/internal/keyring  [no test files]
?       go.datum.net/datumctl/internal/mcp      [no test files]
ok      go.datum.net/datumctl/internal/output   0.036s
FAIL

[drewr]

Interestingly, git-bisecting the test suite, it hasn't worked (at least on this machine) for over a year.

37d8bf4

% git bisect run bash -c "nix-shell -p go --run 'go test -timeout 5m ./...' >/dev/null 2>&1"
running 'bash' '-c' 'nix-shell -p go --run '\''go test -timeout 5m ./...'\'' >/dev/null 2>&1'
Bisecting: 33 revisions left to test after this (roughly 5 steps)
[...]
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[37d8bf4ce6cae92957a1b1255b37162c53a995f2] fix: use proto marshalling, not regular marshalling (facepalm.. sorry)
running 'bash' '-c' 'nix-shell -p go --run '\''go test -timeout 5m ./...'\'' >/dev/null 2>&1'
37d8bf4ce6cae92957a1b1255b37162c53a995f2 is the first bad commit
commit 37d8bf4ce6cae92957a1b1255b37162c53a995f2
Author: Tyler Sullivan <sullivtr@gmail.com>
Date:   Mon Dec 30 11:09:48 2024 -0800

    fix: use proto marshalling, not regular marshalling (facepalm.. sorry)

 internal/output/output.go      | 25 ++++++++++++++++++-------
 internal/output/output_test.go | 23 ++++++++++++++++-------
 2 files changed, 34 insertions(+), 14 deletions(-)
bisect found first bad commit