Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[core-api] order of transactions with same timestamp

See original GitHub issue

Describe the bug The API returns transactions with the same timestamp in an unpredictable and wrong manner.

To Reproduce Steps to reproduce the behavior:

Go to https://dexplorer.ark.io/api/v2/wallets/cam/transactions?page=1&limit=5&orderBy=timestamp:desc
Go to https://dexplorer.ark.io/api/v2/wallets/cam/transactions?page=2&limit=5&orderBy=timestamp:desc
Search for: 64c15a316786216825f68240ce733db052d2788f43ea94acdb5acabe484382c4
The same transaction is present in both responses

Both JSON responses: https://pastebin.com/UFrG0qhZ

Expected behavior The above mentioned transaction should not be present on the second page, if it is on the first.

Additional context The results should be sorted by an additional fallback parameter with a unique value, e.g. the transaction id.

Issue Analytics

State:
Created 5 years ago
Comments:8 (6 by maintainers)

Top GitHub Comments

1reaction

datedcommented, Feb 1, 2019

Yea pagination introduces a whole set of problems on its own which have to be dealt with by the application, but this can be done only if the ordering is deterministic (if the dataset doesn’t change that is).

0reactions

datedcommented, Jul 15, 2019

This issue appears to be back @faustbrian @vasild.

Visit https://explorer.ark.io/wallets/APSu7jcJbBvKQRoi43x4JUe8oYDEuSuPEr/transactions/all/1 and https://explorer.ark.io/wallets/APSu7jcJbBvKQRoi43x4JUe8oYDEuSuPEr/transactions/all/2 and search for e.g. 4f7c8…bb245