-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"No input file found for" with eslint import #1985
Comments
I'm running into the same issue. I wonder how this could ever have worked (when Sonar implemented importing), as the paths are seemingly always absolute? |
Ok, I found what's the problem, but not yet sure how to fix it. Your report contains disk name TBH I'm not sure on which side the bug is: ESLint generating bad path or ours not matching it when it's lower-case. I will try to follow up on it next week. |
I investigated bit further, and there is inconsistency in SonarQube's API wrt. capitalization of the drive letter in windows which is demonstrated in the following test
to workaround we can use Line 59 in b808d37
@NatMarchand thanks for reporting this problem, we will fix it in the next release |
I'm having the same problem but on mac. The very strange thing is that some days ago working very well. I've make a new fresh installation of all the required libraries and it's not working as well. |
@poyel could you be more specific which "same" problem you have? Describe properly your issue please. |
@vilchik-elena Yes, sorry. The generation of the json report by tslint is fine, but when i run sonar-scanner utility, i have this error |
It looks like 6.3 isn't around the corner. Is there any way we can work around this issue? |
I thought I was running into the same problem, but the comments here suggest the system drive casing as the problem. This is not what I'm seeing. The case to the base path (
|
@Bouke are you sure this file is part of analyzed project? do you see it imported in SQ UI? |
I'm currently encountering a bug.
SonarJS version: 6.2.0.12043
SonarQube version: 7.9.3.33349
I have a nodejs project in the folder e:\dev\somewhere\mysources
I'm running a eslint which outputs a report to e:\dev\somewhere\mysources\report\eslint.json
which looks like this:
I have sonar-project.properties which looks like this :
Then I run the scanner with this command line :
I got the following warning and no files get analyzed correctly :
The file DO exists at this path and I expect the lint errors/warnings taken in account.
When I make the paths relatives in the report/eslint.json file (manually), it does work (of course it cannot be a solution to always change the values of the linter report).
The text was updated successfully, but these errors were encountered: