You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 16, 2021. It is now read-only.
I'm using minikube and I've deployed kubeless-ui via the k8s.yml file.
I am getting the service url via minikube service -n kubeless ui --url which gives me http://192.168.99.100:30113.
I am using Chrome Version 69.0.3497.100 (Official Build) (64-bit) on Windows 7 x64.
The bug also occurs on Firefox 62.0.3 (64-bit) so I don't think it's a browser specific bug.
Something goes wrong in the editor react component and the editor does not have syntax highlighting.
The chain of events starts in src/components/Editor/Editor.js at line 145 in render(), where the mode is computed for the AceEditor 3rd party component.
Somewhere along the way this fails because a Promise is not handled properly. Because of that the
browser issues a request to http://192.168.99.100:30113/mode-[object%20Promise].js which
of course fails.
I think you need an async/await pair either in runtimeToMode() or render() or both :).
In let mode = this.runtimeToMode(), mode ends up to be a Promise object, not the resolved result.
I wanted to run the app locally but I'm on Windows and node-sass does not support it.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I'm using
minikube
and I've deployedkubeless-ui
via thek8s.yml
file.I am getting the service url via
minikube service -n kubeless ui --url
which gives mehttp://192.168.99.100:30113
.I am using Chrome Version 69.0.3497.100 (Official Build) (64-bit) on Windows 7 x64.
The bug also occurs on Firefox 62.0.3 (64-bit) so I don't think it's a browser specific bug.
Something goes wrong in the editor react component and the editor does not have syntax highlighting.
The chain of events starts in
src/components/Editor/Editor.js
atline 145
inrender()
, where themode
is computed for theAceEditor
3rd party component.-> render() -> runtimeToMode() -> RuntimeHelper.runtimeToLanguage() ->
-> await this.getAllRuntimes() -> ... start returning
Somewhere along the way this fails because a Promise is not handled properly. Because of that the
browser issues a request to
http://192.168.99.100:30113/mode-[object%20Promise].js
whichof course fails.
I think you need an
async/await
pair either inruntimeToMode()
orrender()
or both :).In
let mode = this.runtimeToMode()
, mode ends up to be a Promise object, not the resolved result.I wanted to run the app locally but I'm on Windows and
node-sass
does not support it.The text was updated successfully, but these errors were encountered: