-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wallet history timeout error when importing wallet with extensive transaction history #883
Comments
I've successfully created a wallet with import issues due to high balance/number of tx's. When this issue gets prioritized please DM me for seed words. I'm not sold on exactly what the issue is. I created a new wallet with 10000+ transactions and could still import without a problem. This particular wallet is older, and the age of the wallet may be part of the issue. |
I was one of the first block of test users on Tari. My AI cluster did a
bunch of the early blocks in testing. Ultimately, I loaded up Tari and
noticed an exception or timeout threshold was being hit. I noticed it was
no longer an issue about a month later.
Pretty sure it was fixed when the wallet logic was refactored a month after
launch.
It's no longer an issue, thanks.
…On Tue, Dec 3, 2024, 3:07 AM Brian Pearce ***@***.***> wrote:
I've successfully created a wallet with import issues due to high
balance/number of tx's. When this issue gets prioritized please DM me for
seed words.
I'm not sold on exactly what the issue is. I created a new wallet with
10000+ transactions and could still import without a problem. This
particular wallet is older, and the age of the wallet may be part of the
issue.
—
Reply to this email directly, view it on GitHub
<#883 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BLQZFLVYQDCPJ5H2QOFLLBL2DVYG3AVCNFSM6AAAAABQEYEOPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJTHEZTINZXGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
For now, I implemented infinite scrolling so we won't render all transactions at all(#1336). Going further, I created MVP(#1343) of pagination so we'll fetch only bunch of the latest transactions that we need at the time. It's on hold for now since it needs merging changes to the tari core repo or changing the way how we handle tx history(fetch, sort, save to store and handle tx events). |
I created a pr in the Tari repo to return transactions in a sorted vector: tari-project/tari#6733 I can continue working on this MVP using these changes |
As part of this task, I'll also debug Brian's issues with his wallet on esmeralda:
|
When importing wallet with an extensive tx history(2500txs),
It exceeds lifetime so we try to restart it over and over again |
Describe the bug
When importing my main wallet—which has hundreds of transactions—I repeatedly encounter a "wallet history timeout" error message. This issue occurs across multiple machines and seems to be tied to the depth of the wallet's transaction history. The application fails to import the wallet properly and does not provide helpful information for correlation.
Steps to reproduce the behavior:
Open the application.
Navigate to the wallet import feature.
Attempt to import a wallet with a large number of transactions (e.g., started within the first few hours of launch).
Observe that a "wallet history timeout" error message appears intermittently during or after the import process.
Expected behavior
The wallet should import successfully without any timeout errors, regardless of the number of transactions in its history.
Screenshots
If applicable, please add screenshots of the "wallet history timeout" error message to help explain the problem.
Desktop:
OS & Version: Microsoft Windows 11 Version 24H2 (OS Build 26100.2033)
Application Version: Tari v0.5.2x-v0.5.3x .* Havent see it in v0.5.31 yet, but the wallets still won sync.
Additional context
I tried using different builds and older versions of the application to determine if the wallet format had changed, but the issue persists.
The error does not occur when importing wallets with fewer transactions.
The problem seems consistent across multiple machines.
The lack of detailed error information makes it difficult to correlate and troubleshoot the issue.
The text was updated successfully, but these errors were encountered: