Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
hive
hive
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 51
    • Issues 51
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 17
    • Merge Requests 17
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • hive
  • hivehive
  • Issues
  • #96

Closed
Open
Opened Oct 29, 2020 by Jason Salyers@jsalyersMaintainer

get_account_history not returning expected number of operations for 'dan' account

While doing some testing, we noticed that when we do a get_account_history call for the 'dan' account, we're often getting a different number of transactions than expected.

sample call (this particular one talks to steem-3, but it's reproducible on api.hive.blog as well):

curl -s -d '{"jsonrpc":"2.0", "id":2, "method":"call", "params":["condenser_api", "get_account_history", ["dan", 100, 5] ] }' http://steem-3:8091 | jq .

we would expect 5 records, but we only get 4.

Interestingly, looking at the ID numbers, it appears that it may think it found 5. In this particular call, we see indexes 96, 98, 99, and 100 returned, but 97 is missing (so possibly 97 was counted as being found before it failed to return 97 for whatever reason).

There's a theory that the account_history node has been configured to not store all transactions but still increment the index, or there is possibly some database corruption, or perhaps a serialization issue with certain transaction types. Definitely needs someone to take a closer look.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: hive/hive#96