Chronicle disconnects with a warning, not an error
Opened this issue · 2 comments
pvanderlinden commented
- often when I start it, I get
warn 2023-02-25T14:55:12.413 chronicle receiver_plugin.cpp:1054 save_contract_abi ] Cannot use ABI for connectfours: Invalid nesting, and then it disconnects from the consumer - on the other occasion when I actually got it working, I get messages which are not utf-8 encoded. How are messages encoded? I can not find this in the documentation, and the example uses utf-8 to decode messages
- I can't find much documentation on what the different message types mean and what they look like, am I missing something?
pvanderlinden commented
When the warning happens, the receiver seems to freeze (not responding to a keyboard interrupt).
cc32d9 commented
these warnings are not critical. They just mean some contracts have invalid ABI.
if you start the ship nodeos from snapshot and then start chronicle with --start-block option, it slurps all the blockchain tables in. On WAX, it may take an hour and a lot of server RAM. Your machine stops responding on keyboard because it may just be busy swapping.