-
Notifications
You must be signed in to change notification settings - Fork 457
Closed
Labels
bugSomething isn't working as expectedSomething isn't working as expected
Description
Describe the bug:
Jupyterlab terminal fails to open from Launcher screen with error message i is not a constructor. Also, trying to start a terminal in Jupyterlab by selecting file->new->terminal fails to open a new terminal tab
Expected behaviour:
A new terminal tab should be opened in Jupyterlab
Steps to reproduce the issue:
- Run
docker run -p 8080:8080 mltooling/ml-workspace:latest - Navigate to http://localhost:8080
- Select
Open Tool,Jupyterlab - From Jupyterlab's Lancher screen click on
Terminalicon
Technical details:
- Workspace version : 0.8.4
- Docker version :
Client: Docker Engine Community:
Version: 18.09.2
API version: 1.39
Go version: go1.10.8
Git commit: 6247962
Built: Sun Feb 10 04:12:39 2019
OS/Arch: darwin/amd64
Experimental: false
Server Docker Engine Community:
Engine:
Version: 18.09.2
API version: 1.39 (minimum version 1.12)
Go version: go1.10.6
Git commit: 6247962
Built: Sun Feb 10 04:13:06 2019
OS/Arch: linux/amd64
Experimental: true
- Host Machine OS (Windows/Linux/Mac): MacOS Mojave 10.14.6
- Command used to start the workspace : docker run -p 8080:8080 mltooling/ml-workspace:latest
- Browser (Chrome/Firefox/Safari): Chrome 75.0.3770.142 (Official Build) (64-bit)
Possible Fix:
Additional context:
Using Safari as browser gives the error message undefined is not a constructor (evaluating 'new i(s,n)')
Metadata
Metadata
Assignees
Labels
bugSomething isn't working as expectedSomething isn't working as expected
