Tom Petracca

hmmm I quickly scanned code and read readme to no avail wrt environment variables

Do expect folks to still use `docker-compose` and `docker-run` plugins and have them work? Or is real goal that this entire repo is dead? CC @CRogers

would this not have worked? ``` dependencies { constraints { rootConfiguration('com.squareup.retrofit2:retrofit:2.4.0') { force = true } } } ```

I can see 6 failures in just the last 5 hours in circleci (across a variety of branches including `develop`): https://app.circleci.com/pipelines/github/palantir/atlasdb Examples: - https://app.circleci.com/pipelines/github/palantir/atlasdb/14101/workflows/ff13b06d-aa20-4036-b831-dbc5d32be769/jobs/63244/tests#failed-test-0 - https://app.circleci.com/pipelines/github/palantir/atlasdb/14101/workflows/ed5f1552-f9ab-462b-95e2-854ce4999908/jobs/63155/tests#failed-test-0 - https://app.circleci.com/pipelines/github/palantir/atlasdb/14093/workflows/e581c295-38a4-4880-8ad9-bebb3cdeebfa/jobs/63061/tests#failed-test-0 Failures is...

// recording a relevant conversation from 9 months ago (largely from @CRogers) I think it's technically possible (what isn't?) to build something like this: ``` recommendedProductDependencies { optionalProductDependency('thing-service') } ```...

So looking at my diff for `init.sh` I end up changing more then just the launch command because I also need to change how we track and set the pid...

Generally clarifying this issue is meant to be a follow-up from PDS-554079

In practice I think we just press on with "sweep at quorum", and either as part of that work or in a follow-up we essentially try to poll the clusters...