Files
logos-logoscore-cli/flake.lock
Dario Gabriel LipicarandClaude Opus 5 0e2c9acbce chore(deps): relock logos-protocol to 0.8, which is what makes saveInboundToken exist
WHAT MOVED. logos-protocol 2e3344ac (0.5.0) -> 42460e5b (0.8.0). One node,
three lines. The input is branch-tracking (no rev in "original"), so a plain
"nix flake lock --update-input logos-protocol" moved it unaided.

WHY IT HAD TO. The parent commit calls TokenManager::saveInboundToken, which
arrived with the INBOUND/OUTBOUND direction split in logos-protocol#72 --
merged as 42460e5b. At the old pin the branch did not compile:

  src/daemon/daemon.cpp:634:30: error: 'class TokenManager' has no member
  named 'saveInboundToken'

That is not a claim about the diff, it is a measured negative control: the
failing build is this exact tree with --override-input logos-protocol
github:logos-co/logos-protocol/2e3344ac, and the pin is the only thing
between the two runs. Nothing else in the repo moved.

Everything in the process image follows this one input -- logos-cpp-sdk,
logos-plugin-qt and logos-liblogos each declare
inputs.logos-protocol.follows = "logos-protocol" -- so the runtime closure of
the built package carries exactly ONE protocol and ONE qt-host:

  logos-protocol-lib-0.8.0        logos-qt-host-0.1.0
  logos-protocol-headers-0.8.0    logos-liblogos-0.1.0

(nix-store -qR on the store path below. The lock as a whole names 17 protocol
revisions across 470 nodes; all the others sit behind doctest and module
inputs that never reach this binary.)

CHECKS -- every check this flake exposes, built individually with
--print-out-paths on x86_64-linux, plus the package CI builds first:

  packages.default      /nix/store/5mqb5r05ybv2sxwz9m21ml64z83ria3y-logos-logoscore-cli
  tests                 /nix/store/5ggcakpbpqd1p58p7r2mfhwq6f7932ci-logos-logoscore-cli-tests
  tests-logoscore       /nix/store/8vff4cqygdlsmcp9dix02yj3wfsnfs97-logos-logoscore-cli-tests-logoscore
  tests-logosctl        /nix/store/ncnnaqwq1nx5m265s8if0v345zw7xnpw-logos-logoscore-cli-tests-logosctl
  symbol-gate           /nix/store/ywz3nzsphqg0939hxvvhrm9kdxcxiqdi-logos-logoscore-cli-symbol-gate
  symbol-gate-negative  /nix/store/xrcf9da8samxxgfv3x493pbnphv8ylj5-logos-logoscore-cli-symbol-gate-negative

tests-logosctl ran 249 + 30 + 25 gtest cases; tests-logoscore ran 24 across
five suites, including the live-daemon ones (ErrorPathTest, LoadedModuleTest,
SocketLifecycleTest, PersistencePathTest). They prove no regression. They do
not discriminate the fix: the old outbound filing still left the slow path
working, which is the whole reason the parent commit exists.

Not built: aarch64-linux and the Darwin systems -- x86_64 Linux builder only.
CI covers both arches.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-24 12:36:20 -03:00

27 MiB

The file is too large to be shown. View Raw