DRILL-8438: Bump YAUAA to 7.19.2 #2808
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
cgivre
changed the title
|
@nielsbasjes Thanks for this. I'll rerun the failed test. Not sure why we're getting network issues but that seems unrelated to this PR. |
|
My fixes seem to have had the desired effect. |
jnturton
pushed a commit
that referenced
this pull request
Dec 31, 2023
* chore(deps): Update Yauaa to 7.19.2 * Additional fix, please squash on merge
jnturton
pushed a commit
to jnturton/drill
that referenced
this pull request
Dec 31, 2023
* chore(deps): Update Yauaa to 7.19.2 * Additional fix, please squash on merge
jnturton
pushed a commit
to jnturton/drill
that referenced
this pull request
Jan 3, 2024
* chore(deps): Update Yauaa to 7.19.2 * Additional fix, please squash on merge
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.
Updating Yauaa to latest version + fixing a bug in the caching in a test.
See #2807
@cgivre
I did 2 things here:
Let's see what the CI build thinks of this.