Picking a different wallet address which hasn't recorded any tx recently #3704
Conversation
This file contains 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
The recent tx that happened for this address was 3 weeks ago and no movement was recorded since then. A new tx recently appeared on the existing address which means it is still in use, hence the change.
tomaszslabon
approved these changes
Sep 6, 2023
lukasz-zimnoch
added a commit
that referenced
this pull request
Sep 14, 2023
Refs #3699 Depends on #3704 It happens that the keep-core client panics when interacting with the `go-electrum` library. We noticed a "concurrent write to websocket connection" error was thrown when calling `GetLatestBlockHeight()` function. The stack trace leads to gorilla/websocket/WriteMessage which is called from the `go-electrum` library. The latest block height call was already wrapped with a read mutex, but we should also wrap it with the write mutex to prevent such concurrent errors.
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.
The recent tx that happened for this address was 3 weeks ago and no movement was recorded since then. A new tx recently appeared on the existing address which means it is still in use, hence the change.