-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Revert "FileConfigurationProvider.Dispose should dispose FileProvider when it owns it" #101609
Conversation
… when it…" This reverts commit 63fad3c.
/backport to release/8.0-staging |
Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/8850932380 |
a7d5f93
to
18230fc
Compare
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.
Thank you for reverting this. I think it's the right call given we can't guarantee the right behavior for everyone.
We should make sure to reactivate #86146. I think the workaround mentioned in that issue is what we'd recommend folks use for now. Maybe we can work to update things like hosting/configuration to lead people to a use a single FileProvider and make sure its lifetime is managed.
I've reopened the issue, unlocked the conversation and set the Milestone to 9.0. |
… when it owns it" (dotnet#101609) * Revert "FileConfigurationProvider.Dispose should dispose FileProvider when it…" This reverts commit 63fad3c. * Add test to ensure the bug does not come back
… when it owns it" (dotnet#101609) * Revert "FileConfigurationProvider.Dispose should dispose FileProvider when it…" This reverts commit 63fad3c. * Add test to ensure the bug does not come back
Reverts #86455 as it introduced a bug: #95745
fixes #95745