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

[Foundation] As a default, do not use the workaround in NSUrlSessionHandler for the threadpool. #8296

Merged
merged 1 commit into from
Apr 6, 2020

Conversation

mandel-macaque
Copy link
Member

When an application was moved the the background, the thread pool from
mono would be left in an unknonw state, making applications to stale
(https://xamarin.github.io/bugzilla-archives/58/58633/bug.html#c7).

This work was added in #5463

We now set the default behaviour to skip the workaround to see if the
new provided mono works as expected. We do not fully remove the
workaround because we need some real world testing.

If the new ThreadPool from mono does not work as expected we do provide
a property to re-add the workaround. The BypassBackgroundSessionCheck
can be set to false to allow users get it back.

The following is an example usage of the API:

// create your own handler instance rather than using the one provided by default.
var handler = new NSUrlSessionHandler() {
  BypassBackgroundSessionCheck = false, // readd the hack
};
var httpClient = new HttpClient (handler); // use the handler with the hack

This is a partial fix for #7080

…andler for thethreadpool.

When an application was moved the the background, the thread pool from
mono would be left in an unknonw state, making applications to stale
(https://xamarin.github.io/bugzilla-archives/58/58633/bug.html#c7).

This work was added in xamarin#5463

We now set the default behaviour to skip the workaround to see if the
new provided mono works as expected. We do not fully remove the
workaround because we need some real world testing.

If the new ThreadPool from mono does not work as expected we do provide
a property to re-add the workaround. The BypassBackgroundSessionCheck
can be set to false to allow users get it back.

The following is an example usage of the API:

```csharp
// create your own handler instance rather than using the one provided
by default.
var handler = new NSUrlSessionHandler() {
  BypassBackgroundSessionCheck = false, // readd the hack
};
var httpClient = new HttpClient (handler); // use the handler with the hack
```

This is a partial fix for xamarin#7080
@mandel-macaque mandel-macaque added the do-not-merge Do not merge this pull request label Apr 6, 2020
@mandel-macaque
Copy link
Member Author

Adding do not merge, we have to wait for the d16-7 branch to be created.

Copy link
Contributor

@whitneyschmidt whitneyschmidt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 thought - would it be useful to add an issue to track removing the hack code once it's verified that it's not needed anymore?

@mandel-macaque
Copy link
Member Author

@whitneyschmidt yes, we have Remove workaround for ThreadPool not working #7080 for that, this PR is not closing it :)

@monojenkins
Copy link
Collaborator

Build success
Build succeeded
API Diff (from stable)
API Diff (from PR only) (no change)
Generator Diff (no change)
Test run succeeded

@mandel-macaque mandel-macaque changed the title [Foundation] As a default, do not use the workaround in NSUrlSessionHandler for thethreadpool. [Foundation] As a default, do not use the workaround in NSUrlSessionHandler for the threadpool. Apr 6, 2020
@mandel-macaque mandel-macaque removed the do-not-merge Do not merge this pull request label Apr 6, 2020
@mandel-macaque
Copy link
Member Author

d16-7 branched, landing.

This pull request was closed.
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.

5 participants