| 18 Oct 2025 |
 just1602 | I'd prefer a good integration of static analyzer and linter instead of llm, tho.
Like, if clang-tidy catch something that would be nice it shows up directly in Gerrit UI instead of working on llm BS | 13:25:06 |
 raitobezarius | we could achieve automatic fixes via clang-tidy | 13:25:47 |
 Sergei Zimmerman (xokdvium) | Isn't there a tool like clang-tidy-sarif to produce sarif traces? Is there a standard solution for rendering sarif traces in gerrit? | 13:25:53 |
| raitobezarius | https://gerrit-review.googlesource.com/Documentation/rest-api-changes.html#fix-suggestion-info | 13:26:36 |
| raitobezarius | there's nothing to render SARIF traces in Gerrit | 13:26:55 |
| raitobezarius | but I can ask, there's a maintainer Q&A soonish | 13:27:18 |
| raitobezarius | maybe I can nerdsnipe GitLab people to do it | 13:27:24 |
 hexa | gitlab people do codeql format | 13:37:44 |
 K900 | @Rutile (Commentator2.0) feel free to ping https://git.lix.systems/lix-project/lix/commit/0ac71ea1cc32daec8ae824f9bf4ae73d61fdb4fc is failing for me on staging-next | 14:56:02 |
| K900 | For some reason my pytest is logging lang/test_lang.py::test_invalid_configuration[NOTSET] SKIPPED | 14:56:49 |
| K900 | For some reason my pytest is logging lang/test_lang.py::test_invalid_configuration[NOTSET] | 14:57:22 |
| raitobezarius | (i skipped everything due to hallway track alas) | 15:05:41 |
 legacy_rootile -> @rootile:flausch.social | urgh, what is it building on? as ci did pass...
though i can implement that alternative | 15:08:53 |
| K900 | staging-next, x86_64-linux | 15:09:12 |
| K900 | There is a pytest update in this cycle | 15:09:18 |
| K900 | So it's probably that | 15:09:21 |
