Al
Al
 I have reverted the commit, but the behavior stays the same. I enabled the debug print, and it seems the coordinates are wrong even before the lines that I...
It's likely that Github Actions is currently having some issues and the antidote instance doesn't have enough time to shut down properly.
Maybe not, I don't know. It's strange that the Antidote instance doesn't want to stop.
Using `-erl_args -hidden` causes every suite to restart and reconnect every node. This causes an infinite request `log_read` loop in the `clocksi_SUITE`, which indicates either a problem with the `hidden`...
This can be reproduced locally with a docker setup by limiting the cpu of one of the data centers. [queues.zip](https://github.com/AntidoteDB/antidote/files/3838518/queues.zip)
Related: #320
Looking at the new Erlang API for time correction, I think we can fix this issue now. The time functions currently used are: bcoutner_mgr.erl: `erlang:timestamp()` (4 times) dc_utilities.erl: `erlang:system_time(micro_seconds)` and...
Maybe related to #203.
`rebar3 edoc` works, we need to deploy it somewhere.
``` %%% multiple_dcs_node_failure_SUITE ==> update_during_cluster_failure_test3: FAILED %%% multiple_dcs_node_failure_SUITE ==> Failure/Error: ?assertEqual([3], Res) expected: [3] got: [1008] line: 358 ```