Hi,
Welcome to the community!
Probably the missing piece here is making sure the exclusions are configured to match the paths SonarCloud sees during analysis. Yes, one would think that ** pretty much covered it, but… it’s worth double-checking via a peek in the UI.
Another thought that occurs to me is that sometimes there’s Java weirdness with \ vs / as the path delineator. So maybe also try **\\Thrift\\*?
And BTW you can check Administration → Background Tasks → [task row’s dot menu] → Show SonarScanner Context to see the parameters analysis actually ran with - just to make sure your exclusions weren’t overridden.
And after all that, if it’s still failing, can you provide your full analysis log?
The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.
This guide will help you find them.
Ann