-
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
Suspicious code fragments in System.Text.Json #112344
Comments
Thank you for help to diagnose the code quality of runtime repository. The linked article is somehow verbose to read, and it doesn't contain links to the source code that we can identify quickly. The analyzer reports are valid. Some are already fixed (#112090) by inspiration of your article. Some issues are in the test/debug suite which are less severe. You are welcomed to submit pull requests to fix the issues. Please submit to main branch and we will backport real important fixes to existing releases. |
Tagging subscribers to this area: @dotnet/area-meta |
This issue has been marked |
Contributes to dotnet#112344
#112384 is fixing issues mentioned in the article that has not been fixed yet, except the ones in System.Text.Json. @dotnet/area-system-text-json Please take a look at the issues in System.Text.Json |
Tagging subscribers to this area: @dotnet/area-system-text-json, @gregsdennis |
The JSON-related code fragments cited are the following: runtime/src/mono/browser/debugger/BrowserDebugProxy/MemberReferenceResolver.cs Lines 59 to 71 in 7715391
runtime/src/mono/browser/debugger/BrowserDebugProxy/MemberObjectsExplorer.cs Lines 100 to 112 in 7715391
runtime/src/mono/browser/debugger/BrowserDebugProxy/Firefox/FirefoxMonoProxy.cs Lines 982 to 993 in 7715391
They use Json.NET DOM types and are part of the browser debugger. |
Tagging subscribers to this area: @thaystg |
Description
Hello.
I have checked project using the PVS-Studio analyzer. The results of the check revealed a number of suspicious code fragments that I have included in an article. You may be interested in taking a look at them.
It's worth noting that the article contains only the most interesting warnings issued by the analyzer. You can check your project in more detail using the free version of PVS-Studio for open-source projects.
Reproduction Steps
Not required
Expected behavior
Not required
Actual behavior
Not required
Regression?
No response
Known Workarounds
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: