Skip to content

Adding debugger warning message as known issue for .net7.0 #7916

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

Closed
wants to merge 2 commits into from

Conversation

thaystg
Copy link
Member

@thaystg thaystg commented Oct 31, 2022

Adding the warning message fixed in this PR as a known issue for .net7.0: dotnet/runtime#77616

Adding the warning message fixed in this PR as a known issue for .net7.0:
dotnet/runtime#77616
@mairaw
Copy link
Contributor

mairaw commented Apr 6, 2023

should this be merged @thaystg?

Copy link
Contributor

@mairaw mairaw left a comment

Choose a reason for hiding this comment

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

Left some comments to improve the content if we're merging this.

@@ -4,6 +4,14 @@ You may encounter the following known issues, which may include workarounds, mit

## .NET Runtime

### Warning messages while debugging a Blazor WebAssembly App using .NET 7
It is just a warning message, can be ignored and it will be fixed in the next servicing release.<br>
``` fail: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] sending error response for id: msg-B7CCCEF5694F2EF11713AE7F86743A45:::1017 -> [Result: IsOk: False, IsErr: True, Value: , Error: { "code": -32601, "message": "'DotnetDebugger.setDebuggerProperty' wasn't found" } ]```
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
``` fail: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] sending error response for id: msg-B7CCCEF5694F2EF11713AE7F86743A45:::1017 -> [Result: IsOk: False, IsErr: True, Value: , Error: { "code": -32601, "message": "'DotnetDebugger.setDebuggerProperty' wasn't found" } ]```
`fail: Microsoft.WebAssembly.Diagnostics.DevToolsProxy[0] sending error response for id: msg-B7CCCEF5694F2EF11713AE7F86743A45:::1017 -> [Result: IsOk: False, IsErr: True, Value: , Error: { "code": -32601, "message": "'DotnetDebugger.setDebuggerProperty' wasn't found" } ]`

@@ -4,6 +4,14 @@ You may encounter the following known issues, which may include workarounds, mit

## .NET Runtime

### Warning messages while debugging a Blazor WebAssembly App using .NET 7
It is just a warning message, can be ignored and it will be fixed in the next servicing release.<br>
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
It is just a warning message, can be ignored and it will be fixed in the next servicing release.<br>
It's just a warning message, but it can be ignored and will be fixed in the next servicing release.


### Unable to decompress 4GB+ zip archives

It's impossible to decompress large (4GB+ after compression) zip archives that consist of more than one zipped file. There is no known workaround. More information and workaround can be found at: https://github.com/dotnet/runtime/issues/77159. This issue will be fixed in the December servicing release.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
It's impossible to decompress large (4GB+ after compression) zip archives that consist of more than one zipped file. There is no known workaround. More information and workaround can be found at: https://github.com/dotnet/runtime/issues/77159. This issue will be fixed in the December servicing release.
It's impossible to decompress large (4GB+ after compression) zip archives that consist of more than one zipped file. There is no known workaround. More information and workaround can be found at: <https://github.com/dotnet/runtime/issues/77159>. This issue will be fixed in the December servicing release.

@thaystg
Copy link
Member Author

thaystg commented Apr 6, 2023

I think we don't need tis anymore

@thaystg thaystg closed this Apr 6, 2023
@rbhanda rbhanda deleted the thaystg-patch-1 branch April 11, 2023 15:30
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.

3 participants