enum_virtual_ops fields next_block_range_begin and next_operation_begin

When querying

curl -s -X POST -d '{"jsonrpc": "2.0", "method": "account_history_api.enum_virtual_ops", "params": {"block_range_begin": 3168135, "block_range_end": 3168138, "group_by_block": false, "limit": 3}, "id": 1000}' https://api.hive.blog

we get

"next_block_range_begin": 3168136,
"next_operation_begin": "9223372036859513401",

using hafah we get

"next_block_range_begin": 3168136,
"next_operation_begin": 0,

So next_operation_begin I guess is incorrect in second case. Also after

curl -s -X POST -d '{"jsonrpc": "2.0", "method": "account_history_api.enum_virtual_ops", "params": {"block_range_begin": 4456473, "block_range_end": 4456475, "group_by_block": true, "limit": 4, "filter": 13085941963787312470}, "id": 1000}' https://api.hive.blog

we get different next_block_range_begin on hafah then on account_history_rocksdb, this might be related with ongoing filter issue - but needs checking