Error: `:0:0: filter ... not found`

[Ravlen]

After updating to 0.30.0 I'm now getting:

• :0:0: filter '.Level in ["suggestion", "warning", "error"]' not found

It seems to be a continuous error, as it appears in the bottom right corner of my VS Code repeatedly, appearing and disappearing while I have a markdown file open.

At one point I also received:

• :0:0: E100 [NewE201] Runtime error
  
  open /Users/path/to/gitlab/doc/.vale/gitlab_base/CodeblockFences.yml: no such file or directory
  
  Execution stopped with code 1.
  

  That file does exist, which suggests it's looking in the wrong place?

System:

• macOS 15.4.1
• VS Code 1.99.3
• Vale VSCode 0.30.0
• Vale 3.11.2

[dosubot]

Hello @Ravlen! I'm Dosu, a friendly bot here to help you solve bugs, answer questions, and navigate your way as a contributor. I'll be assisting you while you wait for a human maintainer. Let's tackle this issue together!

To address the error :0:0: filter '.Level in ["suggestion", "warning", "error"]' not found after updating to Vale VSCode 0.30.0, check your configuration settings in VSCode:

1. Open your VSCode settings and search for vale.valeCLI.minAlertLevel.
2. Ensure that the minAlertLevel is set correctly. It should be one of the following: "suggestion", "warning", or "error". The default setting is "inherited", which should automatically handle the filter creation.
3. If you have disabled spellcheck, ensure that vale.enableSpellcheck is set to false to apply the correct filter.

Regarding the runtime error related to CodeblockFences.yml, verify that your Vale configuration file is correctly set up and that Vale runs as expected on the command line. You can specify the path to your Vale configuration file using the vale.valeCLI.config setting in VSCode.

If the issue persists, consider downgrading to version 0.20.0 as a temporary workaround:

1. Right-click on the Vale VSCode extension in the extensions list.
2. Select 'Install specific version'.
3. Choose version 0.20.0.

This should help resolve the runtime error related to CodeblockFences.yml and the filter issue ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[Ravlen]

Troubleshooting steps I've taken:

First, just to be clear:

❯ vale -v
vale version 3.11.2

I checked my versions, and had a few listed in mise which we're using to handle dependencies:

❯ mise list vale
Tool  Version  Source                                Requested 
vale  3.9.3   
vale  3.10.0  
vale  3.11.2   ~/projects/gdk/gitlab/.tool-versions  3.11.2

My vale config file, in the VS Code settings (Vale > Vale CLI: Config) is set to: /path/to/projects/gdk/gitlab/.vale.ini

I've since removed the old versions, and now it is:

❯ mise list vale
Tool  Version  Source                      Requested 
vale  3.11.2   ~/.config/mise/config.toml  3.11.2

and

❯ vale -v
vale version 3.11.2

I restarted everything and updated to 0.30.0 and it seemed stuck for about a minute, then finally it started to show vale warnings/etc in markdown files with the plugin again. It seemed like it needed time for the LSP to start up? 🤔

[dnsmichi]

Similar error.

• macOS 15.4.1
• VS Code Version: 1.100.0
• Vale VSCode 0.30.0
• Vale version from asdf list value: 3.9.4

Looks like the newly introduced Vale LSP gets this specific filter pushed as a hardcoded entry. https://github.com/ChrisChinchilla/vale-vscode/pull/41/files#diff-84e6ec45ef01406e1d0a7699cd3a8cd6cc534505a520ef8c3e6a5690c58981deR140

  // Handle old enableSpellcheck to output as filter
  if (configuration.get("vale.enableSpellcheck") === false) {
    filters.push(`.Extends != "spelling"`);
  }

Not sure what it does but the corresponding error output leads me to thinking that LSP does not know about this configuration type.

[Error - 15:00:37] Parsing error: Msg("{\n  \"Line\": 0,\n  \"Path\": \"\",\n  \"Text\": \"filter '.Extends != \\\"spelling\\\"' not found\",\n  \"Code\": \"E100\",\n  \"Span\": 0\n}\n")

vale.enableSpellcheck is always false by default config. So the filter is pushed every time.

For now, I've reverted to installing a specific Value VS Code extension 0.20.0 version which works fine.