cc32d9
hi, with SSD1306_ERROR_ABORT deactivated, the `SSD1306_I2CMasterAttachDisplayDefault()` returns `true` if the display is disconnected, and only printing the error on the console: ``` E (21938) I2CDefaultWriteBytes: i2c_master_cmd_begin( I2CPortNumber, CommandHandle, pdMS_TO_TICKS( 1000...
@mnunberg will there be a chance to have this merged and pushed to CPAN?
we've seen this behavior again (also on WAX). Two identical physical servers, `v2.0.12wax01` from my wax2.0 repo, running a full WAX state history (from genesis), and Fabian's reader got stuck...
A 2.0.13 WAX node encountered this error, and stopped as expected. But it can't restart, as state history is missing the block. Failure where it stopped: ``` Sep 11 22:25:11...
the node went on with the head block, so it's difficult to reproduce or test a bugfix. But what it should've done is stop and not continue after there was...
no, it's the first time that I see the state history data corrupted. But what is a systematic problem, is that nodeos prints a warning and goes ahead, instead of...
Just experienced it with 2.0.6 on WAX on two independent servers within a couple of days. It just stops updating state history silently. The network has been experiencing intensive forks....
It looks like it's related to increased forks frequency, so #10080 might be related
in my case, logging was limited to error level, so no logs here
whatever the cause is, nodeos should stop if it cannot keep writing the ship data. Currently this failure is difficult to detect because it keeps sending empty ship data via...