cc32d9
cc32d9
I sent some TLOS directly from Scatter, and it showed me an URL for transaction pointing to http://bloks.io which is an EOS explorer
I'm porting EOSIO 2.1 to WAX (https://github.com/cc32d9/wax2.1), and tried to run a node with rockdb backend: ``` backing-store = rocksdb persistent-storage-num-threads = 6 persistent-storage-max-num-files = 10 persistent-storage-write-buffer-size-mb = 512 ```...
eosio-2.0.7, Ubuntu 18.04. The node has resynched Telos from genesis. All of a sudden, it stopped writing state history logs, without any messages related to the moment when it stopped...
While working on WAX snapshot unit tests, fixed a couple of old issues. Please merge in upstream: https://github.com/cc32d9/wax2.1/commit/b5ebb8fa9aa4b5b236506ade906f73e14638ce8e
This patch is renaming table deltas in the ABI for no apparent reason. This breaks compatibility with all state history readers, and makes no sense. https://github.com/EOSIO/eos/commit/d71569a15a881f03793534ba84a0f20b3f1998f7 This change must be...
If state history plugin has problems writing the history, nodeos must stop immediately. related issue: #9483 Another condition is if the node starts from a snapshot that is newer than...
This PR sets "canonical" mode in JSON encoder, so that all documents are created with sorted hashes. Otherwise Perl randomizes them and they are difficult to analyze. Also this PR...
I will collect more data when my current test finishes. But this is what I observed with 2.16.2b: a cluster of 4 machines, running latest 5.2 release candidate. The keyspace...
I'm developing this module using AZMQ, and it doesn't go well: https://github.com/EOSChronicleProject/eos-chronicle/blob/81dbe977a264fcf674d95ef941a5479ef30f78bc/chronicle-receiver/exp_zmq_plugin.cpp the data is written quite intensively with async_send, and it's not limited by high watermark like the synchronous...
I'm using chainbase in Chronicle project in concurrent mode: one process opens the database in read-write mode and is constantly updating it as state history data arrives. Then, multiple read-only...