| 18 Oct 2025 |
K900 |
Gerrit Code Review v3.10 can receive automatic reviews and suggestions from external AI LLMs such as ChatGPT.
| 10:30:16 |
K900 | Boo | 10:30:18 |
Kirottu | Ew | 11:11:14 |
aloisw | One would hope that would be opt-in. | 11:46:24 |
helle (just a stray cat girl) | I mean worst case we have another custom patch on our Gerrit | 11:51:58 |
aloisw | Ah it's old news to begin with, gerrit.lix.systems is already on 3.12. As I have not seem LLM integration on it it's probably indeed opt-in. | 11:53:19 |
raitobezarius | 3.13 will make some stuff enabled by default sadly | 12:27:12 |
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 |
Rutile (Commentator2.0) feel free to ping | 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 |
Rutile (Commentator2.0) feel free to ping | ah | 15:09:46 |
Rutile (Commentator2.0) feel free to ping | gimme a sec | 15:09:50 |
Rutile (Commentator2.0) feel free to ping | https://gerrit.lix.systems/c/lix/+/4433 here ya go K900 | 15:12:20 |
helle (just a stray cat girl) | there you go for the +2 | 16:37:16 |
Rutile (Commentator2.0) feel free to ping | would like to know if it does work on staging-next before i merge and have to hotfix it again | 16:38:07 |
helle (just a stray cat girl) | you can test on staging-next yourself, sadly my computational capacity is taken up by some large cross compilations and uh, mentally by a mild migraine | 16:39:04 |
Qyriad | I like the implication that either your brain is doing part of the cross compiling or that your computer has a migraine | 17:41:16 |