Change:
} const fileMatchParentParts: URI[] = []; <del> let uri = this.uriParent(rawFileMatch.resource); </del> <ins> const normalizedResource = this.uriIdentityService.extUri.normalizePath(this.resource); let uri = this.normalizedUriParent(rawFileMatch.resource); </ins> <del> const debug: string[] = ['[search model building]']; while (!this.uriEquals(this.resource, uri)) { </del> <ins> while (!this.uriEquals(normalizedResource, uri)) { </ins> fileMatchParentParts.unshift(uri); const prevUri = uri; <del> uri = this.uriParent(uri); if (this._logService.getLevel() === LogLevel.Trace) { debug.push(`current uri parent ${uri} comparing with ${prevUri}`); } </del> <ins> uri = this.normalizedUriParent(uri); </ins> if (this.uriEquals(prevUri, uri)) { <del> this._logService.trace(debug.join('nn')); throw Error(`${rawFileMatch.resource} is not correctly configured as a child of its ${this.resource}`); </del> <ins> throw Error(`${rawFileMatch.resource} is not correctly configured as a child of its ${normalizedResource}`); </ins> } } <del> if (this._logService.getLevel() === LogLevel.Trace) { this._logService.trace(debug.join('nn')); } </del> const root = this.closestRoot ?? this; let parent: FolderMatch = this;

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.72.2 OS Version: Windows 10 Pro 21H2 Steps to Reproduce: a remote folder on the same network global search This was working for me previously, however, for some reason I have lost the ability to global search. I see below errors in the Log(Window). The open folder is: file://ha/config When I perform a search, I get these errors of " file .... is not correctly configured as a child of its" When I check the path of these files, I see that the search term I set are found on those files but for some reason vscode outputs an error. I tried a clean install but it didn't help. exclude settings and ignore files does not make any difference. The only workaround I found was to duplicate workspace option or saving the session as workspace Log (Window) Trace: Log (Host Extension) Trace
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.72.2. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
VS Code Version is 1.72.2, missed the last two digits.
I tried everything that I can think of (clean install with default settings, etc), but I cannot find what is wrong with it. I am not sure what is this error "is not correctly configured as a child of its". It seems like a trust issue for the folder but I granted access to the folder.

It is not in restricted mode and there is no other option I can think of.
Also encountering this issue on: Version: 1.72.2 Commit: Date: 2022-10-12T22:16:26.920Z Electron: 19.0.17 Chromium: 102.0.5005.167 16.14.2 V8: 10.2.154.15-electron.0 OS: Linux x64 5.18.10--generic Sandboxed: No Edit: Rolling back to a previous version of VS Code appears to have resolved the issue, possibly related to this fetaure?
Same on macOS Version: 1.72.2 Commit: Date: 2022-10-12T22:16:30.254Z (2 wks ago) Electron: 19.0.17 Chromium: 102.0.5005.167 16.14.2 V8: 10.2.154.15-electron.0 OS: Darwin x64 21.6.0 Sandboxed: No I was also thinking about something from those recent changes () because this is a recent issue, but I don't understand why it doesn't seem to affect everyone (like other teammates using the same workspaces). is there an easy way to rollback to a previous version of VSCode?
Is the path to one of your files really ? Or should it be (without the double slash before src). Just checking if the code somehow parses the path wrong.
Correct actual path is , but console logs are printed with a double slash
Your can follow the instructions on this stack overflow post
Hi ! I some extra logging on the Insiders build of vscode. Can you please do the following? Insiders the command from the command palette inside of Insiders. , then . a search where you run into the error. to the Output console and select the "Log (Window)" channel me the output that you see. It'd help me out a lot with fixing this since I'm unable to reproduce the issue from my side.
Sure thing will download it now.

Appreciate the help
Hope this is useful :slightlysmilingface: Version: 1.74.0-insider Commit: Date: 2022-11-04T05:19:14.702Z Electron: 19.1.3 Chromium: 102.0.5005.167 16.14.2 V8: 10.2.154.15-electron.0 OS: Linux x64 5.18.10--generic Sandboxed: Yes
Log output for the insider built: 1.74.0
Thanks for the logs it should be fixed in tomorrow's Insiders version!
What is the best way to verify this? I tried the following on VS Code stable, but I wasn't able to repro the issue: machines alex1 and alex2 alex2, open folder alex1d$reposmicrosoftvscode a search in the search view.
I've updated to the latest version of VS Code and haven't seen the issue since definitely resolved for me
you are referring to insider version correct? Can't wait for official November release (thx for the fix), and still don't get why it affected so few people.
Still facing same issue on macOS: Version: 1.74.0 Commit: Date: 2022-12-05T16:43:37.594Z (2 days ago) Electron: 19.1.8 Chromium: 102.0.5005.167 16.14.2 V8: 10.2.154.15-electron.0 OS: Darwin x64 21.2.0 Sandboxed: No I can also add that it is more painful when typing in search box (over copy pasting a term in search box or using cmd+shift+f) UI becomes unresponsive, can't stop the search, can't click anywhere else). And ultimately VSCode crashes.
Are you getting the error message of "is not correctly configured as a child of its"? What does your workspace path look like?
Yes error message is the same: It really looks like a debounce issue, when typing in search field. If I type 3 letters, it starts to hang. If I stop and wait, sometime the search ends (but with tons of messages like the one above), and then subsequent searches are stacked with previous ones in search results tree.

If I insist typing more letters, then VSCode crashes: a warning dialog is displayed with the message "The window is not responding. You can reopen or close the window or keep waiting". If I press Keep Waiting button, then it continues hanging, and reopen the same warning dialog. Meantime CPU consumption grows badly. Only solution is to close window. For information, I have 35 folders in my workspace, with some of them containing a huge hierarchy and lots of files. But until October this year everything was working fine. FWIW, in my workspace file, folders are declared like this:
Hi Can you follow the steps that I listed in and show me your logs? I just re- trace logging in Insiders.
Hello here is the produced log with Visual Studio Code - Insiders
using the insiders version restricted the potential cause to my workspace file content () - and it had to be on my side as this issue doesn't seem widespread. It turns out that some folders path in this file were ending with a slash, others not. I've removed ending slash everywhere, and everything seems to be back working. Could you confirm this situation could lead to this bug?
were you using trace logs when collecting logs? I can't seem to find the logs that I to insiders. The logs should be in the output channel.
@ this, were the folders actually ending in , or was it defined with a at the end in the file?
Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our . Please take the time to review these and update the issue. Happy Coding!
1) Yes I've used insider version, with all traces enabled (Developer: Set log level, then chose "Trace ... All" entry). I was also surprised to see no specific logs. 2) Some folders were defined with a "/" at the end the .code-workspace file.
were you on the channel for the output? <img width="142" alt="image" src="https://user-"
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!