Skip to content

retry upon losing connection to docker - #334

Merged
jesseduffield merged 2 commits into
masterfrom
retry-if-docker-not-available
May 11, 2022
Merged

retry upon losing connection to docker#334
jesseduffield merged 2 commits into
masterfrom
retry-if-docker-not-available

Conversation

@jesseduffield

@jesseduffield jesseduffield commented May 11, 2022

Copy link
Copy Markdown
Owner

This PR does two things:

  1. if we can't connect to docker, we retry until we can
  2. CPU monitoring now only happens through the SDK, and I've changed how we collect CPU data so it's not sitting at 0 unnecesssarily

@jesseduffield
jesseduffield force-pushed the retry-if-docker-not-available branch 2 times, most recently from c73505c to 9616da0 Compare May 11, 2022 07:27
@jesseduffield
jesseduffield force-pushed the retry-if-docker-not-available branch from 9616da0 to d27ce19 Compare May 11, 2022 07:49
@jesseduffield
jesseduffield merged commit 13c0bfc into master May 11, 2022
@jesseduffield
jesseduffield deleted the retry-if-docker-not-available branch May 11, 2022 08:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant