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

getTransaction API request fails under specific conditions #1105

Open
ch-4ml opened this issue Aug 13, 2024 · 1 comment
Open

getTransaction API request fails under specific conditions #1105

ch-4ml opened this issue Aug 13, 2024 · 1 comment

Comments

@ch-4ml
Copy link

ch-4ml commented Aug 13, 2024

The getTransactions?address=${address}&limit=${limit} request fails under specific conditions.

If the number of queryable transactions for the given address is less than the limit, it should be possible to retrieve only the transactions within that range.

For example, if there are actually 8 queryable transactions and the limit option is set to 10, the response should include information for 8 transactions.

The following response is returned:
{ "ok": false, "error": "LITE_SERVER_UNKNOWN: cannot compute block with specified transaction: cannot find block (0,ee5241437c5c7412) lt=47596406000001: lt not in db", "code": 500 }

Call getTransactions?address=${address}&limit=100 for random accounts - preferably accounts with infrequent transactions. Some accounts successfully return a list of transactions, while others return the error mentioned above.

This can also be verified at https://toncenter.com/api/v2.

Mac OS (Apple Silicon)

@ch-4ml
Copy link
Author

ch-4ml commented Aug 13, 2024

When I use { archival: true }, it worked as intended.

But I think it's still needed even on non-archived light servers.

If the number of queryable transactions for the given address is less than the limit, it should be possible to retrieve only the transactions within that range.

@ch-4ml ch-4ml closed this as completed Aug 13, 2024
@ch-4ml ch-4ml reopened this Aug 13, 2024
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

1 participant