curl / Mailing Lists / curl-library / Single Mail
Buy commercial curl support. We help you work out your issues, debug your libcurl applications, use the API, port to new platforms, add new features and more. With a team lead by the curl founder Daniel himself.

Re: Re: Time to drop codeql from the CI setup?

From: 陈星杵 via curl-library <curl-library_at_lists.haxx.se>
Date: Sun, 22 Dec 2024 18:07:32 +0800 (GMT+08:00)

So do you want to not use CodeQL in the Git? I think the bugs that CodeQL can find rely too much on expert knowledge, so this may be the reason why it is not effective.


&gt; -----原始邮件-----
&gt; 发件人: "Dan Fandrich via curl-library" <curl-library_at_lists.haxx.se>
&gt; 发送时间: 2024-12-22 03:33:43 (星期日)
&gt; 收件人: curl-library_at_lists.haxx.se
&gt; 抄送: "Dan Fandrich" <dan_at_coneharvesters.com>
&gt; 主题: Re: Time to drop codeql from the CI setup?
&gt;
&gt; On Sat, Dec 21, 2024 at 03:04:39PM +0100, Daniel Stenberg via curl-library wrote:
&gt; &gt; We started using codeql for static code analysis in 7183f5acc3d7ca39,
&gt; &gt; June 2020.
&gt; &gt;
&gt; &gt; Since then, not a single commit has been merged into the source code repository citing codeql as
&gt; &gt; source or reason. Yet, it keeps getting updated and we get constant reminders to upgrade the
&gt; &gt; pinning it to the latest hash.
&gt;
&gt; There have been 158 issues raised by CodeQL in that time. Every single one of
&gt; them was closed as "false positive" or "won't fix". So, I think you're onto
&gt; something.
&gt;
&gt; Dan
&gt; --
&gt; Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
&gt; Etiquette: https://curl.se/mail/etiquette.html
</dan_at_coneharvesters.com></curl-library_at_lists.haxx.se>
-- 
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette:   https://curl.se/mail/etiquette.html
Received on 2024-12-22