Skip to content

fix(thread): answer commands with missing/unknown wallet id instead of 500 - #7

Closed
feafel wants to merge 1 commit into
UTEXO-Protocol:mainfrom
feafel:fix/wallet-thread-missing-responses
Closed

feafel wants to merge 1 commit into
UTEXO-Protocol:mainfrom
feafel:fix/wallet-thread-missing-responses

Conversation

@feafel

@feafel feafel commented Oct 12, 2026

Copy link
Copy Markdown

When the wallet id was absent or the wallet unknown (dropped/evicted), the loop logged and continued without answering the oneshot, so send_cmd reported wallet thread is dead (HTTP 500) — indistinguishable from a dead server and an invitation to retry-storm it.

Adds an exhaustive respond_wallet_missing helper replying InvalidFingerprint (the id is the master fingerprint; maps to HTTP 400 via the existing classifier) on all 32 command variants. Drop/Stop keep their existing arms and semantics.

Verified by exhaustive variant cross-check against the enum + rustfmt parse. Full cargo test could not run here (private rgb-*-s-bfa deps need repo access) — requesting CI.

…f 500

When the wallet id was absent or unknown, the loop logged and continued
without answering the oneshot, so send_cmd reported 'wallet thread is
dead' (HTTP 500) - indistinguishable from a dead server and an
invitation to retry-storm. Reply InvalidFingerprint (HTTP 400, the id is
the master fingerprint) on every variant via an exhaustive helper.
@gofman8 gofman8 closed this Oct 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants