forked from camilo/lhm
-
Notifications
You must be signed in to change notification settings - Fork 26
Use concrete Trilogy retry exception classes #183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
neilshopify
wants to merge
6
commits into
Shopify:master
Choose a base branch
from
neilshopify:fix-trilogy-retry-errors
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
1e71231
Use concrete Trilogy retry exception classes
neilshopify ef69166
Retry trigger checks during LHM invocations
neilshopify 2f72ea1
Use separate connections in parallel integration tests
neilshopify f4697fc
Bump version to 4.5.2
neilshopify 5e2f412
Use retriable-compatible max elapsed time
neilshopify 8ef59c6
Use finite max elapsed time for retriable compatibility
neilshopify File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,7 @@ | ||
| PATH | ||
| remote: . | ||
| specs: | ||
| lhm-shopify (4.5.1) | ||
| lhm-shopify (4.5.2) | ||
| retriable (>= 3.0.0) | ||
|
|
||
| GEM | ||
|
|
||
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,7 @@ | ||
| PATH | ||
| remote: .. | ||
| specs: | ||
| lhm-shopify (4.5.1) | ||
| lhm-shopify (4.5.2) | ||
| retriable (>= 3.0.0) | ||
|
|
||
| GEM | ||
|
|
||
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,7 @@ | ||
| PATH | ||
| remote: .. | ||
| specs: | ||
| lhm-shopify (4.5.1) | ||
| lhm-shopify (4.5.2) | ||
| retriable (>= 3.0.0) | ||
|
|
||
| GEM | ||
|
|
||
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -26,7 +26,7 @@ GIT | |
| PATH | ||
| remote: .. | ||
| specs: | ||
| lhm-shopify (4.5.1) | ||
| lhm-shopify (4.5.2) | ||
| retriable (>= 3.0.0) | ||
|
|
||
| GEM | ||
|
|
||
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,5 +2,5 @@ | |
| # Schmidt | ||
|
|
||
| module Lhm | ||
| VERSION = '4.5.1' | ||
| VERSION = '4.5.2' | ||
| end | ||
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| require 'minitest/autorun' | ||
| require 'minitest/spec' | ||
| require 'active_record' | ||
| require 'lhm/sql_retry' | ||
| require 'trilogy' | ||
|
|
||
| describe Lhm::SqlRetry do | ||
| describe '#default_retry_config' do | ||
| it 'uses an effectively unbounded max elapsed time value compatible with retriable validation' do | ||
| retry_config = Lhm::SqlRetry.new(nil).send(:default_retry_config) | ||
|
|
||
| assert_equal Float::MAX, retry_config[:max_elapsed_time] | ||
| end | ||
| end | ||
|
|
||
| describe '#retriable_trilogy_errors' do | ||
| it 'only uses exception classes as retriable keys' do | ||
| retry_errors = Lhm::SqlRetry.new(nil).send(:retriable_trilogy_errors) | ||
|
|
||
| retry_errors.each_key do |error_class| | ||
| assert error_class.is_a?(Class), "#{error_class.inspect} is not a class" | ||
| assert error_class <= Exception, "#{error_class.inspect} is not an exception class" | ||
| end | ||
| end | ||
|
|
||
| it 'matches trilogy connection error classes without using the ConnectionError module' do | ||
| retry_errors = Lhm::SqlRetry.new(nil).send(:retriable_trilogy_errors) | ||
|
|
||
| refute_includes retry_errors.keys, Trilogy::ConnectionError | ||
| assert_includes retry_errors.keys, Trilogy::BaseConnectionError | ||
| assert_includes retry_errors.keys, Trilogy::ConnectionClosed | ||
| assert_includes retry_errors.keys, Trilogy::SSLError | ||
| end | ||
| end | ||
| end |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Learning question — the old setup used the ConnectionError category, which covered everything under it automatically. Now that they're listed out one by one, if trilogy adds a new connection error type later, would we have to remember to add it here too?