Improve indexer failure handling and reduce relay log noise - #953
Open
dangershony wants to merge 1 commit into
Open
Improve indexer failure handling and reduce relay log noise#953dangershony wants to merge 1 commit into
dangershony wants to merge 1 commit into
Conversation
- Remove yakihonne relays from default mainnet relay lists (SDK + webapp) - Demote relay disconnect logging: single-line warning instead of error + stack trace on every reconnect attempt; EOSE/OK tracking messages demoted to debug - Log which indexer is in use and include the indexer host in address-balance/UTXO failure messages so bug reports name the endpoint - Increase indexer HttpClient timeout from 10s to 30s (cold Fulcrum/ electrs can be slow; the gap-scan fans out many requests at once) - PaymentFlow: distinguish indexer/network failures from wallet issues in the user-facing error (point to Settings to switch indexer) and stop overwriting the real cause with 'wallet wasn't ready'
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to a user bug report on v0.2.34 (Fedora rpm): founder couldn't pay for project deployment — the deploy screen showed 'We couldn't start watching for your payment because the wallet wasn't ready' and the Receive modal hung on Loading.... Root cause: the primary indexer was timing out (10s HttpClient timeout), so
GetNextReceiveAddressnever produced an address, and the log never said which indexer failed. The log was also flooded with relay disconnect stack traces every minute.Changes
Indexer failure handling
Indexer <host> did not respond: ...) so future reports name the endpoint (MempoolSpaceIndexerApi).PaymentFlowViewModel: indexer/network failures now tell the user to check their connection or switch indexers in Settings (with the failure detail), instead of the misleading 'unlock the wallet' / 'wallet wasn't ready' text. The generic 'no receive address available' message no longer overwrites the real cause.Relay log noise
nostr-01/nostr-02.yakihonne.com) from the default mainnet relay lists in both the SDK and the webapp — they were returning 502s continuously. Note: existing installs keep them in saved settings; only fresh profiles get the new defaults.Validation
Angor.Shared,Angor.Sdk,App(design) andAngor.Client(webapp) all build with 0 errors.Not in this PR (known follow-ups)
AngorCreateFeeSats(10,001) + miner fee — paying exactly the requested amount leaves the wallet short.