tui: re-probe chain height while the node screen is up #181

Merged
sirius merged 1 commit from wt/tui-sync-status into main 2026-10-11 20:28:29 +00:00
Owner

The F7 NODE row was a snapshot taken when the wallet child started. Ctrl-R only re-read that cache, so a syncing in-process daemon looked frozen (height stuck, while get_info on 127.0.0.1:18081 kept moving).

The event loop now calls wallet_child_refresh about once a second while F7 or the wallet screen is up. The probe runs off the UI thread. When it finishes, the NODE row is rewritten from the new height and target. Ctrl-R starts a probe instead of reprinting the cache.

Proof: cargo test --locked --lib the_setup_screen_sync_line_follows_a_later_probe (pass). cargo clippy --locked --lib --tests -- -D warnings (pass). wallet_setup_config_tests: 28 passed.

The F7 NODE row was a snapshot taken when the wallet child started. Ctrl-R only re-read that cache, so a syncing in-process daemon looked frozen (height stuck, while get_info on 127.0.0.1:18081 kept moving). The event loop now calls wallet_child_refresh about once a second while F7 or the wallet screen is up. The probe runs off the UI thread. When it finishes, the NODE row is rewritten from the new height and target. Ctrl-R starts a probe instead of reprinting the cache. Proof: cargo test --locked --lib the_setup_screen_sync_line_follows_a_later_probe (pass). cargo clippy --locked --lib --tests -- -D warnings (pass). wallet_setup_config_tests: 28 passed.
tui: re-probe chain height while the node screen is up
All checks were successful
ci / test (pull_request) Successful in 14m16s
ci / sdk (pull_request) Successful in 1m28s
99581bec5e
The F7 NODE row kept the height from child start. Ctrl-R only
re-read that cache, so a syncing daemon looked frozen. Poll
wallet_child_refresh off the UI thread and copy the answer back.
sirius merged commit 9b827fc001 into main 2026-10-11 20:28:29 +00:00
sirius deleted branch wt/tui-sync-status 2026-10-11 20:28:29 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sirius/onionwire!181
No description provided.