dualface / dualface/quicktui

[monitor] q.sh install verification failing

Closed
#294 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
48
Forks
2
Avg merge
1m
Merged PRs (30d)
7

Description

This issue is managed by the Verify q.sh Install workflow.

### q.sh install verification failing

Run: [34863747541](https://github.com/dualface/quicktui/actions/runs/34863747541)
Workflow: Verify q.sh Install
Ref: main
SHA: `f216d3c048fe0a71a9c9f9dc4a8e6cc0bddd8abe`
Hard failures: 1

| cell | expected | installed | reason | log tail |
| --- | --- | --- | --- | --- |
| `quicktui.ai/q.sh/preview` | expected=server2-preview-20260914-233210-a971ade26 | installed=server2-preview-20260914-233210-a971ade26 | pairing capability did not advertise quicktui.e2e.v1 with device_pop_v1 after 60 attempts in 20s; curl_status=0 | [truncated] 6 stage=capability curl_status=0 elapsed=5s schema_v2 probe attempt 17 stage=capability curl_status=0 elapsed=5s schema_v2 probe attempt 18 stage=capability curl_status=0 elapsed=6s schema_v2 probe attempt 19 stage=capability curl_status=0 elapsed=6s schema_v2 probe attempt 20 stage=capability curl_status=0 elapsed=6s schema_v2 probe attempt 21 stage=capability curl_status=0 elapsed=7s schema_v2 probe attempt 22 stage=capability curl_status=0 elapsed=7s schema_v2 probe attempt 23 stage=capability curl_status=0 elapsed=7s schema_v2 probe attempt 24 stage=capability curl_status=0 elapsed=8s schema_v2 probe attempt 25 stage=capability curl_status=0 elapsed=8s schema_v2 probe attempt 26 stage=capability curl_status=0 elapsed=8s schema_v2 probe attempt 27 stage=capability curl_status=0 elapsed=9s schema_v2 probe attempt 28 stage=capability curl_status=0 elapsed=9s schema_v2 probe attempt 29 stage=capability curl_status=0 elapsed=9s schema_v2 probe attempt 30 stage=capability curl_status=0 elapsed=10s schema_v2 probe attempt 31 stage=capability curl_status=0 elapsed=10s schema_v2 probe attempt 32 stage=capability curl_status=0 elapsed=10s schema_v2 probe attempt 33 stage=capability curl_status=0 elapsed=11s schema_v2 probe attempt 34 stage=capability curl_status=0 elapsed=11s schema_v2 probe attempt 35 stage=capability curl_status=0 elapsed=11s schema_v2 probe attempt 36 stage=capability curl_status=0 elapsed=12s schema_v2 probe attempt 37 stage=capability curl_status=0 elapsed=12s schema_v2 probe attempt 38 stage=capability curl_status=0 elapsed=12s schema_v2 probe attempt 39 stage=capability curl_status=0 elapsed=13s schema_v2 probe attempt 40 stage=capability curl_status=0 elapsed=13s schema_v2 probe attempt 41 stage=capability curl_status=0 elapsed=13s schema_v2 probe attempt 42 stage=capability curl_status=0 elapsed=13s schema_v2 probe attempt 43 stage=capability curl_status=0 elapsed=14s schema_v2 probe attempt 44 stage=capability curl_status=0 elapsed=14s schema_v2 probe attempt 45 stage=capability curl_status=0 elapsed=14s schema_v2 probe attempt 46 stage=capability curl_status=0 elapsed=15s schema_v2 probe attempt 47 stage=capability curl_status=0 elapsed=15s schema_v2 probe attempt 48 stage=capability curl_status=0 elapsed=15s schema_v2 probe attempt 49 stage=capability curl_status=0 elapsed=16s schema_v2 probe attempt 50 stage=capability curl_status=0 elapsed=16s schema_v2 probe attempt 51 stage=capability curl_status=0 elapsed=16s schema_v2 probe attempt 52 stage=capability curl_status=0 elapsed=17s schema_v2 probe attempt 53 stage=capability curl_status=0 elapsed=17s schema_v2 probe attempt 54 stage=capability curl_status=0 elapsed=17s schema_v2 probe attempt 55 stage=capability curl_status=0 elapsed=18s schema_v2 probe attempt 56 stage=capability curl_status=0 elapsed=18s schema_v2 probe attempt 57 stage=capability curl_status=0 elapsed=18s schema_v2 probe attempt 58 stage=capability curl_status=0 elapsed=19s schema_v2 probe attempt 59 stage=capability curl_status=0 elapsed=19s schema_v2 probe attempt 60 stage=capability curl_status=0 elapsed=19s schema_v2 probe exhausted attempts=60 elapsed=20s last_stage=capability curl_status=0 Sep 14 15:41:32 7f0903daa052 systemd[76]: Starting QuickTUI Remote Terminal Server... Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.391603 [INFO] [CONFIG] Set session_backend=tmux in /home/qtuser/.config/quicktui-server-v2/config.toml Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.391617 [INFO] [CONFIG] Set session_backends=tmux in /home/qtuser/.config/quicktui-server-v2/config.toml (auto-detected) Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.395540 [INFO] [CONFIG] rebaked QUICKTUI_TMUX_SOCKET /tmp/tmux-1000/default -> /tmp/tmux-1000/default Sep 14 15:41:32 7f0903daa052 systemd[76]: Started QuickTUI Remote Terminal Server. Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.511090 INFO agentwizard: using bundled registry version=8 Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.514284 [INFO] [SERVER] quicktui server2-preview-20260914-233210-a971ade26 listening on [::]:8022 Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.522021 INFO relay agent disabled; no config on disk Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.522214 [INFO] [UPGRADE] background update check started: current=server2-preview-20260914-233210-a971ade26 interval=2h0m0s timeout=20s Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.522226 [INFO] [UPGRADE] checking latest server release: current=server2-preview-20260914-233210-a971ade26 Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.522847 [INFO] [CONTROL] tmux state reconcile loop started: fast_interval=10s idle_grace=30m0s idle_interval=10m0s timeout=2m0s Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.535007 [INFO] [CONTROL] sessions_state updated: 0 session(s): [] Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.550185 [INFO] [AB2] provider setup current: provider=claude Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.550195 [WARN] [AB2] provider setup requires action: provider=codex detail=trust_required Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.550196 [INFO] [AB2] provider setup current: provider=grok Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.550198 [WARN] [AB2] provider setup requires action: provider=opencode detail=restart_required Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.615631 [ERROR] [AB2] live_collection: scan failed Sep 14 15:41:32 7f0903daa052 quicktui-server[238]: 15:41:32.726989 WARN agentwizard: initial refresh failed err="agentwizard: version rollback rejected: remote 4 < current 8" Sep 14 15:41:33 7f0903daa052 quicktui-server[238]: 15:41:33.398391 [INFO] [UPGRADE] no server update available: current=server2-preview-20260914-233210-a971ade26 latest=server2-preview-20260914-233210-a971ade26 asset=quicktui-server-linux-amd64 |

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with Verify q.sh Install workflow run 34863747541 on main at SHA f216d3c048fe0a71a9c9f9dc4a8e6cc0bddd8abe. Inspect the q.sh install verification entry point and its capability probe, focusing on why quicktui.e2e.v1 with device_pop_v1 is not advertised after 60 attempts. Done when the installed preview passes the capability check and the workflow succeeds.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, shell
Domain
ci-cd, cli, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.