-
Notifications
You must be signed in to change notification settings - Fork 26
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
Minor Upgrades for Backend Dependencies #7782
Conversation
// Makes txw2 write self-closing tags in xml (which we want). Not imported. | ||
"org.codehaus.woodstox" % "wstx-asl" % "4.0.6", | ||
// Json Web Tokens (used for OIDC Auth). import pdi.jwt | ||
"com.github.jwt-scala" %% "jwt-play-json" % "9.2.0", | ||
"com.github.jwt-scala" %% "jwt-play-json" % "10.0.0", |
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.
https://github.com/jwt-scala/jwt-scala/releases says no breaking changes, just the play 3 upgrade
@@ -68,7 +68,7 @@ class DataVaultTestSuite extends PlaySpec { | |||
"returns failure" when { | |||
"requesting invalid range" in { | |||
val result = (vaultPath / dataKey) | |||
.readBytes(Some(Range.Long(-10, 10, 1)))(globalExecutionContext) | |||
.readBytes(Some(Range.Long(-5, -10, 1)))(globalExecutionContext) |
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.
Negative starts for byte ranges are now actually allowed in GCS. So we need to test an even more invalid range to check that a failure is indeed returned (this test is intended to check that no exceptions bubble up but instead the tryo turns them into Box.Failures).
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.
LGTM. Thanks for bumping those dependencies 🎉
Steps to test: