"Nbextensions" tab not showing in jupyterhub - docker

can anyone explain how to fix or troubleshoot this issue ?
How i understand i already install packages and enable all modules.
There are no any issue(at least i can't see any) with requirements or versions.
But after login in jupyterhub, the "Nbextensions" tab is not showing.
Output of commands jupyter --version , jupyter server extension list and jupyter nbextension list is printed below.
# jupyter --version
Selected Jupyter core packages...
IPython : 8.8.0
ipykernel : 6.20.2
ipywidgets : not installed
jupyter_client : 7.4.9
jupyter_core : 5.1.3
jupyter_server : 2.1.0
jupyterlab : 3.5.3
nbclient : 0.7.2
nbconvert : 7.2.9
nbformat : 5.7.3
notebook : 6.5.2
qtconsole : not installed
traitlets : 5.6.0
# jupyter server extension list
Config dir: /root/.jupyter
Config dir: /usr/etc/jupyter
Config dir: /usr/local/etc/jupyter
jupyter_server_terminals enabled
\- Validating jupyter_server_terminals...
jupyter_server_terminals 0.4.4 OK
jupyterlab enabled
\- Validating jupyterlab...
jupyterlab 3.5.3 OK
nbclassic enabled
\- Validating nbclassic...
nbclassic 0.5.1 OK
notebook_shim enabled
\- Validating notebook_shim...
notebook_shim OK
# jupyter nbextension list
Known nbextensions:
config dir: /root/.jupyter/nbconfig
notebook section
nbextensions_configurator/config_menu/main enabled
\- Validating: OK
contrib_nbextensions_help_item/main enabled
\- Validating: OK
varInspector/main enabled
\- Validating: OK
spellchecker/main enabled
\- Validating: OK
codefolding/main enabled
\- Validating: OK
tree section
nbextensions_configurator/tree_tab/main enabled
\- Validating: OK
config dir: /usr/etc/jupyter/nbconfig
notebook section
nbextensions_configurator/config_menu/main enabled
\- Validating: OK
tree section
nbextensions_configurator/tree_tab/main enabled
\- Validating: OK
config dir: /usr/local/etc/jupyter/nbconfig
notebook section
nbextensions_configurator/config_menu/main enabled
\- Validating: OK
contrib_nbextensions_help_item/main enabled
\- Validating: OK
tree section
nbextensions_configurator/tree_tab/main enabled
\- Validating: OK\
This commands i use for installation:
pip install jupyter_contrib_nbextensions
pip install jupyter_nbextensions_configurator
jupyter nbextension install --sys-prefix --py jupyter_nbextensions_configurator --overwrite
jupyter nbextension enable --sys-prefix --py jupyter_nbextensions_configurator
jupyter serverextension enable --sys-prefix --py jupyter_nbextensions_configurator
Based on github thread:
https://github.com/Jupyter-contrib/jupyter_nbextensions_configurator/issues/127#issuecomment-1301506342

Related

Vaadin upgrade 22.0.2 to 23.0.3 failed

I upgraded my application (i.e. I adjusted the version number in the pom) from Vaadin v22.0.2 (using which it built and ran perfect) to v23.0.3 and the below is what I get. The issue is again something with node but what is wrong here?
run maven build:
[INFO] Scanning for projects...
[INFO]
[INFO] -----------------< com.example:my-app >------------------
[INFO] Building my-app 1.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
Downloading from webjars: https://dl.bintray.com/webjars/maven/org/webjars/npm/mobile-drag-drop/maven-metadata.xml
[WARNING] Could not transfer metadata org.webjars.npm:mobile-drag-drop/maven-metadata.xml from/to webjars (https://dl.bintray.com/webjars/maven): Transfer failed for https://dl.bintray.com/webjars/maven/org/webjars/npm/mobile-drag-drop/maven-metadata.xml
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) # my-app ---
[INFO] Deleting U:\Documents\eclipse\workspace_Vaadin\my-app\target
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) # my-app ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] Copying 1 resource
[INFO] Copying 14 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) # my-app ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 85 source files to U:\Documents\eclipse\workspace_Vaadin\my-app\target\classes
[INFO]
[INFO] --- vaadin-maven-plugin:23.0.3:prepare-frontend (default) # my-app ---
[INFO] Project node version 16.13.0 is older than 16.14.0. Using node from C:\Users\xyz\.vaadin.
[INFO] Reflections took 1690 ms to scan 161 urls, producing 9229 keys and 45288 values
[INFO] Added 9 default dependencies to main package.json
[INFO] Copying frontend resources from jar files ...
[INFO] Visited 161 resources. Took 424 ms.
[INFO]
[INFO] --- vaadin-maven-plugin:23.0.3:build-frontend (default) # my-app ---
[INFO] Reflections took 1091 ms to scan 161 urls, producing 9229 keys and 45288 values
[INFO] Scanning classes to find frontend configurations and dependencies...
[INFO] Visited 4053 classes. Took 3945 ms.
[INFO] Visited 142 classes. Took 87 ms.
[INFO] Unable to determine version information. No vaadin_versions.json found
[INFO] Running `npm install` to resolve and optionally download frontend dependencies. This may take a moment, please stand by...
[INFO] Project node version 16.13.0 is older than 16.14.0. Using node from C:\Users\xyz\.vaadin.
[INFO] using 'C:\Users\xyz\.vaadin\node\node.exe C:\Users\xyz\.vaadin\node\node_modules\npm\bin\npm-cli.js --no-update-notifier --no-audit --scripts-prepend-node-path=true --ignore-scripts install' for frontend package installation
[WARNING] package-lock.json is missing from this project. This may cause the npm package installation to take several minutes. It is recommended to keep the package-lock.json file persistently in your project. Please stand by...
npm WARN ERESOLVE overriding peer dependency
npm WARN ERESOLVE overriding peer dependency
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: rollup-plugin-babel#4.4.0
npm WARN Found: rollup#0.47.6
npm WARN node_modules/.pnpm/validator#13.7.0/node_modules/validator/node_modules/rollup
npm WARN dev rollup#"^0.47.0" from validator#13.7.0
npm WARN node_modules/.pnpm/validator#13.7.0/node_modules/validator
npm WARN validator#13.7.0
npm WARN node_modules/validator
npm WARN validator#13.7.0
npm WARN node_modules/.pnpm/#vaadin/form#0.0.15_lit#2.0.0/node_modules/validator
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer rollup#">=0.60.0 <3" from rollup-plugin-babel#4.4.0
npm WARN node_modules/.pnpm/validator#13.7.0/node_modules/validator/node_modules/rollup-plugin-babel
npm WARN dev rollup-plugin-babel#"^4.0.1" from validator#13.7.0
npm WARN node_modules/.pnpm/validator#13.7.0/node_modules/validator
npm WARN
npm WARN Conflicting peer dependency: rollup#2.70.1
npm WARN node_modules/rollup
npm WARN peer rollup#">=0.60.0 <3" from rollup-plugin-babel#4.4.0
npm WARN node_modules/.pnpm/validator#13.7.0/node_modules/validator/node_modules/rollup-plugin-babel
npm WARN dev rollup-plugin-babel#"^4.0.1" from validator#13.7.0
npm WARN node_modules/.pnpm/validator#13.7.0/node_modules/validator
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: webpack-merge#4.2.2
npm WARN Found: peer eslint-plugin-jsx-a11y#"^3.0.2 || ^4.0.0" from eslint-config-airbnb#14.1.0
npm WARN node_modules/.pnpm/webpack-merge#4.2.2/node_modules/webpack-merge/node_modules/eslint-config-airbnb
npm WARN dev eslint-config-airbnb#"^14.1.0" from webpack-merge#4.2.2
npm WARN node_modules/.pnpm/webpack-merge#4.2.2/node_modules/webpack-merge
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer eslint-plugin-jsx-a11y#"^3.0.2 || ^4.0.0" from eslint-config-airbnb#14.1.0
npm WARN node_modules/.pnpm/webpack-merge#4.2.2/node_modules/webpack-merge/node_modules/eslint-config-airbnb
npm WARN dev eslint-config-airbnb#"^14.1.0" from webpack-merge#4.2.2
npm WARN node_modules/.pnpm/webpack-merge#4.2.2/node_modules/webpack-merge
npm ERR! Cannot read properties of null (reading 'isDescendantOf')
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\xyz\AppData\Local\npm-cache\_logs\2022-04-02T20_04_31_034Z-debug-0.log
[ERROR] Command `C:\Users\xyz\.vaadin\node\node.exe C:\Users\xyz\.vaadin\node\node_modules\npm\bin\npm-cli.js --no-update-notifier --no-audit --scripts-prepend-node-path=true --ignore-scripts install` failed:
[ERROR] >>> Dependency ERROR. Check that all required dependencies are deployed in npm repositories.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 07:43 min
[INFO] Finished at: 2022-04-02T22:11:51+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.vaadin:vaadin-maven-plugin:23.0.3:build-frontend (default) on project my-app: Could not execute build-frontend goal: Npm install has exited with non zero status. Some dependencies are not installed. Check npm command output -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Why am I not surprised? This would have been the first time that a Vaadin upgrade worked out of the box... :-(
Never mind - I did a "Vaadin dance" and then the build worked. And the application - at least on first sight - also worked OK again.
Later addition - since I was asked to provide the steps. My "Vaadin dance" looks like so:
#echo off
:package_entries
set fn=package.json
echo Step 1: Going to remove unsupported Vaadin v19+ entries from %fn%:
pause
rem let user see what we do:
#echo on
type %fn% | findstr /V /C:"#vaadin/application-theme-plugin" > %fn%_1
type %fn%_1 | findstr /V /C:"#vaadin/stats-plugin" > %fn%_2
type %fn%_2 | findstr /V /C:"#vaadin/theme-live-reload-plugin" > %fn%_3
type %fn%_3 | findstr /V /C:"#vaadin/theme-loader" > %fn%_4
rem remove an already existing backup - just in case (if there were one the cp below won't work)
rm %fn%~
rem rename back to original and keep a backup:
cp -b -f %fn%_4 %fn%
rem delete the temp. files":
rm %fn%_?
#echo off
echo unsupported Vaadin v19+ entries removed from %fn%.
:local_stuff
echo Step 2: Going to remove project local stuff:
pause
rem let user see what we do:
#echo on
call mvn vaadin:clean-frontend
rmdir /S /Q .\target
rmdir /S /Q .\node_modules
rmdir /S /Q .\frontend\generated
rm package.json
rm package-lock.json
rm pnpm-lock.yaml
rm pnpmfile.js
rm tsconfig.json
rm types.d.ts
rm webpack.config.js
rm webpack.generated.js
#echo off
echo project local vaadin-generated stuff removed.
:global_stuff
echo Step 3: Going to remove global stuff: removing pnpm stuff
pause
rem let user see what we do:
#echo on
rm -r -f %USERPROFILE%\.pnpm-debug.log
rm -r -f %USERPROFILE%\.pnpm-state.json
rmdir /S /Q %USERPROFILE%\.vaadin
rmdir /S /Q %USERPROFILE%\.pnpm-store
rem just in case - I encountered them here, too:
rmdir /S /Q D:\.pnpm-store
rmdir /S /Q U:\.pnpm-store
#echo off
echo global vaadin-installed stuff removed.
rem clear (and preload) default repository:
:repo_stuff
echo Step 4: Going to empty m2repository!
pause
rem let user see what we do:
#echo on
rem strange enough I again and again got "access denied" on certain .jars ||-( So we first take ownership...
takeown /R /F %USERPROFILE%\.m2\m2repository
rem ... before removing the stuff:
rm -r -f %USERPROFILE%\.m2\m2repository\*
cp -R %USERPROFILE%\.m2\repo-preload\* %USERPROFILE%\.m2\m2repository
#echo off
echo m2repository cleaned.
echo.
pause
I do this in multiple steps:
1st run: execute up to first pause - try to rebuild
if still not working:
2nd run: re-execute from top up to second pause - try to rebuild
if still not working:
3rd run: re-execute from top up to third pause - try to rebuild
At the latest after running the entire cmd-file the rebuilds so far always worked...
Deleting the node_modules folder worked for me most of the time.

NetSuite 64bit ODBC Driver installation on Ubuntu 18.04 Cluster giving error:- Can't open lib '/opt/netsuite/odbcclient/lib64/ivoa27.so

Have been running around this issue since 2-3 days now with no luck. Hope someone guides me and help resolve this issue here.
I am running a Python application from /home/admin/app/example.py directory in a 3 node Ubuntu 18.04 clustered environment which is supposed to connect to NetSuite via ODBC and read list of tables. The code and directory setup is same across all 3 nodes. There's a load balancer routing request to all these 3 nodes.
Here's example how the connection is made via PyODBC module:
import pyodbc
cnxn = pyodbc.connect('DSN=NetSuite;UID=user;PWD=pass'.format(dsn, uid, pwd), autocommit=True)
cursor=cnxn.cursor()
tables_list = []
for row in cursor.tables():
tables_list.append(row.table_name)
print (tables_list)
However, while running the python application on cluster, I am always getting error as:- Can't open lib '/opt/netsuite/odbcclient/lib64/ivoa27.so; even though the driver file, all its dependencies (via ldd command) and all the path variables i.e. $LD_LIBRARY_PATH, $ODBCINI and $OASDK_ODBC_HOME exists and is set to be available system-wide (added under /etc/environment file) as below on all the 3 nodes:
PYTHON_APP_HOME=/home/admin/app/
LD_LIBRARY_PATH="/opt/netsuite/odbcclient/lib64"
ODBCINI="/opt/netsuite/odbcclient/odbc64.ini"
OASDK_ODBC_HOME="/opt/netsuite/odbcclient/lib64"
Here's the output from "ldd" command for driver dependencies:
-rwxr-xr-x 1 root root 3277375 Jul 25 16:03 ivoa27.so
/opt/netsuite/odbcclient/lib64$ ldd /opt/netsuite/odbcclient/lib64/ivoa27.so
linux-vdso.so.1 (0x00007fff401a2000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fee1d589000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fee1d385000)
libicuuc.so.42 => /opt/netsuite/odbcclient/lib64/libicuuc.so.42 (0x00007fee1d12b000)
libicudata.so.42 => /opt/netsuite/odbcclient/lib64/libicudata.so.42 (0x00007fee1c0e6000)
libpam.so.0 => /lib/x86_64-linux-gnu/libpam.so.0 (0x00007fee1bed8000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fee1bcb9000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fee1b930000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fee1b592000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fee1b37a000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fee1af89000)
/lib64/ld-linux-x86-64.so.2 (0x00007fee1db3c000)
libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1 (0x00007fee1ad60000)
libcap-ng.so.0 => /lib/x86_64-linux-gnu/libcap-ng.so.0 (0x00007fee1ab5b000)
Below is how the steps were performed as per Netsuite driver README.txt instructions and the ODBC driver is setup similarly across all the 3 nodes on Ubuntu 18.04 OS.
The Netsuite 64bit Linux driver files/folders are unpacked and copied at location:
$cd /opt/netsuite/odbcclient/*. This entire dir,sub-dir & files within have both r+x permissions.
Installed libraries $sudo apt install unixodbc && apt-get install unixodbc-dev
Executed script/command provided by Netsuite from dir /opt/netsuite/odbcclient:- $source oaodbc64.sh (since it's a bash shell). This sets up the same variables as shown above.
From the same directory/folder ran below command for registering it as system-wide Driver:
$sudo odbcinst -i -d -f /opt/netsuite/odbcclient/odbcinst.ini
which returned message as:
odbcinst: Driver installed. Usage count increased to 1.
Target directory is /etc
odbcinst: Driver installed. Usage count increased to 1.
Target directory is /etc
Then ran below command also for installing it as system DSN:-
$sudo odbcinst -i -s -l -f /opt/netsuite/odbcclient/odbc64.ini
After this, checked /etc directory where both odbc.ini and odbcinst.ini files where created/registered. Both *.ini files were also given execute permissions to all.
-rwxr-xr-x 1 root root 500 Jul 24 10:31 odbc.ini
-rwxr-xr-x 1 root root 199 Jul 24 10:31 odbcinst.ini
$odbcinst -j
unixODBC 2.3.4
DRIVERS............: /etc/odbcinst.ini
SYSTEM DATA SOURCES: /etc/odbc.ini
FILE DATA SOURCES..: /etc/ODBCDataSources
USER DATA SOURCES..: /opt/netsuite/odbcclient/odbc64.ini
SQLULEN Size.......: 8
SQLLEN Size........: 8
SQLSETPOSIROW Size.: 8
$odbcinst -q -d
[ODBC Drivers]
[NetSuite ODBC Drivers 8.1]
$odbcinst -q -s
[NetSuite]
[ODBC]
I am also able to connect from each individual nodes via isql and also by running the example.py via python shell locally.
$isql -v 'NetSuite' 'user' 'pass'
+---------------------------------------+
| Connected! |
| |
| sql-statement |
| help [tablename] |
| quit |
| |
+---------------------------------------+
SQL>
But when running the same on cluster, it gives same error always. Please help. I am sure am missing something.
Here's the output of odbc.ini and odbcinst.ini files from /etc directory:
/etc$ more odbcinst.ini
[ODBC Drivers]
NetSuite ODBC Drivers 8.1=Installed
UsageCount=1
[NetSuite ODBC Drivers 8.1]
APILevel=1
ConnectFunctions=YYN
Driver=ivoa27.so
DriverODBCVer=03.52
FileUsage=0
SQLLevel=1
UsageCount=1
/etc$ more odbc.ini
[ODBC Data Sources]
NetSuite=NetSuite ODBC Drivers 8.1
[NetSuite]
Driver=/opt/netsuite/odbcclient/lib64/ivoa27.so
Description=Connect to your NetSuite account
Host=XXXXX.connect.api.netsuite.com
Port=1708
ServerDataSource=NetSuite.com
Encrypted=1
Truststore=/opt/netsuite/odbcclient/cert/ca3.cer
CustomProperties=AccountID=XXXXX;RoleID=XXXX
[ODBC]
Trace=0
IANAAppCodePage=4
TraceFile=odbctrace.out
TraceDll=/opt/netsuite/odbcclient/lib64/ddtrc27.so
InstallDir=/opt/netsuite/odbcclient
Tried below other things that didn't work:
Added ODBC variable paths within .profile,.bashrc ,/etc/profile,/etc/bash.bashrc other than /etc/environment.
Changed the owner of /lib64/ folder and all files within it and *.ini files under /etc from root to admin.
By creating symbolic links:
sudo ln -s /etc/odbcinst.ini /usr/local/etc/odbcinst.ini
sudo ln -s /etc/odbc.ini /usr/local/etc/odbc.ini
Thanks !!
UPDATE - SOLVED !! One important step that was missing from our end was the reboot/restart of all the nodes for those 3 variables to take into system-wide effect after it had been added into /etc/environment file(s).
In order to investigate, we printed below additional things into our code to ensure that it indeed is a 64 bit platform/architecture, drivers and datasources are registered and listed. However, the variables were still showing blanks/none. That verified that although the variable path was set/effective locally when running from individual nodes. However, when running from outside/via remote session, the variable values didn't get apply.
import os
import pyodbc
import platform
print(platform.architecture())
print (pyodbc.drivers())
print(pyodbc.dataSources())
print(os.environ["LD_LIBRARY_PATH"])
print(os.environ["ODBCINI"])
print(os.environ["OASDK_ODBC_HOME"])
Before reboot:
[2020-07-27 18:46:51,948] {logging_mixin.py:112} INFO - ('64bit', 'ELF')
[2020-07-27 18:46:51,949] {logging_mixin.py:112} INFO - ['ODBC Drivers', 'NetSuite ODBC Drivers 8.1']
[2020-07-27 18:46:51,950] {logging_mixin.py:112} INFO - {'NetSuite': '/opt/netsuite/odbcclient/lib64/ivoa27.so', 'ODBC': ''}
[2020-07-27 18:46:51,950] {logging_mixin.py:112} INFO - Error: 'LD_LIBRARY_PATH'
After reboot:
[2020-07-28 06:11:59,961] {logging_mixin.py:112} INFO - ('64bit', 'ELF')
[2020-07-28 06:11:59,963] {logging_mixin.py:112} INFO - ['ODBC Drivers', 'NetSuite ODBC Drivers 8.1']
[2020-07-28 06:11:59,965] {logging_mixin.py:112} INFO - {'NetSuite': '/opt/netsuite/odbcclient/lib64/ivoa27.so', 'ODBC': ''}
[2020-07-28 06:11:59,965] {logging_mixin.py:112} INFO - /opt/netsuite/odbcclient/lib64
[2020-07-28 06:11:59,965] {logging_mixin.py:112} INFO - /opt/netsuite/odbcclient/odbc64.ini
[2020-07-28 06:11:59,965] {logging_mixin.py:112} INFO - /opt/netsuite/odbcclient/lib64

Why JupyterLab not installed?

I want to install Jupyter Lab from github, and do it, and all ok,
but I am getting the following exception:
"Exception: Jupyter command jupyter-lab not found."
What am I missing?
$ pipenv install -e git+git://github.com/jupyterlab/jupyterlab.git#egg=jupyterlab
Installing collected packages: ipython-genutils, decorator, six, traitlets, Send2Trash, attrs, pyrsistent, jsonschema, jupyter-core, nbformat, ptyprocess, tornado, terminado, python-dateutil, pyzmq, jupyter-client, entrypoints, testpath, MarkupSafe, jinja2, webencodings, bleach, pygments, defusedxml, pandocfilters, mistune, nbconvert, parso, jedi, wcwidth, prompt-toolkit, pickleshare, pexpect, backcall, ipython, ipykernel, prometheus-client, notebook, json5, jupyterlab-server, jupyterlab
Running setup.py develop for jupyterlab
Successfully installed MarkupSafe-1.1.1 Send2Trash-1.5.0 attrs-19.1.0 backcall-0.1.0 bleach-3.1.0 decorator-4.4.0 defusedxml-0.6.0 entrypoints-0.3 ipykernel-5.1.1 ipython-7.7.0 ipython-genutils-0.2.0 jedi-0.14.1 jinja2-2.10.1 json5-0.8.5 jsonschema-3.0.2 jupyter-client-5.3.1 jupyter-core-4.5.0 jupyterlab jupyterlab-server-1.0.0 mistune-0.8.4 nbconvert-5.5.0 nbformat-4.4.0 notebook-6.0.0 pandocfilters-1.4.2 parso-0.5.1 pexpect-4.7.0 pickleshare-0.7.5 prometheus-client-0.7.1 prompt-toolkit-2.0.9 ptyprocess-0.6.0 pygments-2.4.2 pyrsistent-0.15.4 python-dateutil-2.8.0 pyzmq-18.0.2 six-1.12.0 terminado-0.8.2 testpath-0.4.2 tornado-6.0.3 traitlets-4.3.2 wcwidth-0.1.7 webencodings-0.5.1
$ pipenv shell
$ jupyter --version
jupyter core : 4.5.0
jupyter-notebook : 6.0.0
qtconsole : not installed
ipython : 7.7.0
ipykernel : 5.1.1
jupyter client : 5.3.1
jupyter lab : not installed
nbconvert : 5.5.0
ipywidgets : not installed
nbformat : 4.4.0
traitlets : 4.3.2
Try running pip install jupyterlab that fixed it for me
Here are the docs to get it running
https://jupyterlab.readthedocs.io/en/stable/getting_started/installation.html

yo webapp generator is installed but not recognized?

I try to install the webapp generator from yeoman but I have got this error :
You don't seem to have a generator with the name webapp installed.
after yo webapp :
npm install -g yo (works fine)
npm install -g generator-webapp (works fine)
yo webapp (does not work)
Here is the command lines (on Mac Os) :
MBP-de-Empon:yo Empon$ npm install -g yo
npm WARN deprecated npmconf#2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
/Users/Empon/npm/bin/yo-complete -> /Users/Empon/npm/lib/node_modules/yo/lib/completion/index.js
/Users/Empon/npm/bin/yo -> /Users/Empon/npm/lib/node_modules/yo/lib/cli.js
> yo#1.8.5 postinstall /Users/Empon/npm/lib/node_modules/yo
> yodoctor
Yeoman Doctor
Running sanity checks on your system
✔ Global configuration file is valid
✔ NODE_PATH matches the npm root
✔ Node.js version
✔ No .bowerrc file in home directory
✔ No .yo-rc.json file in home directory
✔ npm version
Everything looks all right!
/Users/Empon/npm/lib
└── yo#1.8.5
MBP-de-Empon:yo Empon$ npm install -g generator-webapp
npm WARN deprecated minimatch#2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
/Users/Empon/npm/lib
└── generator-webapp#2.4.1
MBP-de-Empon:yo Empon$ yo webapp
Error webapp
You don't seem to have a generator with the name webapp installed.
You can see available generators with npm search yeoman-generator and then install them with npm install [name].
To see the 14 registered generators run yo with the `--help` option.
MBP-de-Empon:yo Empon$
EDIT :
So yeoman searched at usr/local... and the webapp generator was downloaded at /Users/Empon/...
So I copied the content into a new folder with the same name : generator-webapp:
mkdir generator-webapp
cp -a /Users/Empon/npm/lib/node_modules/generator-webapp/. /usr/local/lib/node_modules/generator-webapp/
I tried again yo webapp, and I have got this error now :
So it looks good until this line :
events.js:141
throw er; // Unhandled 'error' event
and a new line appear on the Terminal and I was not being able to complete the sass options :
MBP-de-Empon:yo Empon$ yo webapp
_-----_ ╭──────────────────────────╮
| | │ 'Allo 'allo! Out of the │
|--(o)--| │ box I include HTML5 │
`---------´ │ Boilerplate, jQuery, and │
( _´U`_ ) │ a gulpfile to build your │
/___A___\ /│ app. │
| ~ | ╰──────────────────────────╯
__'.___.'__
´ ` |° ´ Y `
? Which additional features would you like to include? (Press <space> to select)
❯◉ Sass
◉ Bootstrap
◉ Modernizr
events.js:141
throw er; // Unhandled 'error' event
^
TypeError: this.env.adapter.prompt(...).then is not a function
at Base.prompt (/usr/local/lib/node_modules/generator-webapp/node_modules/yeoman-generator/lib/base.js:240:45)
at module.exports.generators.Base.extend.prompting (/usr/local/lib/node_modules/generator-webapp/app/index.js:102:17)
at Object.<anonymous> (/usr/local/lib/node_modules/generator-webapp/node_modules/yeoman-generator/lib/base.js:439:23)
at /usr/local/lib/node_modules/generator-webapp/node_modules/yeoman-generator/node_modules/run-async/index.js:25:25
at /usr/local/lib/node_modules/generator-webapp/node_modules/yeoman-generator/node_modules/run-async/index.js:24:19
at /usr/local/lib/node_modules/generator-webapp/node_modules/yeoman-generator/lib/base.js:440:9
at processImmediate [as _immediateCallback] (timers.js:383:17)
MBP-de-Empon:yo Empon$

Why doesn't rebar compile my files?

It's been a while since I've done any Erlang and I wanted to get back into it and use rebar to do it. I have a simple module-test combo that I've verified compiles okay, but when I try and compile it through rebar, nothing happens:
PS C:\Users\Magnus\Programming\binlog_parser_demo> rebar co -vv
DEBUG: Consult config file "c:/Users/Magnus/Programming/binlog_parser_demo/rebar.config"
DEBUG: Rebar location: "c:/Users/Magnus/Programming/rebar/rebar"
DEBUG: is_rel_dir(C:/Users/Magnus/Programming/binlog_parser_demo) -> false
DEBUG: Available deps: []
DEBUG: Missing deps : []
DEBUG: Plugins requested while processing C:/Users/Magnus/Programming/binlog_parser_demo: []
DEBUG: Predirs: []
==> binlog_parser_demo (compile)
DEBUG: Matched required ERTS version: 7.0 -> .*
DEBUG: Matched required OTP release: 18 -> .*
DEBUG: Min OTP version unconfigured
DEBUG: Postdirs: []
PS C:\Users\Magnus\Programming\binlog_parser_demo> ls -r
Directory: C:\Users\Magnus\Programming\binlog_parser_demo
Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 3/9 15:42 src
d---- 3/9 14:42 test
Directory: C:\Users\Magnus\Programming\binlog_parser_demo\src
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 3/9 14:43 2293 binlog_parser_demo.erl
Directory: C:\Users\Magnus\Programming\binlog_parser_demo\test
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 3/9 14:51 2662 binlog_parser_demo_tests.erl
What am I doing wrong? The file structure is what I got when I ran the template rebar create template=simplemod modid=binlog_parser_demo (and replaced the generated files with my old prewritten ones). I've verified that erlc is in the path and available and that erlc can compile the files okay when run independently.
You need to add a .app.src file to your src directory to define your application. The contents might look something like the following, but you'll need to adjust it to make it work properly for your case.
{application, binlog_parser, [
{description, "Binlog Parser"},
{vsn, "0.1"},
{registered, []},
{applications, [kernel, stdlib]}
]}.
See the rebar "Getting Started" docs for more information.

Resources