vscode does not report the same thing as the terminal

[cloud-walker]

I'm using v2.18.3 installed globally, but if I use the vscode extension, its reporting different things, in particular the issue that I had on #62 its still there for vscode, I'm missing something?

[BartWaardenburg]

Thanks for reporting this! The root cause: the VS Code extension auto-downloads fallow-lsp to its global storage directory on first activation, but never re-downloads it when the extension or CLI is updated. So the LSP diagnostics were coming from the old binary while your terminal CLI was v2.18.3.

Fixed in d3a0be3 — the extension now checks the installed binary's version on activation and automatically re-downloads if it doesn't match the extension version. This will ship in the next VS Code marketplace release.

Immediate workaround (until the extension update is published):

1. Open the VS Code "Fallow" output channel (View → Output → select "Fallow")
2. Find the line Using fallow-lsp binary: /path/to/...
3. Delete that file (and the fallow sibling in the same directory)
4. Reload VS Code — it will download the latest binaries

[BartWaardenburg]

This fix is now released in v2.19.0. After updating the extension from the VS Code marketplace, it will automatically detect the stale binary and re-download the matching version. Thanks for reporting this!