Rh-che: Theia IDE **Next** editor fails to start with Che 7 workspace (works on minishift)

[ibuziuk]

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

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

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]

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

[mmorhun]

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

[mmorhun]

Just checked, it works from Firefox.

[garagatyi]

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

[garagatyi]

Tried to play with it in PR https://github.com/redhat-developer/rh-che/pull/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]

@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]

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

[ibuziuk]

yeah. sorry for the confusion - just updated the description

[AndrienkoAleksandr]

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]

@ibuziuk We got breaking changes from theia: https://github.com/theia-ide/theia/pull/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]

@ibuziuk Upstream issue: https://github.com/theia-ide/theia/issues/5046
Variant of the fix to track: https://github.com/theia-ide/theia/pull/5047

[ibuziuk]

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

[ibuziuk]

verified on che.openshift.io:

Closing. Thanks @AndrienkoAleksandr !