RUBY-897 Print first 250 chars of query selector when logging and rescue inspect error #610
Conversation
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
|
Seems reasonable to me. |
…cue inspect error
estolfo
force-pushed
the
RUBY-897-log-inspect
branch
from
609d75f to
fba4b28
Compare
estolfo
added a commit
that referenced
this pull request
Apr 24, 2015
RUBY-897 Print first 250 chars of query selector when logging and rescue inspect error
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.
I guessed that 250 characters was a decent limit on the selector field when logging an error with a query but am open to suggestions for that limit to be decreased or increased.