vscode: Can't search in workspace that includes folder using a FileSystemProvider

VSCode Version: 1.44.0
OS Version: Ubuntu 18.04.4 LTS

Steps to Reproduce:

Open workspace with contains non default file system (file) but with provider defined in plugin
Try and search

Does this issue occur when all extensions are disabled?: Yes

/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:4376 No search provider registered for scheme: ccfs, waiting

(anonymous) @ /usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:4376
searchWithProviders @ /usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:4376

(anonymous) @ /usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:4375

processTicksAndRejections @ internal/process/task_queues.js:85

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 20 (8 by maintainers)

Commits related to this issue

Don't wait on search providers for schemes other than vscode-remote Fix #94928 — committed to microsoft/vscode by roblourens 4 years ago

Most upvoted comments

This is fixed in Insiders but not stable yet.

roblourens on Apr 14, 2020

is that expected that users of my extension have to between choose to use file search or work with external file system?

because feature is in proposed stage but causes issues in stable release

PS. please note; v1.43.0 works fine

PPS:

Does this issue occur when all extensions are disabled?: Yes

means issue is not related to the extension. I’m correct?

SqrTT on Apr 10, 2020

Hi, I’m getting the following log after the 1.44.0 update whenever I CTRL+P (search hangs and does not show results):

[13934:0413/222622.335701:INFO:CONSOLE(4376)] "No search provider registered for scheme: gitlens, waiting", source: file:///usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js (4376)

disinstalling, reinstalling gitlens or disabling extensions was of no help.

Recreating the workspace fixed it.

Version: 1.44.0
Commit: 2aae1f26c72891c399f860409176fe435a154b13
Date: 2020-04-08T11:22:13.689Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.3.0-45-generic

Feder1co5oave on Apr 14, 2020

let’s start from scratch. Extension don’t use search provider API (TextSearchProvider and FileSearchProvider or any other from proposed). Extension use registerFileSystemProvider and registers scheme ccfs this was working well for last two years, but starting v1.44.0 users with the extension face issue with broken search with mentioned in subject error.

I don’t need proposed API. I need search working again. At this point I can fix this only by drop off feature which relays on FileSystemProvider. Is there way to save feature?

SqrTT on Apr 10, 2020