GitLab

repiared 003, 004, 005 and 006 test in dhf test group, now they checks ballance ev ery hour, not at the end of the test

[DLN/EMF] return filtered results even if we don't find the requested amount. If we don't find any, throw an exception to report the item number to begin further searching from. None of this is ideal, but it's a temporary solution until we can get something more performant, such as using hivemind to supply this data.

remove unused validate_transaction function (becomes it grabs a write_lock and it's just distracting to see it in the code when it's not used). Comment the point in API processing where lock is set to true for API calls.

It was yielding the write much more often than intended.  Now it will
only yield the write lock after it has held the lock for 500ms.
In addition, we added a warning log message if it takes more than 50ms
to acquire a write lock (if it's being starved by long-running read
requests)

originally with read locks, but they are implemented as calls to the
underlying account_history_api, which already does the correct locking

our node to lock up when under load.  Instead, we allow the mutex's default
behavior which is fair (Terekhov) locking.

Reduce max limit on get_account_history from 10k blocks of operations to 1k blocks. 10k blocks puts a lot of strain on hived.

the last few arguments

position in the static variant

(it will only be used if the client supports it)

account_history_api::get_account_history methor has been extended by optional argument specifying an operation filter. \see hive_operations_filter enum definition.
condenser_api::get_account_history now can take optionally 4. parameter specifying operation filter (\see account_history_api::get_account_history description)

The operations `clear_null_account_balance_operation`, `consolidate_treasury_balance_operation` added to `get_impacted_account_visitor`

Partially eliminated IS_LOW_MEM #ifdefs breaking reward calculations. Still code must be cleaned and all code (specific to comment-content, child-parent comment traversal) which was performed only on FAT node.

condenser_api::get_accounts call shall also query for account reputation (if reputation plugin was enabled).

include_reversible parameter is optional, and this is atm correclty handled by old chainbase AH plugin.

added by accident in the inital commit

Implement synchronization of processing currently processed block (head block) and an irreversible block being persisted
against API requests.

Reversible operations are included in result set of `enum_virtual_ops`
and `get_ops_in_block` methods if `include_reversible` has been set to true.

Fixed bug in `enum_virtual_ops` implementation leading to returning `next_block_range_begin`
less than block range begin specified to call, in case when no vops has been accepted.
This bug could have also negative impact on performance, since RocksDB had to jump
to the storage begin and this way significantly invalidate database caches.

This implementations is still WIP. More testing and thread locking must be added.

It seems that this bug was caused by a change in websocketpp 0.8.0.
where they started calling a callback into fc
https://gitlab.syncad.com/hive/hive/-/blob/47abb726e5b467b3b4d597d4c2ccaf39f015ec13/libraries/fc/src/network/http/websocket.cpp#L207-210
before we were allowed to set socket options.
This commit manually applies this patch:
https://github.com/zaphoyd/websocketpp/commit/a4494d5a1ed7de0099556b644b9a3ab975d8584f
Fixes #80