Fix Sequel integration not loading by default #516
Merged
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
delner
requested review from
pawelchcki and
palazzem
and removed request for
pawelchcki
palazzem
approved these changes
Aug 20, 2018
pawelchcki
approved these changes
Aug 20, 2018
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.
As reported by #514 the Sequel integration wasn't being loaded by default after its migration to the new integration API. We forgot to add
require 'ddtrace/contrib/sequel/integration'toddtrace.rb.This pull request adds that line, making the Sequel integration available by default. Users without this change can work around the problem by adding the following after
require 'ddtrace'in their configuration file: