BUG: The executable was not found. Use the 'sql,jinja-sql.executablePath' ... about vscode-sqlfluff HOT 9 CLOSED

I think this was it! #20 (comment)

The issue magically vanished for me, probably due to an update. Have you tried updating vscode and/or the plugin?

from vscode-sqlfluff.

This is related to an older version of lintingProvider.ts (in this commit that is still used in version 0.0.4 of the extension.

The message in the older version was "Cannot lint ${textDocument.fileName}. The executable was not found. Use the '${this.linter.languageId}.executablePath' setting to configure the location of the executable"

The error message is now different in master so the issue should disappear when a new version of the extension is realeased.

from vscode-sqlfluff.

I come with the same issue, do we have any news here? @nolanbconaway @dorzey

from vscode-sqlfluff.

I just installed the plugin and ran into the problem 😿

Is there any chance someone could please do a 0.0.5 release to get the fix out?

from vscode-sqlfluff.

@nolanbconaway thanks for reporting this for me Happy to provide any more info. The jinja-sql thing that showed up was weird! Current theory is somehow the Better Jinja extension is interfering? That's where the ,jinja-sql piece is coming from...

Mac Os 11.2
VSCode 1.51.1
Anaconda vSomething?
sqlfluff versions 0.3.6 and 0.4.0.a3 (both didn’t work?)
extension dorzey.vscode-sqlfluff=v0.0.4 and here’s what i think are my relevant settings in .vscode/settings.json

"python.pythonPath": "/Users/anders.swanson/opt/anaconda3/envs/dbt/bin/python",
"sql.linter.executablePath": "/Users/anders.swanson/opt/anaconda3/envs/dbt/bin/sqlfluff",
"sql.linter.run": "onType",
"files.associations": {
  "*.sql": "jinja-sql",
  "*.dbtspec": "yaml"
},

from vscode-sqlfluff.

glad to know you've got it under control! so if I were to build a vsix from the master branch, might I believe to format on save? Or is there something to the error message that I might need to change?

I don't know why this.linter.languageId = sql,jinja-sql.executablePath. Is this a problem? Is it because of my files.associations?

from vscode-sqlfluff.

I just built a new version from master locally and the linter works correctly now, even when providing a path for sqlfluff. The formatter doesn't seem to work though.

from vscode-sqlfluff.

I have seen that 0.0.5 is out now, so the extension should be working when using "sql.linter.executablePath" in the config.

from vscode-sqlfluff.

Sorry; I'm still catching up on the backlog of issues. Could somebody please confirm if this is fixed?

from vscode-sqlfluff.