Run Fallback Mode when Errno::ECONNRESET exception happens
#164
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tech solution
Run tests in Fallback Mode when
Errno::ECONNRESETexception happens.Other problem but not sure if related (probably not)
Let's Encrypt certificates may be affected by the recent expiry (2021-09-30) of their old root certificate.
https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/
This can cause that
knapsack_progem running on CI with old `OpenSSL version < 1.1.0 can't connect to Knapsack Pro API.user solution
Users should update OpenSSL to >= 1.1.0 (or docker image to newer one to get the latest openssl version) on their CI server. This way knapsack_pro gem can connect with Knapsack Pro API successfully.
Related to
https://gist.github.com/ArturT/1dfb677a886c6ae7242eaf13a2628d75