Skip to content
This repository has been archived by the owner on Mar 17, 2021. It is now read-only.

Theia IDE **Next** editor fails to start with Che 7 workspace (works on minishift) #1379

Closed
ibuziuk opened this issue Apr 19, 2019 · 13 comments
Labels

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Apr 19, 2019

Description

Theia IDENext / Master editor fails to start with Che 7 workspace
Seems to work just fine on minishift against upstream (7.0.0-beta-4.0-SNAPSHOT)
Default and master Theia editor work fine

Reproduction Steps

Create and start che 7 workspace with Theia IDE next editor
image

ERROR workspace fails to start (loader image is shown forever, refresh does not help)
image

OS and version:
che.openshift.io
che 7 beta 3 (theia next seems to work just fine against minishift 7.0.0-beta-4.0-SNAPSHOT)
Also Theia IDE *Master works fine

Diagnostics:

@ibuziuk ibuziuk changed the title Theia IDE **Next** editor fails to start with Che 7 workspace (works on minishift) Theia IDE **Next** / **Master** editor fails to start with Che 7 workspace (works on minishift) Apr 19, 2019
@ibuziuk ibuziuk changed the title Theia IDE **Next** / **Master** editor fails to start with Che 7 workspace (works on minishift) Theia IDE **Next** editor fails to start with Che 7 workspace (works on minishift) Apr 19, 2019
@ibuziuk
Copy link
Member Author

ibuziuk commented Apr 19, 2019

also one funny thing noted. Theia Master is also broken the same way on che.openshift.io, but it looks like it uses the very same image as next editor - Image: eclipse/che-theia:next

image

image

@mmorhun
Copy link

mmorhun commented Apr 22, 2019

@ibuziuk master is deprecated, next should be used instead. The fact that both use the same image is expected.

@mmorhun
Copy link

mmorhun commented Apr 22, 2019

Just checked, it works from Firefox.

@garagatyi
Copy link

@mmorhun also checked upstream Che on minikube - works correctly on Chrome

@garagatyi
Copy link

Tried to play with it in PR #1380 but got next error error

Message: "Failure executing: POST at: https://osoproxy.prod-preview.openshift.io/api/v1/namespaces/ogaragat-preview-che/configmaps. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. configmaps is forbidden: User "ogaragat-preview" cannot create configmaps in the namespace "ogaragat-preview-che": no RBAC policy matched. The error may be caused by an expired token or changed password. Update Che server deployment with a new token or password."

At the same time I'm able to login using the same account to prod-preview and start a workspace. But Theia with image next doesn't start neither there.

@ibuziuk
Copy link
Member Author

ibuziuk commented Apr 23, 2019

@mmorhun if master deprecated maybe it makes sense to hide this editor picking from UD completely ?
@garagatyi yeah, as I wrote in the description theia next seems to work just fine in the upstream

@garagatyi
Copy link

@ibuziuk I wasn't sure if you were talking about upstream or RhChe

@ibuziuk
Copy link
Member Author

ibuziuk commented Apr 23, 2019

yeah. sorry for the confusion - just updated the description

@AndrienkoAleksandr
Copy link
Contributor

AndrienkoAleksandr commented Apr 23, 2019

I see DOM Exception in the browser console, maybe it's a reason of the issue:

Stack trace

theia.b98e6bbaa771fa5efc00.js:1 Uncaught (in promise) DOMException
s @ theia.b98e6bbaa771fa5efc00.js:1
Promise.then (async)
c @ theia.b98e6bbaa771fa5efc00.js:1
(anonymous) @ theia.b98e6bbaa771fa5efc00.js:1
a @ theia.b98e6bbaa771fa5efc00.js:1
e.start @ theia.b98e6bbaa771fa5efc00.js:1
(anonymous) @ che.4e315c956aed0da82cb7.js:1
Promise.then (async)
nJ+H @ che.4e315c956aed0da82cb7.js:1
f @ runtime.e89741c86dc89dd2ddfd.js:1
t @ runtime.e89741c86dc89dd2ddfd.js:1
r @ runtime.e89741c86dc89dd2ddfd.js:1
(anonymous) @ theia.b98e6bbaa771fa5efc00.js:1
theia.b98e6bbaa771fa5efc00.js:1 root INFO Config file tasks.json does not exist under file:///projects

I am trying to build image with source map to get normal stack trace.

@AndrienkoAleksandr
Copy link
Contributor

@ibuziuk We got breaking changes from theia: eclipse-theia/theia#4724
Something wrong with theia start synchronization. On the local servers like minikube and minishift it's not reproducible...

Original error: InvalidStateError: getLayoutMap() must be called from a top-level browsing context.. We lost original exception, because theia code has some code section without try-catch error handling.

I begin analyze how to fix it.

@AndrienkoAleksandr
Copy link
Contributor

AndrienkoAleksandr commented Apr 30, 2019

@ibuziuk Upstream issue: eclipse-theia/theia#5046
Variant of the fix to track: eclipse-theia/theia#5047

@ibuziuk
Copy link
Member Author

ibuziuk commented May 2, 2019

Moved to Other Che Teams pipeline since OSIO team is not working on this issue

@ibuziuk
Copy link
Member Author

ibuziuk commented May 13, 2019

verified on che.openshift.io:

image

Closing. Thanks @AndrienkoAleksandr !

@ibuziuk ibuziuk closed this as completed May 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants