Alexolut

It seems that extension now work again for VS 17.3.5

In general I don't have problems with other code. That's why I think the triggers not relevant here. Only the line with `catch` is problematic from cpp-linter point of view....

The repo is private. Excerpt from related yaml file: ``` on: workflow_call: ``` I formatted entire file locally with clang-format 18.1.7 (on CI I see 18.1.8 but I had faced...

I disabled annotation as you suggested `file-annotations: false`. Below the output from action run: ``` Performing checkup on filename.cpp INFO:CPP Linter:Running "/usr/bin/clang-format-18 -style=file --output-replacements-xml --lines=96:103 filename.cpp" INFO:CPP Linter:Getting fixes with...

Look like the output is empty line? But same output here was before changing verbosity to debug.  > the .clang-format config file you are using I hope that default...

> Could this just be a difference in LF vs CRLF? I don't think so. All lines have the same ending. But complaining only for the one with `catch`. I...

output-replacement-xml returns me the following: ``` 
 ``` Offset 2789 points right after the curly brace: ``` } catch (const std::exception& ex) { ^ ``` I'm not sure what does...

According your explanation (if I understand it correctly) looks like clang-format expects the following:  After that linter suggests me to remove entire line 100!  Mind blowing. I work...

> You can do this with a python prompt `line: 99 col: 37` Exactly the same position that I mentioned before ``` } catch (const std::exception& ex) { ^ ```

It seems that we can post an issue (bug) on [LLVM GH](https://github.com/llvm/llvm-project/issues) only based on the assumption that we must get "empty" output-replacements-xml, e.g.: ``` ``` if we did clang-format...