-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Check by the PVS-Studio Static Code Analyzer #9
Comments
After these potential bugs are fixed, we should also pass Degate through different sanitizers, and perhaps add automatic checks to the CI/CD pipeline. I'll add that to the list of to-do. |
Cool! These warnings open the room for discussions.
|
I'm glad that you are interested in the project. To answer you:
If you have any other questions, or if you need more clarification, please feel free. I have less time than before (since April 2021), but I will try to keep the project alive. For example, I plan to publish a bugfix update (2.0.1) soon. |
The code base changed in 3 years, I'll close this issue but add a new pass of static analyzers to the planning. |
Issue
Analyzer issued a lot of warnings.
To Reproduce
Environment:
Web Report
Degate_c2d0f29_PVS-Studio-log.zip
Text Report
Click to expand
The text was updated successfully, but these errors were encountered: