Duplicate transactions returned

[sameersubudhi]

Actual behavior

Repeated transaction in the response even when queried with different offsets.

Eg: Transaction with ID 0557163513927ed2197ba9ddfbea20c39f62709ac49a4850991f0c7dea4d7e57 is present in the response for the following queries.

With offset 0:
https://service.lisk.com/api/v2/transactions?height=19365983&limit=10&offset=0&includePending=false

With offset 10:
https://service.lisk.com/api/v2/transactions?height=19365983&limit=10&offset=10&includePending=false

Expected behavior

The transaction should appear in only one of the responses since the offset in the second query is greater than equal to the limit set in the first query.

Steps to reproduce

• Query the above endpoints and check the transactions returned

Which version(s) does this affect? (Environment, OS, etc...)

v0.6.4

[sameersubudhi]

Resolved as part of PR #1326.

[sameersubudhi]

Was fixed for 0.7.0 in PR #1326. Re-opening it to fix for 0.6.4.