Doesn't work properly in standard AWS EC2 Ubuntu bash

[rthickling]

In a vanilla AWS Ubuntu bash session, while jpterm installs nicely with pip install jpterm and runs seemingly fine.

However after creating a notebook, things go wrong quite quickly. It's not possible to execute a cell - ctrl-E and ctrl-R don't work and cause editing to stop properly functioning.

[davidbrochart]

Maybe these key bindings are intercepted by the shell? Do you know if other Textual applications work fine in this environment, for instance toolong?

[rthickling]

Tried toolong: works very well - ctrl-t, ctrl-f, ctrl-g all fine. I hit ctrl-e and ctrl-r (no function in toolong) and these don't do anything - but don't mess anything up as far as I can tell.

I tested AWS since it seems a great use-case. There's plenty of people who would love to use Jupyter but won't want to open browsers or, e.g. VSCode nor use Jupyter remotely while administering AWS.

I'm ssh'ing into AWS from an Ubuntu box using GNOME Terminal Version 3.49.92.

BTW jpterm seems a great project.

[davidbrochart]

Thanks for the kind words!
I guess I should try myself with an AWS free tier.

[davidbrochart]

I tried with a local SSH server, and it seems to work fine. What version of jpterm do you have installed?

[rthickling]

I did pip install jpterm
Which gave me jpterm-0.2.8.dist-info in my ~/.local/lib/python3.10/site-packages

[rthickling]

Tried with a fresh (local) Ubuntu 23.10 install and ssh to (the same) AWS box:

In a .ipynb file

• ctrl-r doesn't execute the cell nor launch a subsequent cell
• after ctrl-r can't backspace
• ctrl-e doesn't execute the cell (seems to do nothing)

[Daemoen]

I can reproduce this in fedora (WSL2) as well. I have tried multiple different terminal interfaces, but it doesn't work at all. It looks great, and I am excited to work with it, but right now, it's non functional. I can load notebooks, I can create notebooks, but no executions are possible.

---

 daemoen  systeminfo | findstr /B /C:"OS Name" /B /C:"OS Version"
OS Name:                   Microsoft Windows 11 Pro
OS Version:                10.0.22631 N/A Build 22631

 daemoen  scoop list wez*
Installed apps matching 'wez*':

Name    Version                  Source Updated             Info
----    -------                  ------ -------             ----
wezterm 20240203-110809-5046fc22 extras 2024-02-07 21:22:11

❯ pcat /etc/os-release
NAME="Fedora Remix for WSL"
VERSION="39"
ID=fedoraremixforwsl
ID_LIKE=fedora
VERSION_ID=39
PLATFORM_ID="platform:f39"
PRETTY_NAME="Fedora Remix for WSL"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:39"
HOME_URL="https://github.com/WhitewaterFoundry/Fedora-Remix-for-WSL"
SUPPORT_URL="https://github.com/WhitewaterFoundry/Fedora-Remix-for-WSL"
BUG_REPORT_URL="https://github.com/WhitewaterFoundry/Fedora-Remix-for-WSL/issues"
PRIVACY_POLICY_URL="https://github.com/WhitewaterFoundry/Fedora-Remix-for-WSL/blob/master/PRIVACY.md"
FEDORA_REMIX_VERSION=39.0.1

❯ zsh --version
zsh 5.9 (x86_64-pc-linux-gnu)

❯ brew list | ag python
python@3.11
python@3.12

❯ pipx list
venvs are in /home/daemoen/.local/share/pipx/venvs
apps are exposed on your $PATH at /home/daemoen/.local/bin
manual pages are exposed at /home/daemoen/.local/share/man
   package jpterm 0.2.11, installed using Python 3.12.2
    - jpterm

That's pretty much everything I could think of to include.

[Daemoen]

Ok, just realized I'm stupid, apparently. Need to connect to a server. I had figured that jpterm would launch a kernel. It doesn't appear to. @rthickling try starting your notebook/server manually, and then pointing jpterm at it via jpterm --server http://blahblah:blah. This worked for me.