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
This occurs when the remote host is OSX, and maybe other flavors of BSD, which have env which do not support the -0 flag.
This seems to confuse jupyter about the cell's status (note [*]like it's still running)
as well as return code, though it does execute subsequent cells.
This occurs when the remote host is OSX, and maybe other flavors of BSD, which have
![image](https://user-images.githubusercontent.com/278431/145271788-d6066e39-aebb-4777-8a2d-534a71cd3cfe.png)
env
which do not support the-0
flag.This seems to confuse jupyter about the cell's status (note
[*]
like it's still running)as well as return code, though it does execute subsequent cells.
One fix (using gnu's env from brew) is:
brew install coreutils
echo PATH=/opt/homebrew/opt/coreutils/libexec/gnubin:/usr/bin:/bin:/usr/sbin:/sbin . ~/.ssh/environment
PermitUserEnvironment yes
from/etc/ssh/sshd_config
,or
sshd
will ignore this file.%login
cell in your notebook again to get a new sshd connection and realize the new environment changes.After this all is fine:
![image](https://user-images.githubusercontent.com/278431/145272640-127ca537-00fd-4688-af06-51ea571d6480.png)
Hopes this helps anyone else encountering the problem.
The text was updated successfully, but these errors were encountered: