-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Openvsx dropped some extensions #18933
Comments
Sounds blocker to me:
|
from what I have tested, the ones that are failing: |
To prevent the problem for the user at runtime, we could make the plugins available "offline" in the registry. Currently the gh action build is not failing thanks to gh-action cache |
This was just discussed on the community call. Can someone summarize the proposed solution? |
I believe the way forward is:
|
* Temporarily remove some plugins where vsix files are missing Part of eclipse-che/che#18933 Signed-off-by: Eric Williams <[email protected]> * Update bash-debug location instead of removing Signed-off-by: Eric Williams <[email protected]>
@ericwill how about we contact the authors of the plugins in question and get them to sign? Has this been explored?
We need to be aware that we're crossing a line between referencing and distributing here. Not saying it's a problem, but the licensing requirements are different. |
@tsmaeder about contacting them.
|
@tsmaeder about offline mode: #18933 (comment)
|
…829) * Temporarily remove some plugins where vsix files are missing Part of eclipse-che/che#18933 Signed-off-by: Eric Williams <[email protected]> * Update bash-debug location instead of removing Signed-off-by: Eric Williams <[email protected]>
I am closing this one as it looks like everything has been merged/cherry-picked |
Describe the bug
Eclipse Che plug-in registry is referencing some extensions that have been dropped from OpenVsx registry
example: bash-debug
it was on openvsx/ google referenced it
but today https://open-vsx.org/extension/rogalmic/bash-debug is returning 404 error
Should be related to the final date of "publishing agreement deadline of January 29, 2021"
It makes impossible to build plugin registry without cache and workspaces using these plug-ins will fail
Che version
Steps to reproduce
Expected behavior
Working VS Code extensions
The text was updated successfully, but these errors were encountered: