Skip to content
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.

Allow to use VS Code builtin extensions in che-theia #572

Closed
wants to merge 12 commits into from

Conversation

tolusha
Copy link
Contributor

@tolusha tolusha commented Dec 3, 2019

What does this PR do?

Allows to use VS Code builtin extensions in che-theia

What issues does this PR fix or reference?

eclipse-che/che#14759

@benoitf
Copy link
Contributor

benoitf commented Dec 3, 2019

hello, why are we not using vsix for VS Code built-in extensions ?
--> eclipse-theia/vscode-builtin-extensions#13

Also using a different package name is not nice for dependencies against these deps.
this hack shouldn't exist: https://github.com/eclipse-theia/theia/pull/6207/files

@che-bot
Copy link
Contributor

che-bot commented Dec 3, 2019

❌ E2E Happy path tests failed ❗

Try Che-Theia editor only Try Che-Theia with Java/maven example Try Che-Theia with NodeJs example

See Details

name link
che-theia docker.io/maxura/che-theia:572
che-theia-endpoint-runtime-binary docker.io/maxura/che-theia-endpoint-runtime-binary:572

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

⚠️ https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.

ℹ️ Use comment "crw-ci-test" to rerun happy path E2E test.

@AndrienkoAleksandr
Copy link
Contributor

@tolusha theia/typescript.spec.ts fails, fix it, please. I guess it is, because you changed list build-in plugins.

@tolusha
Copy link
Contributor Author

tolusha commented Dec 4, 2019

@benoitf
vsix files aren't published yet.

@tolusha
Copy link
Contributor Author

tolusha commented Dec 4, 2019

@benoitf

Also using a different package name is not nice for dependencies against these deps.
this hack shouldn't exist: https://github.com/eclipse-theia/theia/pull/6207/files

Not sure if I understand you. Could you elaborate more?

@che-bot
Copy link
Contributor

che-bot commented Dec 4, 2019

❌ E2E Happy path tests failed ❗

Try Che-Theia editor only Try Che-Theia with Java/maven example Try Che-Theia with NodeJs example

See Details

name link
che-theia docker.io/maxura/che-theia:572
che-theia-endpoint-runtime-binary docker.io/maxura/che-theia-endpoint-runtime-binary:572

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

⚠️ https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.

ℹ️ Use comment "crw-ci-test" to rerun happy path E2E test.

@tolusha
Copy link
Contributor Author

tolusha commented Dec 9, 2019

@benoitf
Could I have some response pls)

@tsmaeder
Copy link
Contributor

hello, why are we not using vsix for VS Code built-in extensions ?

Because some of the built-ins would translate to a separate Che plugin. For example, a theia image would not necessarily include a typescript compiler. Also, the referenced PR is quite new.

@benoitf
Copy link
Contributor

benoitf commented Dec 11, 2019

Because some of the built-ins would translate to a separate Che plugin. For example, a theia image would not necessarily include a typescript compiler

I'm not sure to understand. To me npmjs or vsix only change the distribution channel.

@tsmaeder
Copy link
Contributor

tsmaeder commented Dec 11, 2019

Because some of the built-ins would translate to a separate Che plugin. For example, a theia image would not necessarily include a typescript compiler

I'm not sure to understand. To me npmjs or vsix only change the distribution channel.

As I understand it, he generates a single vsix for all the extensions, which means we cannot omit any. With the npm published stuff, you can pick which ones you want.

@benoitf
Copy link
Contributor

benoitf commented Dec 11, 2019

ok got it. After discussion another PR was created eclipse-theia/vscode-builtin-extensions#15 (to have one VSIX per extension)

@che-bot
Copy link
Contributor

che-bot commented Dec 13, 2019

✅ E2E Happy path tests succeed 🎉

Try Che-Theia editor only Try Che-Theia with Java/maven example Try Che-Theia with NodeJs example

See Details

name link
che-theia docker.io/maxura/che-theia:572
che-theia-endpoint-runtime-binary docker.io/maxura/che-theia-endpoint-runtime-binary:572

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

@che-bot
Copy link
Contributor

che-bot commented Dec 13, 2019

❌ E2E Happy path tests failed ❗

Try Che-Theia editor only Try Che-Theia with Java/maven example Try Che-Theia with NodeJs example

See Details

name link
che-theia docker.io/maxura/che-theia:572
che-theia-endpoint-runtime-binary docker.io/maxura/che-theia-endpoint-runtime-binary:572

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

⚠️ https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.

ℹ️ Use comment "crw-ci-test" to rerun happy path E2E test.

@benoitf
Copy link
Contributor

benoitf commented Dec 17, 2019

@tolusha could you publish vsix files elsewhere as files are no longer there ?

@che-bot
Copy link
Contributor

che-bot commented Dec 18, 2019

❌ E2E Happy path tests failed ❗

Try Che-Theia editor only Try Che-Theia with Java/maven example Try Che-Theia with NodeJs example

See Details

name link
che-theia docker.io/maxura/che-theia:572
che-theia-endpoint-runtime-binary docker.io/maxura/che-theia-endpoint-runtime-binary:572

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

⚠️ https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.

ℹ️ Use comment "crw-ci-test" to rerun happy path E2E test.

Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
Signed-off-by: Anatoliy Bazko <[email protected]>
@che-bot
Copy link
Contributor

che-bot commented Dec 21, 2019

❌ E2E Happy path tests failed ❗

Try Che-Theia editor only Try Che-Theia with Java/maven example Try Che-Theia with NodeJs example

See Details

name link
che-theia docker.io/maxura/che-theia:572
che-theia-endpoint-runtime-binary docker.io/maxura/che-theia-endpoint-runtime-binary:572

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

⚠️ https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.

ℹ️ Use comment "crw-ci-test" to rerun happy path E2E test.

@tolusha
Copy link
Contributor Author

tolusha commented Dec 21, 2019

root ERROR Failed to resolve plugins from 'local-dir:///default-theia-plugins' Error: invalid comment length. expected: 2. found: 0
    at /home/theia/node_modules/yauzl/index.js:133:25
    at /home/theia/node_modules/yauzl/index.js:631:5
    at Immediate.<anonymous> (/home/theia/node_modules/fd-slicer/index.js:202:5)
    at runCallback (timers.js:705:18)
    at tryOnImmediate (timers.js:676:5)
    at processImmediate (timers.js:658:5)

@dmytro-ndp
Copy link
Contributor

@tolusha: you can use test workspace devfile to run workspace with your changes locally.

@tolusha
Copy link
Contributor Author

tolusha commented Dec 21, 2019

Cool!

@tolusha
Copy link
Contributor Author

tolusha commented Dec 23, 2019

@tsmaeder @svor
Unfortunately this issue requires additional investigation

@tsmaeder
Copy link
Contributor

'yauzl' being an unzip library, I suspect a broken zip/vsix. Unfortunately, the error message does not say which one.

@tsmaeder
Copy link
Contributor

crw-ci-test

@azatsarynnyy
Copy link
Member

Hello
Recently, a very similar mechanism was introduced in Theia upstream. For the details, see:

I think we can stop work on this PR and adapt Che Theia build instead to rely on the upstream:
download:plugins script provided by @theia/cli.

@tsmaeder
Copy link
Contributor

Yes, it just comes down to updating the packages.json of our assembly as in the example @azatsarynnyy linked. I propose we close this PR in favor of a new one.

@RomanNikitenko
Copy link
Member

Should we close the PR?
If I understand correctly, #618 brings VS Code builtin extensions in che-theia.

@azatsarynnyy @vzhukovskii

@vzhukovs
Copy link
Contributor

cc @tolusha

@azatsarynnyy
Copy link
Member

Should we close the PR?
If I understand correctly, #618 brings VS Code builtin extensions in che-theia.

@azatsarynnyy @vzhukovskii

Yes, it can be closed as we're relying on Theia's mechanism now.

@vzhukovs
Copy link
Contributor

Closed due to irrelevance

@vzhukovs vzhukovs closed this Feb 26, 2020
@vzhukovs vzhukovs deleted the ab/builtinext branch February 26, 2020 08:50
vinokurig pushed a commit that referenced this pull request Apr 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants