-
Notifications
You must be signed in to change notification settings - Fork 653
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
Could not resolve config path #10418
Comments
Hey @M393, can you reproduce the issue on https://psalm.dev ? |
What's the exact psalm command you run? |
I'm using the vscode extension (v2.7.0). The log above is from the Output panel. |
Here is a simplified command of what the VSCode extension is running:
Output:
|
Will be fixed with my PR on the next release :-) |
I'm seeing this error notification pop up with Psalm 5.17 every time I open any PHP file in PhpStorm. For example:
|
I updated to 5.17 just now and no longer have this issue. Try to find out how with which parameters psalm is started. Install the last working version and get the command line arguments: |
The error occurs with both 5.16 and 5.17, but not with 5.15. According to Process Monitor the following command is being run:
|
@theodorejb could you try to run the command with windows directory separators in the file path, e.g. Do you still get this error then? It seems like the issue is in something that was supposed to be fixed by another PR here #10441 but perhaps this function has an issue when unix separators are used on windows? |
@kkmuffme I get the same error for both forward slash and backslash directory separators. |
I found the issue and opened #10452 to fix it. |
Yeah, it's kind of what I expected already #10441 (comment) |
These were missed in vimeo#10441. Fixes "Could not resolve config path" error on Windows (vimeo#10418).
On Windows 10 after upgrading from 5.15.0 to 5.16.0 I get this error:
C:\test
is the project location, seems like the path is concatenated to itself.Tried to remove everything from my config file, still same error:
The text was updated successfully, but these errors were encountered: