RE: HeyStack launch!
You are viewing a single comment's thread:
The issue is that in one call a transaction is being given the number 2484376:
But in another call that transaction is being given the number 2484378:
So I agree it's not a case of new transactions interspersing themselves inbetween the existing transactions since, as you say, new transactions are added as the end and the loading is backwards.
It's some kind of re-indexing issue. Perhaps indirectly caused by new transactions being added forcing a re-indexing? It needs to be something that mainly affects larger accounts (which typically have more frequent transactions).
Or the call being directed to a different source which has different numbers. A different node somehow? My knowledge of how the API returns are actually generated is sketchy.
Posted Using LeoFinance Beta
Oh thats actually really weird. Do you know if 2 different api nodes were used in there or if it was the one? There's a chance different nodes might have different actions at different indexes. Account history is being redone so it should hopefully be better in the future. On my call using @deathwing's node I got it at index id in the picture.
I'm just using 'https://api.hive.blog' for all calls.
It happens on Steem as well so I think it must be a pretty old issue.
Posted Using LeoFinance Beta
Try using https://api.deathwing.me for now. This should hopefully be fixed on launch of new account history.
OK, that's great advice thanks!
I used one of Roeland's nodes in some of my testing which may explain why I didn't see this error occurring as much previously.
Posted Using LeoFinance Beta