Draft
Conversation
Main item it to drop SerializationConstructor from Exception classes From the recommended actions in dotnet/docs#34893: Consider whether you truly need your custom exception type to be serializable. Chances are you do not need it to be serializable, as exception serialization is primarily intended to support remoting, and support for remoting was dropped in .NET Core 1.0.
1033c4a to
a78f254
Compare
Also support Abort/Kill on NET8 .NET 6.0 now throws PlatformNotSupportedException
a78f254 to
4bc7f34
Compare
This allows aborting threads stuck in Native waits
Member
|
@manfred-brands Is this still WIP, or has it been superseded by newer stuff? |
Member
Author
@OsirisTerje unfortunately still WIP because it deadlocks on Linux/MacOs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds support for proper Timeout to .NET 8.0