Daniel Gutson
Daniel Gutson
Thanks for the fix of our code :) I agree that the message is misleading, pls consider to turn this ```[[]]``` issue in as a separate warning.
SARIF is by large becoming a standard with a reach far beyond github. It is being used by lint aggregators and dashboards (eg we are adding SARIF support to CodeChecker).
Hi, is anybody working on this enhancement?
I suggest that, instead of supporting multibytes as a terminator, generalize by supporting a rule as a terminator, so a multibyte constant sequence would be a particular case.
Hi, any update on this? @hirosassa do you need help?
(FWIW we're currently working on this, so feel free to assign this to @qequ)
Hi @fviernau, sure. I see what you mean. We have the "third party libraries" compliance audits, where we need to fill a number of data about the libraries _we_ use....
Hi @fviernau , I think that, based on your initial comment, we need to tackle first the separation between "internal/external" libs. This is a key underlying problem in our use...
@tsteenbe my main interest here is direct dependencies (depth 1) because this is what we can control; the generalization to depth N is, a generalization, but I don't have such...
I actually don't care about the level > X dependencies; however the "internal vs external" dependencies still hold (internal should not count in the X). Also, running ORT this way...