Back to Signal Feed
CodeTracked since May 19, 2026

Add non-Linux `CheckLinger` stub to unblock cc-connect builds

The PR adds `daemon/linger_stub.go` with a `//go:build !linux` guard implementing `CheckLinger()` for non-Linux platforms, resolving a cross-platform compile failure where `cmd/cc-connect/daemon.go` called `daemon.CheckLinger` but only the Linux/systemd implementation existed.

CheckLingerdaemoncmd/cc-connect/daemon.godaemon/linger_stub.go

What Happened

  • The PR adds `daemon/linger_stub.go` with a `//go:build !linux` guard implementing `CheckLinger()` for non-Linux platforms, resolving a cross-platform compile failure where `cmd/cc-connect/daemon.go` called `daemon.CheckLinger` but only the Linux/systemd implementation existed.
  • The PR adds `daemon/linger_stub.go` with a `//go:build !linux` guard implementing `CheckLinger()` for non-Linux platforms, resolving a cross-platform compile failure where `cmd/cc-connect/daemon.go` called `daemon.CheckLinger` but only the Linux/systemd implementation existed.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduced a non-Linux `CheckLinger` build-stub in `daemon/linger_stub.go` so the new `daemon.CheckLinger` call in daemon startup code resolves on all platforms, not just Linux.

Why Track This

Why It Matters

Builds of cc-connect on macOS and Windows no longer fail at compile time, so maintainers can release and test cross-platform binaries without platform-specific breakage. The change uses a `!linux`-scoped stub (`linger_stub.go`) that returns a default linger value and user string, preventing the `undefined: daemon.CheckLinger` symbol error from the Linux-only systemd implementation. Watch for any non-Linux code paths that rely on actual systemd linger behavior, since the stub is a compatibility no-op and may mask missing platform-specific semantics.

Impact

Builds of cc-connect on macOS and Windows no longer fail at compile time, so maintainers can release and test cross-platform binaries without platform-specific breakage. The change uses a `!linux`-scoped stub (`linger_stub.go`) that returns a default linger value and user string, preventing the `undefined: daemon.CheckLinger` symbol error from the Linux-only systemd implementation. Watch for any non-Linux code paths that rely on actual systemd linger behavior, since the stub is a compatibility no-op and may mask missing platform-specific semantics.

What To Watch Next

  • Watch whether CheckLinger becomes a repeated pattern.
  • Track follow-up changes around Code Repository Intelligence.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: non_linux_code_paths_assuming_systemd_linger, user_env_dependency_in_stub_default.
Open Topic TimelineOpen Technical EventOpen Original Sourcenon_linux_code_paths_assuming_systemd_linger / user_env_dependency_in_stub_default / ci_only_build_checks_insufficient_for_runtime_behavior

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

chenhg5/cc-connect PR #1052: fix(daemon): add CheckLinger stub for non-Linux platforms

Fixes `undefined: daemon.CheckLinger` on macOS/Windows by adding a no-op `CheckLinger` that returns a default enabled flag and user from `USER` (or `unknown`).