When doing block lookups, steem-ruby will use json-rpc-batch requests. It adheres to a maximum of 50 items in the batch. If the developer wants more than 50 blocks, steem-ruby automatically chunks so that it never requests more than 50 at a time.
At very infrequent intervals, a required block will not make it into the request. For example, a unittest required block_num 10501 in this result (below), but it was missing. From this VCR recording, it appears that it wasn't even requested by steem-ruby which implies there might be something wrong with the chunking logic.
Clue: It appears from the VCR recording that it chunked correctly by only requesting 50 blocks. But steem-ruby appears to have expected 51 blocks in the result.
When doing block lookups,
steem-ruby
will use json-rpc-batch requests. It adheres to a maximum of 50 items in the batch. If the developer wants more than 50 blocks,steem-ruby
automatically chunks so that it never requests more than 50 at a time.At very infrequent intervals, a required block will not make it into the request. For example, a unittest required block_num 10501 in this result (below), but it was missing. From this VCR recording, it appears that it wasn't even requested by
steem-ruby
which implies there might be something wrong with the chunking logic.Clue: It appears from the VCR recording that it chunked correctly by only requesting 50 blocks. But
steem-ruby
appears to have expected 51 blocks in the result.