Daniel Marjamäki

One thing I recomend when it comes to AI is to keep internal metrics so that you can better help you evluete AI future solutions how do you suggest that I do that?

I am adding AI reviews in opensource cppcheck AI is not perfect there is some bad review comments. As a PR author you can reject such comments by resolving them. My idea going forward is that I will not review a PR manually if there are open AI reviews. I want to limit the amount of manual reviews because; for reviewers it takes a lot of time. I don't want to waste time on nits that we could avoid automatically. I have to re-review the whole PR every time I see some nits. for developers manual reviews...

It's still being processed. If we will have trouble to keep up with open PRs I think we can launch more runner VMs. It might be low with 100/1000 .. I will see if it makes sense to increase these values later. At least if a runner is idle it could fill up more packages..

I am experimenting with a webserver that will execute the test-my-pr script on PRs. I want more or less that it will provide daca@home feedback directly when somebody works on a PR. http://ec2-16-170-140-253.eu-north-1.compute.amazonaws.com/ It is only executed on open non-draft PRs that have a successful CI. It will execute on 1000 packages if the PR modifies tokenizer or valueflow. Otherwise it will execute on 100 packages. When I started it , it would count packages even if they did not have C/C++...

I am experimenting with a webserver that will execute the test-my-pr script on PRs: http://ec2-16-170-140-253.eu-north-1.compute.amazonaws.com/ It will execute on 1000 packages if the PR modifies tokenizer or valueflow. Otherwise it will execute on 100 packages. When I started it , it would count packages even if they did not have C/C++ code that is fixed now.. AI-generated verdicts will be provided for a random subset of the warnings (up to 20 or so). Those should be taken with a grain of salt for...

Cppcheck 2.22.0

Let's start preparing for Cppcheck 2.22 release. My goal is to tag in ~ 14 days. If it looks stable enough. Let's try to focus on bug fixes for a while. Features I want to finish before the release: the "warning hash" related functionality to make it possible to create a baseline, to speedup cppcheck integration speedups in simplecpp, errorlogger, suppressions etc

Cppcheck-2.21.0