[Cody Ignore] Process non-file URIs

[valerybugakov]

• Based on the thread here: VS Code: implement ContextFiltersProvider.isUriAllowed #3771 (comment)

[PriNova]

With the latest pre-release build with commit b67ea9b context fetching is totally broken.
I'm working on the Cody fork and asking questions on the chat with 'enhanced context' enabled and after fetched some files and lines I got the following error depicted in the image below.

I'm on WSL (Ubuntu) through Windows 11 as local host in VS Code.

[PriNova]

Switching the resolve.every to 'true' in line 63 does solve it

cody/lib/shared/src/prompt/prompt-string.ts

Lines 57 to 69 in 1a8baaf

	public async toFilteredString(
	contextFilter: Pick<ContextFiltersProvider, 'isUriIgnored'>
	): Promise<string> {
	const references = internal_toReferences(this)
	const checks = references.map(reference => contextFilter.isUriIgnored(reference))
	const resolved = await Promise.all(checks)
	if (!resolved.every(value => value === false)) {
	throw new Error(
	'The prompt string contains a reference to a file that is not allowed by the context filters.'
	)
	}
	return internal_toString(this)
	}

From the POV of logic this seems wrong, but semantically it seems right, because the functions are not following the happy path.
#3092 fixes this issue

[PriNova]

Switching the resolve.every to 'true' in line 63 does solve it

cody/lib/shared/src/prompt/prompt-string.ts

Lines 57 to 69 in 1a8baaf

	public async toFilteredString(
	contextFilter: Pick<ContextFiltersProvider, 'isUriIgnored'>
	): Promise<string> {
	const references = internal_toReferences(this)
	const checks = references.map(reference => contextFilter.isUriIgnored(reference))
	const resolved = await Promise.all(checks)
	if (!resolved.every(value => value === false)) {
	throw new Error(
	'The prompt string contains a reference to a file that is not allowed by the context filters.'
	)
	}
	return internal_toString(this)
	}

From the POV of logic this seems wrong, but semantically it seems right, because the functions are not following the happy path. #3092 fixes this issue

This is now obsolete for PLG users, because it works correctly without issue in the latest pre-release build since #3942 . The issue #3928 can be closed too, if PLG user.