-
Notifications
You must be signed in to change notification settings - Fork 131
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
Upgrade okhttp3 to latest #231
Conversation
@@ -106,7 +106,7 @@ public void shouldListLogEventsWithQuery() throws Exception { | |||
assertThat(recordedRequest, hasMethodAndPath("GET", "/api/v2/logs")); | |||
assertThat(recordedRequest, hasHeader("Content-Type", "application/json")); | |||
assertThat(recordedRequest, hasHeader("Authorization", "Bearer apiToken")); | |||
assertThat(recordedRequest, hasQueryParameter("q", "email%3A%5C*%40gmail.com")); | |||
assertThat(recordedRequest, hasQueryParameter("q", "email:\\*@gmail.com")); |
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.
I wonder if this change on behavior could be a breaking change??
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.
@lbalmaceda
This is my confession:
I'm not a real contributor to auth0...
I'm just suffering from dependency convergence. We're using Zipkin for tracing reporting, and it's already using version 3.14.3 of okhttp3.
For some reason, the auth0 project, which we're also using, is still back on version 3.9.1.
I fear these 2 versions are not compatible.
So I tried to just upgrade the okhttp3 version but found out that some tests are breaking, probably because of changes made between these versions handling URL encoding.
I'll be happy if someone who really understands what is the use of okhttp3 for auth0 will be able to handle this version bump.
I think it's important for auth0 to remain relevant for users, to always try and bump to the latest dependencies versions. Consider using @dependabot for this.
Could you please help with this?
Thanks a lot,
Uziel
@lbalmaceda |
@usulkies Thanks for the keep looking for a workaround to keep the tests untouched. Give me a few days to try this out manually, please. |
Hi @lbalmaceda , |
@usulkies I couldn't check this yet. Let me add a backlog item so at least the team is aware. |
Ran into this as well and raised #236 before I noticed this PR. This is really quite an old dependency now 😅 |
@usulkies Sorry for the delay here. We're going through some issues categorization and we think this is something worth adding to the SDK. We will investigate and test a bit the changes in terms of char encoding, and would need to bump the OkHttp version to the latest 3.x. Is that something you can do in the meantime? |
Hi @lbalmaceda I'm not sure I understood your question. What would you like me to do in the meantime? |
👋 that would be bumping to the current latest version, which according to maven central is |
Done |
@lbalmaceda When is the next planning meeting? Can you guess when we'll have this released? |
Hi @usulkies, I'm going to be reviewing this and will be following up this week. Thanks! |
Regarding the issues observed with tests failing prior to updating some usages to Rather than changing to not URL encode query parameters (which is what @usulkies I've gotten this working locally, so instead of asking you to revert your changes on this PR to use |
Closing this PR as it has been addressed in #262. We are hoping to do a release by the end of this week that will include this change; I'll follow up here when that's done. Thanks for your patience all! 🙇 |
Thanks @jimmyjames ! |
Just to make sure to close this loop - version 1.18.0 was released Friday and includes an update to use OkHttp 3.14.9 👍 |
Changes
Upgrading the okhttp3 version to the latest on the 3.x line
Change few tests assertion to match encoded URL
References
N/A
Testing
Please describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this library has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.
Checklist