#analyzers — Public Fediverse posts

→ #Mythos finds a curl vulnerability
https://daniel.haxx.se/blog/2026/05/11/mythos-finds-a-curl-vulnerability/

“AI powered code #analyzers are significantly better at finding security flaws and mistakes in #source code than any traditional code analyzers did in the past. All modern AI models are good at this now. Anyone with time and some experimental spirits can find #security problems now.”

“We have not seen any AI so far report a #vulnerability that would somehow be of a novel kind or something totally new.”

#AI #curl #code #flaws

→ #Mythos finds a curl vulnerability
https://daniel.haxx.se/blog/2026/05/11/mythos-finds-a-curl-vulnerability/

“AI powered code #analyzers are significantly better at finding security flaws and mistakes in #source code than any traditional code analyzers did in the past. All modern AI models are good at this now. Anyone with time and some experimental spirits can find #security problems now.”

“We have not seen any AI so far report a #vulnerability that would somehow be of a novel kind or something totally new.”

#AI #curl #code #flaws

→ #Mythos finds a curl vulnerability
https://daniel.haxx.se/blog/2026/05/11/mythos-finds-a-curl-vulnerability/

“AI powered code #analyzers are significantly better at finding security flaws and mistakes in #source code than any traditional code analyzers did in the past. All modern AI models are good at this now. Anyone with time and some experimental spirits can find #security problems now.”

“We have not seen any AI so far report a #vulnerability that would somehow be of a novel kind or something totally new.”

#AI #curl #code #flaws

Hmm, just hit the first analyzer that needs relatively new version of Roslyn because of a new language feature I need to support (collection expression syntax) and now I'm not sure what to do. The existing analyzers target Roslyn 3.11 to support VS2019 16.11, which is very much not capable of running that. We'll need Roslyn 4.8, with a minimum supported VS version of 2022 17.8.

Time to bump up the minimum? What happens if I try to run Roslyn 4.8 analyzers in 2019? 🤔

#DotNet #Roslyn #Analyzers

Hmm, just hit the first analyzer that needs relatively new version of Roslyn because of a new language feature I need to support (collection expression syntax) and now I'm not sure what to do. The existing analyzers target Roslyn 3.11 to support VS2019 16.11, which is very much not capable of running that. We'll need Roslyn 4.8, with a minimum supported VS version of 2022 17.8.

Time to bump up the minimum? What happens if I try to run Roslyn 4.8 analyzers in 2019? 🤔

#DotNet #Roslyn #Analyzers

Hmm, just hit the first analyzer that needs relatively new version of Roslyn because of a new language feature I need to support (collection expression syntax) and now I'm not sure what to do. The existing analyzers target Roslyn 3.11 to support VS2019 16.11, which is very much not capable of running that. We'll need Roslyn 4.8, with a minimum supported VS version of 2022 17.8.

Time to bump up the minimum? What happens if I try to run Roslyn 4.8 analyzers in 2019? 🤔

#DotNet #Roslyn #Analyzers

Hmm, just hit the first analyzer that needs relatively new version of Roslyn because of a new language feature I need to support (collection expression syntax) and now I'm not sure what to do. The existing analyzers target Roslyn 3.11 to support VS2019 16.11, which is very much not capable of running that. We'll need Roslyn 4.8, with a minimum supported VS version of 2022 17.8.

Time to bump up the minimum? What happens if I try to run Roslyn 4.8 analyzers in 2019? 🤔

#DotNet #Roslyn #Analyzers

Hmm, just hit the first analyzer that needs relatively new version of Roslyn because of a new language feature I need to support (collection expression syntax) and now I'm not sure what to do. The existing analyzers target Roslyn 3.11 to support VS2019 16.11, which is very much not capable of running that. We'll need Roslyn 4.8, with a minimum supported VS version of 2022 17.8.

Time to bump up the minimum? What happens if I try to run Roslyn 4.8 analyzers in 2019? 🤔

#DotNet #Roslyn #Analyzers

Заводим друзей в C# (аки C++ friend, однако, более того)

Премьера! Драматическое признание в любви (к Ф...). 100 рублей и 100_000 юаней! Реализации аналогов друзей в C#, различные подходы, сравнительный анализ. Элвис жив! Вах, заходи дорогой(-ая), другом будешь!

https://habr.com/ru/articles/961264/

#c# #Friend #roslyn #analyzers

Probably unrelated, but does anybody know why the 4.x releases of Microsoft.CodeAnalysis.Analyzers have been unlisted from NuGet? https://www.nuget.org/packages/Microsoft.CodeAnalysis.Analyzers/4.14.0

We are still dependent on this for our "build & test with latest" validation.

#DotNet #Roslyn #Analyzers

hika: AI search for deeper thinking, not just find answers

#Sales #Analyzers #ArtificialIntelligence

https://awesomeindie.com/product/hika

Realizing that it's been more than a year since VS 2019 went out of mainstream support.

Is it time to remove support for it from the xUnit.net Analyzers yet?

#DotNet #CSharp #Roslyn #Analyzers

MiniMeters is a tiny but powerful collection of audio analyzers created by an independent and very responsive developer. Praised in several places, I tried it yesterday and then bought it for the price of a menu lunch that I took as crowdfunding. Beautiful UI, Linux support and CLAP plugin format were strong factors.

https://minimeters.app/

#MiniMeters #linuxaudio #analyzers #musicproduction #clap

If anyone needs to bulk generate GlobalSuppressions.cs from Roslyn analyzers (on a potentially huge solution), I wrote a sample here:
https://github.com/KirillOsenkov/CodeCleanupTools/blob/e6aa2eda6bdfc2f359a2254168fac73f9971e158/CodeFixer/Program.cs#L144-L233

VS itself doesn't do a reliable job here, but this tool should scale much better. Also shows how Roslyn concepts work.

#dotnet #roslyn #analyzers

I have taken to doing something I normally don't like. The analyzer tests for @xunit are out-of-our-control slow because of the time spent to invoke #Roslyn and get the results from the analyzer.

So I've been combining tests that might've been separate, with "this line is bad, these lines are fine" by way of putting them all in one test, but only expecting a subset to trigger the diagnostic. 😣

Example: https://github.com/xunit/xunit.analyzers/blob/01f4b5f74e81efb5b3e2141ded37a6fef6ae59eb/src/xunit.analyzers.tests/Analyzers/X1000/DoNotUseBlockingTaskOperationsTests.cs#L27-L45

#dotnet #csharp #analyzers

CI build time climb when introducing multiple #Roslyn version support for @xunit #analyzers. ⏱️

There is an unfortunate side-effect of writing #Roslyn #Analyzers with respect to compatibility.

The @xunit analyzers target Microsoft.CodeAnalysis 4.2.0 because that's what in VS 2022 17.2, which is currently still in LTS support.

CodeAnalysis 4.2.0 doesn't support C# 12. There are analyzers that are broken because of this, when used with C# 12 language features, and we can't fix them unless we're willing to throw away compatibility with everything before VS 2022 17.8.

#dotnet #csharp

Episode 471 of FreeCodeSession is live!

https://www.youtube.com/watch?v=S99_QRHg6YE

#CSharp #analyzers

Snatch revendique l'attaque informatique à l'encontre de 🇫🇷 ELITechGroup SAS (elitechgroup.com) #france #biomedical #innovative #scalable #ransomware #santé #databreach #care #confidence #analyzers #snatch #programs #careers #molecular #calibrators #reliability #financial #partnership #machines #chemistry #health #digital #solutions #pandemic #automation #market #threats #systems #smart #online #numérique #units #microbiology #reagents #analytical #solutions #technologies #informatique