EclipseFdn / EclipseFdn/open-vsx.org
Request Entity Too Large when publishing extension
- Dominant language
- TypeScript
- Stars
- 394
- Forks
- 145
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
In #2300, @kineticsquid mentioned it was decided internally to limit the Eclipse infrastructure (probably a proxy server like nginx) to 256M per extension.
As two years have passed:
* many more VS Code forks have popped up and are being adopted (e.g., Cursor, AntiGravity)
* LLM's are now a thing and are introducing larger and larger extensions
* we're no longer the only extension to be >256MB
I'm wondering whether in light of these changes, you'd reconsider. The OpenVSX software has had [support for 512MB](https://github.com/eclipse/openvsx/blob/84d01402f007233c8a1e5b28587e4f4784c7d3fd/server/src/main/java/org/eclipse/openvsx/ExtensionService.java#L39) for quite some time now.
As a matter of example, here are some other plugins that also exceed the 256 MB threshold on the VSC marketplace and that thus cannot be hosted on OpenVSX. There are even some out there that are larger than 512 MB.
| Extension | Size |
| ------------------------------------- | --------- |
| openai.chatgpt | 274.34 MB |
| MarsCode.marscode-extension | 289.33 MB |
| Oracle.sql-developer | 316.86 MB |
| ms-dynamics-smb.al | 304.87 MB |
| ASF.apache-netbeans-java | 277.71 MB |
| AzurePolicy.azurepolicyextension | 296.13 MB |
| nicepkg.aide-pro | 359.11 MB |
| JetBrains.resharper-code | 311.19 MB |
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.