-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[trimming] System.Diagnostics trimming out DebuggerTypeProxyAttribute. #57588
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @tommcdon, @krwq Issue Details
|
We have |
Updating area label - the failing tests are under System.Collections. |
Tagging subscribers to this area: @dotnet/area-system-collections Issue Details
|
@lewing @ilonatommy, any idea if this issue still occurs? |
This issue has been marked |
Number of tests are disabled against this issue. You can re-enable them and see whether they pass. |
This issue has been automatically marked |
This issue will now be closed since it had been marked |
We still have tests disabled against this issue. |
Still failing, I will take a look |
I do not see a point to expect from edit: the change of exception type is not the right solution, instead we probably should not have 0 Length of custom attributes. |
The failures are still relevant. |
The text was updated successfully, but these errors were encountered: