Tomáš Nožička

> STEP: Waiting for the ScyllaCluster to re-deploy 09/16/22 08:48:55.746 > Sep 16 08:48:55.748: INFO: ScyllaCluster e2e-test-scyllacluster-mjgn4-6ndph/basic-h8jj7 (RV=7123) is rolled out Fixed by https://github.com/scylladb/scylla-operator/pull/1049

Also the CPU is high for the operator. In a steady state the starter binary is at almost 0% cpu and around 40MiB. Initially I thought this could be setup...

dupe of https://github.com/scylladb/scylla-operator/issues/749

Filled ScyllaDB issue as well https://github.com/scylladb/scylla-jmx/issues/236

> I only had a brief look - wouldn't a merkle tree be a standard approach for this use case? It's valid but more for cryptography. The approach here allows...

> would this approach also allow you to check if a given file was originally a part of the archive? Transiently. But anything can be messed up with, it's just...

>> What's most bothering is that the build doesn't fail and they silently break the docs. > What do you mean, does it fail to build? it builds but our...

> Probably introduced in https://github.com/scylladb/scylla-operator/pull/1540 that PR is removing the suppression and I see no suppression config in master, so this should warn and warnings become errors, so it should...

it may be a different one but there should be only ONE top level header (title) per page

/assign @dgarcia360