diff options
| author | bors <bors@rust-lang.org> | 2024-09-27 19:39:35 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-09-27 19:39:35 +0000 |
| commit | 46fe025e6870f6321436b22eca11c5e36437877a (patch) | |
| tree | a7bb665bc6b3067842d14e9c0737d23c422d6497 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 235809d088fed9f89f8077d1f7d746bf28208606 (diff) | |
| parent | 75ca498a488729e16d856de8fd6fd58aabf6f3d3 (diff) | |
| download | rust-46fe025e6870f6321436b22eca11c5e36437877a.tar.gz rust-46fe025e6870f6321436b22eca11c5e36437877a.zip | |
Auto merge of #18192 - darichey:read-buildfile-into-vfs, r=Veykril
Include buildfiles in VFS We subscribe to `textDocument/didSave` for `filesToWatch`, but the VFS doesn't contain those files. Before https://github.com/rust-lang/rust-analyzer/pull/18105, this would bring down the server. Now, it's only a benign error logged: ``` ERROR notification handler failed handler=textDocument/didSave error=file not found: /foo/bar/TARGETS ``` It's benign, because we will also receive a `workspace/didChangeWatchedFiles` for the file which will invalidate and load it. Explicitly include the buildfiles in the VFS to prevent the handler from erroring.
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions