Cannot search extension by "m" text

[YiXuTa]

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Chrome 140.0.7339.208
• Local OS: Windows 11
• Remote OS: Debian 6.1.148-1 (2025-08-26) x86_64 GNU/Linux
• Remote Architecture: Amd64
• code-server --version: 1.104.1

Steps to Reproduce

1. Click "extensions" icon on the left panel
2. Input "m" text in the search component
3. then it will show "Error while fetching extensions"

Expected

If you input other text, such as "a" , or "b" , or "c" , it will list many extensions

Actual

just show error "Error while fetching extensions"

Logs

Screenshot/Video

No response

Does this bug reproduce in native VS Code?

No

Does this bug reproduce in GitHub Codespaces?

No

Are you accessing code-server over a secure context?

• I am using a secure context.

Notes

No response

[code-asher]

Are there logs in the browser console? Also you marked that this is also broken in VS Code and Codespaces, is that right?

[YiXuTa]

Are there logs in the browser console? Also you marked that this is also broken in VS Code and Codespaces, is that right?

It is good in VS Code and Codespaces, I changed the description.
The logs in chrome devtools is

workbench.js:sourcemap:34   ERR TypeError: Cannot read properties of null (reading 'filter')
    at SD (workbench.js:sourcemap:1267:17829)
    at UKe.K (workbench.js:sourcemap:1267:32638)
    at async UKe.I (workbench.js:sourcemap:1267:29200)
    at async UKe.I (workbench.js:sourcemap:1267:30399)
    at async a (workbench.js:sourcemap:1267:27630)
    at async UKe.query (workbench.js:sourcemap:1267:27918)
    at async Cht.queryGallery (workbench.js:sourcemap:2451:14748)
    at async Promise.all (/index 0)
    at async Izs.Mc (workbench.js:sourcemap:2447:13827)
    at async workbench.js:sourcemap:2447:4483

[code-asher]

Thank you for confirming. It looks like one (or more) of the extensions that comes up has no files (malloydata.malloy-vscode). I think it might be a bug with Open VSX.

[code-asher]

I opened an issue, we can track this here: eclipse/openvsx#1369