Skip to content
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

Failed to retrieve transactions #652

Open
2 tasks done
unek opened this issue Jul 2, 2024 · 2 comments
Open
2 tasks done

Failed to retrieve transactions #652

unek opened this issue Jul 2, 2024 · 2 comments

Comments

@unek
Copy link

unek commented Jul 2, 2024

New issue checklist

General information

  • Library version(s): 1.6.3
  • Browser version(s): node.js 18
  • Devices/Simulators/Machine affected: happens only on one machine
  • Reproducible in the testnet? (Yes/No):
  • Related issues:

Bug report

Expected behavior

getTransaction() returning transaction data

Actual behavior

getTransaction() throws an error for seemingly every transaction. Additionally, the console is full of logs saying:
BaseMiniConsensus: Failed to retrieve transaction proof to update mempool: Failed to retrieve transactions proof for [...]

This did not happen before. Happens only on one machine, does not throw on my dev setup.

Steps to reproduce

Run client.getTransaction('8393F45CEAE96110F598CB1A2CB4962480B073EECB8403B8B312EC1C4D610005')

Crash log? Screenshots? Videos? Sample project?

getTransaction('8393F45CEAE96110F598CB1A2CB4962480B073EECB8403B8B312EC1C4D610005') throws Error: Failed to retrieve transactions for g5P0XOrpYRD1mMsaLLSWJICwc+7LhAO4sxLsHE1hAAU=

@sisou
Copy link
Member

sisou commented Jul 12, 2024

Hi! I am unable to reproduce this, running client.getTransaction('8393F45CEAE96110F598CB1A2CB4962480B073EECB8403B8B312EC1C4D610005') on https://wallet.nimiq.com (get the client with client = await gimmeNimiqClient()). There I get the transaction details just fine.

What kind of environment are you running these commands in? Does your client have consensus when you run the command?

@unek
Copy link
Author

unek commented Jul 12, 2024

resetting the consensus (I think that's what it was, docs are down now, can't remember the method) few minutes after the app started fixed it, but only until next launch. now I switched to a volatile light client, and I'm no longer getting any errors.

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

No branches or pull requests

2 participants