agent-deck-1.16.35
checks.aarch64-linux.pkgs-agent-deck
· build #9696
· raw
1elastic-arm-9a50e053: building 53kqvc2brsp7aa8vbdpf2v1ppai5kmcl-agent-deck-1.16.35.drv2Using versionCheckHook
unpackPhase
3unpacking source archive /nix/store/k1s5z7sm1gl0gavln4pl53w4fi2k0yvk-source4source root is sourcebuildPhase
5Building subPackage ./cmd/agent-deck6buildPhase completed in 2 minutes 2 secondscheckPhase
72026/11/01 04:57:24 WARN codex_hook_status_unreadable instance=partial path=/tmp/nix-w5UFJp/TestWriteCodexHookStatus_PartialPriorFailsClosed3411913085/001/.local/share/agent-deck/hooks/partial.json bytes=108Codex notify hook installed successfully.9Config: /tmp/nix-w5UFJp/TestCodexHooksInstallUninstall794237759/001/.codex/config.toml10Codex notify hook removed successfully.11Codex notify hook upgraded successfully.12Config: /tmp/nix-w5UFJp/TestCodexHooksInstall_UpgradesLegacyTableWithoutMarkers4047694560/001/.codex/config.toml13Codex notify hook upgraded successfully.14Config: /tmp/nix-w5UFJp/TestCodexHooksInstall_UpgradesLegacyMarkerBlock2120314613/001/.codex/config.toml15Codex notify hook upgraded successfully.16Config: /tmp/nix-w5UFJp/TestCodexHooksInstall_ReplacesBlockInPlaceAndKeepsMode1062080780/001/.codex/config.toml17Codex notify hook removed successfully.18Error reading codex config: open /tmp/nix-w5UFJp/TestCodexHooksInstall_UnreadableConfigIsNotOverwritten2709835832/001/.codex/config.toml: permission denied19Error writing codex config: open /tmp/nix-w5UFJp/TestCodexHooksInstall_ReadOnlyConfigIsNotReplaced1425284504/001/.codex/config.toml: permission denied20Codex notify hook upgraded successfully.21Config: /tmp/nix-w5UFJp/TestCodexHooksUninstall_KeepsLineEndingscrlf2529445073/001/.codex/config.toml22Codex notify hook removed successfully.23Codex notify hook upgraded successfully.24Config: /tmp/nix-w5UFJp/TestCodexHooksUninstall_KeepsLineEndingsno_final_newline3302470743/001/.codex/config.toml25Codex notify hook removed successfully.26Error: the agent-deck notify block in /tmp/nix-w5UFJp/TestCodexHooksInstall_BlockBelowTableIsRefusedprofiles.work3906512448/001/.codex/config.toml sits below a [table], where notify belongs to that table.27Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'.28Error: the agent-deck notify block in /tmp/nix-w5UFJp/TestCodexHooksInstall_BlockBelowTableIsRefusedprofiles.qa,wes3253265277/001/.codex/config.toml sits below a [table], where notify belongs to that table.29Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'.30Error: the agent-deck notify block in /tmp/nix-w5UFJp/TestCodexHooksInstall_BlockBelowTableIsRefused_hooks_._a=b1397086887/001/.codex/config.toml sits below a [table], where notify belongs to that table.31Move the block above every table, or remove it and rerun 'agent-deck codex-hooks install'.32agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-w5UFJp/TestEventProfileUsesStorageFallbackForMissingInference3419518672/001/.claude-ghost" would select profile "ghost", which does not exist; falling back to profile "work" instead of creating it. Known profiles: none yet. Pass -p/--profile or set AGENTDECK_PROFILE explicitly to pick a different profile, run `agent-deck profile create ghost` if you intend to create it, or unset CLAUDE_CONFIG_DIR to use the default profile.33Gemini hooks installed successfully.34Config: /tmp/nix-w5UFJp/TestGeminiHooksInstallUninstall822836806/001/.gemini/settings.json35Gemini hooks removed successfully.36✓ Reordered group 'Beta': position 1 → 037✓ Reordered group 'Beta': position 1 → 238✓ Reordered group 'Gamma': position 2 → 039✓ Reordered group 'Alpha': position 0 → 040✓ Reordered group 'Gamma': position 2 → 241✓ Reordered group 'Alpha': position 0 → 242agentpaths: resolved agent-deck path under the real home (/tmp/nix-NmkFGw/.config/agent-deck); this touches REAL user data. If this is a test, it is NOT sandboxed; call testutil.IsolateHome() in TestMain and run with a temp HOME+XDG (2026-06-04 data-loss incident, S4).43WARNING: no notify-daemon running; completions are not being recorded, so an empty drain or 0 done does not mean nothing finished. Start one with `agent-deck notify-daemon` (`agent-deck conductor setup` installs it as a service).44WARNING: no notify-daemon running; completions are not being recorded, so an empty drain or 0 done does not mean nothing finished. Start one with `agent-deck notify-daemon` (`agent-deck conductor setup` installs it as a service).45agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-w5UFJp/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG3739938034/001/.claude-ghost" would select profile "ghost", which does not exist; falling back to profile "work" instead of creating it. Known profiles: none yet. Pass -p/--profile or set AGENTDECK_PROFILE explicitly to pick a different profile, run `agent-deck profile create ghost` if you intend to create it, or unset CLAUDE_CONFIG_DIR to use the default profile.46agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-w5UFJp/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG3739938034/001/.claude-ghost" would select profile "ghost", which does not exist; falling back to profile "work" instead of creating it. Known profiles: work. Pass -p/--profile or set AGENTDECK_PROFILE explicitly to pick a different profile, run `agent-deck profile create ghost` if you intend to create it, or unset CLAUDE_CONFIG_DIR to use the default profile.47agent-deck: CLAUDE_CONFIG_DIR="/tmp/nix-w5UFJp/TestIssue2740_WatcherCommandsUseTheResolvedProfileCLAUDE_CONFIG3739938034/001/.claude-ghost" would select profile "ghost", which does not exist; falling back to profile "work" instead of creating it. Known profiles: work. Pass -p/--profile or set AGENTDECK_PROFILE explicitly to pick a different profile, run `agent-deck profile create ghost` if you intend to create it, or unset CLAUDE_CONFIG_DIR to use the default profile.48--- FAIL: TestIssue2921ClaudeLikeFakeIsGoneWhenItsCleanupReturns (0.00s)49 issue2921_guarded_fake_cleanup_test.go:33: fixture did not start50notify-daemon: binary upgraded (running 1.16.35, on-disk 1.16.35-next); recycling51notify-daemon: binary upgraded (running 1.16.35, on-disk 1.16.35-next); recycling52Waiting for the sandbox provider to clean up (press Ctrl-C again to quit now)...53Waiting for the sandbox provider to clean up (press Ctrl-C again to quit now)...54Waiting for the sandbox provider to clean up (press Ctrl-C again to quit now)...55remote-agent: probe: storage gone56remote-agent: binary upgraded (running v1.16.35); exiting so the controller reconnects57remote-agent: probe produced no listing (Error: database is locked)58remote-agent: probe produced no listing ([])59remote-agent: no input for 300ms, exiting60remote-agent: the host now selects another profile; exiting so the controller reconnects6162═══ Remote: offline (a@offline) ═══63 – Skipped: agent-deck not found on remote or host unreachable6465═══ Remote: offline (a@offline) ═══66 ✗ Failed: stub: no platform67A remote sweep is already running on this controller (pid 13229, started 5:02AM); waiting for it...6869═══ Remote: lab (a@lab) ═══70 – Skipped: sweep already in progress, remote lab is being updated by 132297172═══ Remote: other (a@other) ═══73 ✓ Up to date (v1.16.0)7475═══ Remote: lab (a@lab) ═══76 ✓ Up to date (v1.16.0)7778═══ Remote: other (a@other) ═══79 ✓ Up to date (v1.16.0)80--- FAIL: TestRemoteFollowEndsOnStdinClose (16.83s)81 --- FAIL: TestRemoteFollowEndsOnStdinClose/events (15.44s)82 remote_read_cli_test.go:207: follow kept running after stdin closed; stderr: 83Warning: the session restarted, but its new tmux name could not be recorded: record restart outcome for tmux session "agentdeck_cli-restart-target_735e3867": record restart outcome for "2e2cd57c-1793509379": instance row not found84 The session is running; agent-deck may show it as errored until the name is saved.85Handed switch-account of self to a detached agent-deck (pid 999): it targets the session this command runs in, whose restart ends this pane. Output: /tmp/x.log. Check the result with `agent-deck session show bf319ead-1793509427` once the session is back.86Warning: output freshness timeout (300ms) — response may be stale87Warning: output freshness timeout (300ms) — response may be stale88Warning: output freshness timeout (300ms) — response may be stale89Launch agent re-registration deferred: a remote sweep (pid 12345, started 05:04:49) is still running90Imported 2 channel(s)91 C0AABSF5GKD -> si-bugs/watcher.toml92 C1BBCDF6HLE -> feat-req/watcher.toml9394Note: Set the ntfy topic in each watcher.toml (all Slack channels95share one ntfy topic from the Cloudflare Worker).96Clients written to: /tmp/nix-w5UFJp/TestImportChannels_EndToEnd1616638844/002/clients.json97Imported 1 channel(s)98 C0AABSF5GKD -> si-bugs/watcher.toml99100Note: Set the ntfy topic in each watcher.toml (all Slack channels101share one ntfy topic from the Cloudflare Worker).102Clients written to: /tmp/nix-w5UFJp/TestImportChannels_Idempotent98349953/002/clients.json103Imported 1 channel(s)104 C0AABSF5GKD -> si-bugs/watcher.toml105106Note: Set the ntfy topic in each watcher.toml (all Slack channels107share one ntfy topic from the Cloudflare Worker).108Clients written to: /tmp/nix-w5UFJp/TestImportChannels_Idempotent98349953/002/clients.json109Imported 0 channel(s)110Clients written to: /tmp/nix-w5UFJp/TestImportChannels_EmptyChannels2942671441/002/clients.json111Installed skill: watcher-creator -> /tmp/nix-w5UFJp/TestWatcherInstallSkill4085974469/001/xdg-config/agent-deck/skills/pool/watcher-creator112Installed skill: watcher-creator -> /tmp/nix-w5UFJp/TestWatcherInstallSkill_DirMode2196686958/001/xdg-config/agent-deck/skills/pool/watcher-creator113Created watcher: create-topic-ntfy (type: ntfy)114Warning: ntfy watcher: this topic is easy to guess and the public server https://ntfy.sh has no access token set, so anyone who guesses the topic can read its events and inject fake ones. Fix one of: use a random topic (agent-deck watcher create ntfy --name <name> --random-topic); set an access token ($NTFY_TOKEN or --token-file <path> with chmod 600, or token = "..." under [source] in watcher.toml); or use your own ntfy server (--server https://ntfy.example.com, or server = "..." under [source]).115Created watcher: create-topic-slack (type: slack)116Warning: slack watcher: this topic is easy to guess and the public server https://ntfy.sh has no access token set, so anyone who guesses the topic can read its events and inject fake ones. Fix one of: use a random topic (agent-deck watcher create slack --name <name> --random-topic); set an access token ($NTFY_TOKEN or --token-file <path> with chmod 600, or token = "..." under [source] in watcher.toml); or use your own ntfy server (--server https://ntfy.example.com, or server = "..." under [source]).117Usage: agent-deck watcher <command> [args]118119Watchers listen for inbound events (webhooks, push notifications,120GitHub events, Slack messages) and route them to conductor sessions121so your running agents can act on them automatically.122123Commands:124 create <type> --name <name> Create a new watcher (types: webhook, ntfy, github, slack)125 start <name> Mark a watcher as running (run by the profile's watcher engine)126 stop <name> Mark a watcher as stopped127 reload [--json] Apply watcher and clients.json changes to the running engine now128 list [--json] List all watchers with status and event rate129 status <name> [--json] Show watcher info, recent events and events not delivered yet130 test <name> Route a synthetic event to verify routing config131 routes [--json] Show all routing rules from clients.json132 import <path> Migrate bash issue-watcher channels.json to Go watcher config133 install-skill <skill-name> Install a skill to ~/config/agent-deck/skills/pool (e.g. watcher-creator)134135Examples (one per adapter type):136137 # Generic HTTP webhook on 127.0.0.1:9000. Requests must be signed with a138 # secret: generated and stored in its watcher.toml unless given by139 # $WEBHOOK_SECRET or --secret-file (chmod 600):140 agent-deck watcher create webhook --name my-webhook --port 9000141142 # GitHub repository webhook with HMAC-SHA256 verification143 # Secret comes from the environment or a chmod-600 file, never a CLI arg:144 GITHUB_WEBHOOK_SECRET=... agent-deck watcher create github --name gh-alerts145 agent-deck watcher create github --name gh-alerts --secret-file ~/.gh-webhook-secret146147 # ntfy push-notification topic. On the public https://ntfy.sh anyone who148 # knows the topic can read and post to it, so use a random topic:149 agent-deck watcher create ntfy --name phone-alerts --random-topic150 # or an access-protected topic on your own ntfy server (token from the151 # environment or a chmod-600 file, never a CLI arg):152 NTFY_TOKEN=... agent-deck watcher create ntfy --name phone-alerts \153 --server https://ntfy.example.com --topic phone-alerts154155 # Slack-bridged via ntfy topic (see skill for Cloudflare Worker setup)156 agent-deck watcher create slack --name team-slack --random-topic157158After creating, activate and inspect:159 agent-deck watcher start <name>160 agent-deck watcher list # see health + events/hour161 agent-deck watcher test <name> # fire a synthetic event162163Routing: edit ~/data/agent-deck/watcher/clients.json to pick which164conductor / group receives events. See `agent-deck watcher routes` for165the currently-loaded rules across all watchers.166167Conversational setup (recommended for first-time use):168 agent-deck watcher install-skill watcher-creator169 # Then inside Claude Code in an agent-deck session, ask:170 # "Use the watcher-creator skill to set up a GitHub watcher"171172Full reference: https://github.com/asheshgoplani/agent-deck#watchers173No routing rules configured.174No watchers configured.175Run 'agent-deck watcher create <type> --name <name>' to create one.176Installed skill: watcher-creator -> /tmp/nix-w5UFJp/TestXDGTask6_WatcherInstallSkillUsesConfiguredPoolPath3082283244/001/xdg-config/agent-deck/skills/pool/watcher-creator177FAIL178FAIL github.com/asheshgoplani/agent-deck/cmd/agent-deck 536.412s179FAIL