Skip to content
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

Allow nullable executorService parameter in Dispatcher class constructor #8401

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

linleo345
Copy link

@linleo345 linleo345 commented May 9, 2024

Allow nullable executorService parameter in Dispatcher.kt constructor to maintain backwards compatibility with OkHttp 3.x migration to 4.x and beyond.

For some more context:
In my internal company's library, there were some code snippets using OkHttp 3.x that passed null into the Dispatcher constructor for the executorService parameter. This worked with the Java implementation of OkHttp library, but with the migration to Kotlin in 4.x and the executorService parameter not being nullable in Dispatcher constructor, this caused some projects to fail after upgrading from OkHttp 3.x to 4.x

Allow Nullable ExecutorService Parameter in Dispatcher Constructor to maintain backwards compatibility with OkHttp3 3.x migration to 4.x and beyond
@linleo345 linleo345 marked this pull request as ready for review May 9, 2024 19:41
@linleo345 linleo345 changed the title Allow Nullable ExecutorService Parameter in Dispatcher Constructor Allow nullable executorService parameter in Dispatcher class constructor May 9, 2024
@linleo345
Copy link
Author

linleo345 commented May 9, 2024

Can I get a re-run of the failed check? Looks like it failed testopenjdk11 action due to the flaky test issue in connectionPreWarmingHttp2

@yschimke
Copy link
Collaborator

yschimke commented May 9, 2024

That's ok. Noted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants