"parsing error" reported, but can't find any trace in the log

[hannes]

When running sonar on a GitHub PR, I get a notification " The last analysis has a warning.See details"

Clicking on the link, I’m told “There were parsing errors in 1 files while analyzing the project. Check the logs for further details.”

Looking at the log (GitHub action, raw GitHub action log), I do not find anything related to “error” or “warn” or “parse”

Can anybody tell me what the “parsing error” may be about?

Setup:

• ALM used: GitHub
• CI system used: GitHub Acctions
• Scanner command used when applicable (private details masked): sonar was started via a GitHub action SonarSource/sonarqube-scan-action@aa494459d7c39c106cc77b166de8b4250a32bb97
• Languages of the repository: TypeScript
• Only if the SonarCloud project is public, the URL: Use istanbul for code coverage report generation by hannes-mk · Pull Request #394 · digitalservicebund/ris-adm-vwv · GitHub
• Error observed (wrap logs/code around with triple quotes ``` for proper formatting): none

[Colin]

Hey @hannes

I have to assume the error is this one:

11:58:06.316 ERROR Failed to analyze file [src/components/input/TextAreaInput.vue]: Cannot set property index of Error which has only a getter

So this is the trouble file.

It’s super convenient this is open source, I can hand it right over to our devs.

In the meantime you can exclude the file from analysis if the warning troubles you.

[hannes]

Thank you so much, Colin !
I wonder where my string searching failed to find that “ERROR”.

Great help!

[ilia]

Hello Hannes,

Thank you for your feedback. I have opened a ticket to track this issue: Jira