Catch potential tsquery errors more gracefully #235
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
japauliina
force-pushed
the
fix/catch-tsquery-errors
branch
from
f8c50bb to
b46d244
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #235 +/- ##
===========================================
- Coverage 71.38% 71.36% -0.03%
===========================================
Files 228 228
Lines 7067 7071 +4
Branches 1086 1086
===========================================
+ Hits 5045 5046 +1
- Misses 1847 1850 +3
Partials 175 175 ☔ View full report in Codecov by Sentry. |
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.
Description
Catch potential tsquery errors more gracefully
Context
Refs: Sentry issue 19731