13:21:52.732 [debug] Kernels for interpreter /bin/python are .jvsc74a57bd0e7370f93d1d0cde622a1f8e1c04877d8463912d04d973331ad4851f04de6915a./bin/python./bin/python.-m#ipykernel_launcher
13:21:52.732 [debug] Kernels for interpreter /opt/miniconda/bin/python are .jvsc74a57bd04c2b8563932708ac4f64e3bc4797ea8eb43fc7530baa7f01daadf5b46d7b1fd4./opt/miniconda/python./opt/miniconda/python.-m#ipykernel_launcher
13:21:52.912 [debug] KernelProvider switched kernel to id = .jvsc74a57bd0af59e808e2bb2d49f2aad3fcaa4e3b4707b54f609965d9d8e3585c2a4131334f.~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher
13:21:52.913 [debug] start the kernel, options.disableUI=true for ~/test.ipynb
13:21:52.916 [debug] Initialize notebook communications for editor ~/test.ipynb
13:21:52.916 [debug] Resolving notebook UI Comms (resolve) for ~/test.ipynb
13:21:52.916 [debug] initialize CommonMessageCoordinator
13:21:52.918 [debug] Registering commtarget jupyter.widget
13:21:52.918 [debug] IPyWidgetMessageDispatcher.initialize
13:21:52.919 [debug] Attempting to determine version of IPyWidgets
13:21:52.922 [debug] Controller selection change completed
13:21:52.922 [debug] Waiting for IPyWidgets version
13:21:52.922 [debug] Waiting for IPyWidgets version promise
13:21:52.961 [debug] Getting activated env variables, Class name = $a (started execution), Arg 1: "~", Arg 2: "~/.conda/envs/praxis_env/bin/python", Arg 3: undefined
13:21:52.961 [debug] Get Custom Env Variables, Class name = Ul (started execution), Arg 1: "~", Arg 2: "RunPythonCode"
13:21:52.962 [debug] Get Custom Env Variables, Class name = Ul, completed in 1ms, has a truthy return value, Arg 1: "~", Arg 2: "RunPythonCode"
13:21:52.963 [info] Starting Kernel startUsingPythonInterpreter, .jvsc74a57bd0af59e808e2bb2d49f2aad3fcaa4e3b4707b54f609965d9d8e3585c2a4131334f.~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher  (Python Path: ~/.conda/envs/praxis_env/bin/python, Conda, praxis_env, 3.9.18) for '~/test.ipynb' (disableUI=true)
13:21:52.964 [debug] Creating raw notebook for resource '~/test.ipynb'
13:21:52.985 [debug] Kernel Launcher. launch, Class name = Fv (started execution), Arg 1: "~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher", Arg 2: 60000, Arg 3: "~/test.ipynb", Arg 4: "~", Arg 5: ""
13:21:52.999 [debug] Getting activated env variables, Class name = $a (started execution), Arg 1: "~/test.ipynb", Arg 2: "~/.conda/envs/praxis_env/bin/python", Arg 3: undefined
13:21:52.999 [debug] Get Custom Env Variables, Class name = Ul (started execution), Arg 1: "~/test.ipynb", Arg 2: "RunPythonCode"
13:21:53.000 [debug] Get Custom Env Variables, Class name = Ul, completed in 1ms, has a truthy return value, Arg 1: "~/test.ipynb", Arg 2: "RunPythonCode"
13:21:53.398 [debug] Launching kernel in kernelProcess.ts, Class name = Lv (started execution), Arg 1: "~", Arg 2: ""
13:21:54.444 [debug] Conda file returned by Python Extension is conda
13:21:54.946 [debug] Got env vars with python ~/sandbox/bin/python, with env var count 52 in 2456ms.
PATH value is ~/sandbox/bin:~/sandbox/bin:~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:21:54.946 [debug] Prepend PATH with python bin for ~/sandbox/bin/python,
PATH value is ~/sandbox/bin:~/sandbox/bin:~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:21:54.947 [debug] Activated Env Variables for ~/sandbox/bin/python,
PATH value is ~/sandbox/bin:~/sandbox/bin:~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:21:54.947 [debug] Getting activated env variables, Class name = $a, completed in 2458ms, has a truthy return value, Arg 1: "~", Arg 2: "~/sandbox/bin/python", Arg 3: undefined
13:21:54.983 [info] Process Execution: ~/sandbox/bin/python -m pip list
13:21:55.638 [debug] Got env vars with python ~/.conda/envs/praxis_env/bin/python, with env var count 51 in 2677ms.
PATH value is ~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:21:55.638 [debug] Prepend PATH with python bin for ~/.conda/envs/praxis_env/bin/python,
PATH value is ~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:21:55.638 [debug] Activated Env Variables for ~/.conda/envs/praxis_env/bin/python,
PATH value is ~/.conda/envs/praxis_env/bin:~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:21:55.639 [debug] Getting activated env variables, Class name = $a, completed in 2678ms, has a truthy return value, Arg 1: "~", Arg 2: "~/.conda/envs/praxis_env/bin/python", Arg 3: undefined
13:21:55.664 [info] Process Execution: ~/.conda/envs/praxis_env/bin/python -m pip list
13:21:55.667 [debug] Got env vars with python ~/.conda/envs/praxis_env/bin/python, with env var count 51 in 2668ms.
PATH value is ~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:21:55.667 [debug] Prepend PATH with python bin for ~/.conda/envs/praxis_env/bin/python,
PATH value is ~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:21:55.667 [debug] Activated Env Variables for ~/.conda/envs/praxis_env/bin/python,
PATH value is ~/.conda/envs/praxis_env/bin:~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:21:55.667 [debug] Getting activated env variables, Class name = $a, completed in 2668ms, has a truthy return value, Arg 1: "~/test.ipynb", Arg 2: "~/.conda/envs/praxis_env/bin/python", Arg 3: undefined
13:21:55.688 [info] Process Execution: ~/.conda/envs/praxis_env/bin/python -c "import ipykernel; print(ipykernel.version); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.file)"
13:21:55.688 [debug] Kernel Env Variables for ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/temp/jupyter/kernels/pythonjvsc74a57bd0af59e808e2bb2d49f2aad3fcaa4e3b4707b54f609965d9d8e3585c2a4131334f/kernel.json, PATH value is ~/.conda/envs/praxis_env/bin:~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux
13:21:55.717 [info] Process Execution: ~/.conda/envs/praxis_env/bin/python -m ipykernel_launcher --f=~/.local/share/jupyter/runtime/kernel-v2-26886DAjW9XBx5DcW.json
> cwd: ~
13:21:55.717 [debug] Launching kernel in kernelProcess.ts, Class name = Lv, completed in 2319ms, has a truthy return value, Arg 1: "~", Arg 2: ""
13:21:56.621 [info] ipykernel version & path 6.26.0, ~/.conda/envs/praxis_env/lib/python3.9/site-packages/ipykernel/init.py for ~/.conda/envs/praxis_env/bin/python
13:21:59.535 [debug] KernelProcess output: NOTE: When using the ipython kernel entry point, Ctrl-C will not work.
To exit, you will have to explicitly quit this process, by either sending
"quit" from a client, or using Ctrl-\ in UNIX-like environments.
To read more about this, see https://github.com/ipython/ipython/issues/2049
To connect another client to this kernel, use:
--existing kernel-v2-26886DAjW9XBx5DcW.json
13:21:59.536 [debug] Kernel Output: To connect another client to this kernel, use: --existing kernel-v2-26886DAjW9XBx5DcW.json
13:21:59.644 [debug] Kernel Launcher. launch, Class name = Fv, completed in 6659ms, has a truthy return value, Arg 1: "~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher", Arg 2: 60000, Arg 3: "~/test.ipynb", Arg 4: "~", Arg 5: ""
13:21:59.660 [debug] Waiting for Raw Session to be ready in postStartRawSession
13:21:59.660 [debug] Waiting for Raw session to be ready, currently connected
13:21:59.661 [debug] Raw session connected
13:21:59.661 [debug] Waiting for Raw session to be ready for 30s
13:21:59.661 [debug] Waited for Raw session to be ready & got connected
13:21:59.661 [debug] Successfully waited for Raw Session to be ready in postStartRawSession
13:21:59.661 [debug] Kernel status before requesting kernel info and after ready is unknown
13:21:59.662 [debug] Sending request for kernelInfo
13:22:00.036 [info] End refreshing Kernel Picker<PHONE_NUMBER>662)
13:22:01.162 [debug] Did not get a response for requestKernelInfo
13:22:01.162 [debug] Sending request for kernelInfo
13:22:02.662 [debug] Did not get a response for requestKernelInfo
13:22:02.663 [warn] Didn't get response for requestKernelInfo after 3001ms.
13:22:02.669 [debug] Begin sendTelemetryForPythonKernelExecutable
13:22:02.669 [debug] Executing silently Code (unknown) = import sys as _VSCODE_sys\nprint(_VSCODE_sys.executable); del _VSCODE_sys
13:22:09.608 [debug] Updating cache with Local kernels startUsingLocalKernelSpec:'.praxis_env.~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher (interpreter id = ~/.conda/envs/praxis_env/bin/python)', Added = , Updated = , Removed =
13:22:17.730 [debug] Executing silently Code (completed) = import sys as _VSCODE_sys\nprint(_VSCODE_sys.executable); del _VSCODE_sys with 1 output(s)
13:22:17.731 [debug] End sendTelemetryForPythonKernelExecutable
13:22:17.731 [debug] Started running kernel initialization for ~/test.ipynb
13:22:17.732 [debug] Executing silently Code (idle) = try:\nimport ipywidgets as _VSCODE_ipywidgets\nprint("e976ee50-99ed-4aba-9b6b-9dcd5634d07d:IPy
13:22:17.906 [debug] Executing silently Code (completed) = try:\nimport ipywidgets as _VSCODE_ipywidgets\nprint("e976ee50-99ed-4aba-9b6b-9dcd5634d07d:IPy with 1 output(s)
13:22:17.906 [debug] Determined IPyWidgets Version as 8 and event fired
13:22:17.906 [debug] Version of IPyWidgets 8 determined after 24.987s
13:22:17.911 [debug] Executing silently Code (idle) = import os as _VSCODE_os\nimport sys as _VSCODE_sys\n%cd "/~"\nif _VSCODE_os.getcwd() not in
13:22:17.964 [debug] Executing silently Code (completed) = import os as _VSCODE_os\nimport sys as _VSCODE_sys\n%cd "/~"\nif _VSCODE_os.getcwd() not in with 1 output(s)
13:22:17.964 [debug] Executing silently Code (idle) = import os\nos.environ['PATH']='/usr/local/texlive/2022/bin/x86_64-linux:' + os.environ['PATH']
13:22:17.973 [debug] Executing silently Code (completed) = import os\nos.environ['PATH']='/usr/local/texlive/2022/bin/x86_64-linux:' + os.environ['PATH'] with 0 output(s)
13:22:17.973 [debug] Requesting Kernel info
13:22:17.974 [debug] Got Kernel info
13:22:17.974 [debug] End running kernel initialization, now waiting for idle
13:22:17.975 [debug] Waiting for 60000ms idle on (kernel): d5448347-0106-46ee-b9c1-5e912171d6a9 -> idle
13:22:17.975 [debug] Finished waiting for idle on (kernel): d5448347-0106-46ee-b9c1-5e912171d6a9 -> idle
13:22:17.975 [debug] End running kernel initialization, session is idle
13:22:17.978 [debug] IPyWidgetScriptSource.initialize
13:22:17.979 [debug] IPyWidgetMessageDispatcher.initialize
13:22:17.981 [debug] getDataDirsImpl, Class name = ff (started execution), Arg 1: "~/test.ipynb", Arg 2: "~/.conda/envs/praxis_env/bin/python"
13:22:17.982 [debug] Get Custom Env Variables, Class name = Ul (started execution), Arg 1: undefined, Arg 2: "RunPythonCode"
13:22:17.983 [debug] Get Custom Env Variables, Class name = Ul, completed in 1ms, has a truthy return value, Arg 1: undefined, Arg 2: "RunPythonCode"
13:22:17.983 [debug] Jupyter Paths :
13:22:18.008 [info] Process Execution: ~/.conda/envs/praxis_env/bin/python ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/pythonFiles/printJupyterDataDir.py
13:22:18.097 [debug] getDataDirsImpl, Class name = ff, completed in 116ms, has a truthy return value, Arg 1: "~/test.ipynb", Arg 2: "~/.conda/envs/praxis_env/bin/python"
13:22:18.589 [debug] IPyWidgetMessageDispatcher.initialize
13:22:18.590 [debug] Web view is ready to receive widget messages
13:22:18.726 [debug] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
13:22:18.726 [debug] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
13:22:18.737 [debug] IPyWidgetMessageDispatcher.initialize
13:22:18.737 [debug] IPyWidgetMessageDispatcher.initialize
13:22:18.744 [debug] Widget Message: data-base-url set to https://vscode-remote%2Bssh-002dremote-002bpraxis.vscode-resource.vscode-cdn.net~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/temp/scripts/ad52e412420ea2a6c522dbfacb04928f3ea2fd56dabce877e2e13497b6ebdf6f/jupyter
13:22:18.744 [debug] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
13:22:18.744 [debug] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
13:22:18.744 [debug] Widget Message: data-base-url set to https://vscode-remote%2Bssh-002dremote-002bpraxis.vscode-resource.vscode-cdn.net~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/temp/scripts/ad52e412420ea2a6c522dbfacb04928f3ea2fd56dabce877e2e13497b6ebdf6f/jupyter
13:23:30.849 [info] Handle Execution of Cells 0 for ~/test.ipynb
13:23:30.854 [debug] start the kernel, options.disableUI=false for ~/test.ipynb
13:23:30.862 [debug] Execution Request Sent to Kernel for cell 0
13:23:30.877 [debug] Start cell 0 execution @<PHONE_NUMBER>876 (clear output)
13:23:30.878 [info] Kernel acknowledged execution of cell 0 @<PHONE_NUMBER>876
13:23:30.886 [info] End cell 0 execution @<PHONE_NUMBER>885, started @<PHONE_NUMBER>876, elapsed time = 0.009s
13:23:30.887 [debug] Cell 0 executed with state Success
13:24:52.417 [debug] Jupyter completion time: 848
13:24:53.378 [debug] Jupyter completion time: 23
13:24:54.075 [info] Handle Execution of Cells 1 for ~/test.ipynb
13:24:54.083 [debug] start the kernel, options.disableUI=false for ~/test.ipynb
13:24:54.086 [debug] Execution Request Sent to Kernel for cell 1
13:24:54.096 [debug] Start cell 1 execution @<PHONE_NUMBER>095 (clear output)
13:24:54.096 [info] Kernel acknowledged execution of cell 1 @<PHONE_NUMBER>095
13:24:54.101 [info] End cell 1 execution @<PHONE_NUMBER>101, started @<PHONE_NUMBER>095, elapsed time = 0.006s
13:24:54.102 [debug] Cell 1 executed with state Success
13:24:57.429 [debug] Disposing request as the cell was deleted ~/test.ipynb
13:24:57.430 [debug] Disposing request as the cell was deleted ~/test.ipynb
13:24:57.431 [info] Dispose Kernel '~/test.ipynb' associated with '~/test.ipynb'
13:24:57.432 [debug] Cancel pending cells
13:24:57.434 [debug] Shutdown session d5448347-0106-46ee-b9c1-5e912171d6a9, .jvsc74a57bd0af59e808e2bb2d49f2aad3fcaa4e3b4707b54f609965d9d8e3585c2a4131334f.~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher - start called from Error:
at Wv.shutdown (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:24:99398)
at Wv.disposeAsync (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:24:98866)
at ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:17:212646
at Ng.dispose (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:17:212860)
at Jg.disposeOldKernel (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:17:205145)
at Jg. (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:17:203478)
at c.y (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at c.z (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1972)
at c.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:2188)
at Dc. (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:2:2351987)
at c.y (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at c.z (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1972)
at c.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:2188)
at t.$acceptDocumentAndEditorsDelta (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:127:95776)
at n.S (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:134:10836)
at n.Q (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:134:10602)
at n.M (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:134:9686)
at n.L (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:134:8901)
at h.value (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:134:7565)
at c.y (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at c.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at d.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:96:14047)
at h.value (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:153:7918)
at c.y (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at c.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at d.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:96:14047)
at s.z (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:96:17112)
at h.value (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:96:15564)
at c.y (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at c.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at h.acceptChunk (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:96:11821)
at h.value (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:96:11108)
at c.y (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at c.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at c.z (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:150:19388)
13:24:57.435 [info] Dispose Kernel process 27304.
13:24:57.478 [debug] Kernel got disposed, hence there is no longer a kernel associated with ~/test.ipynb
13:24:57.483 [debug] Cancel executions after closing notebook ~/test.ipynb
13:24:57.483 [debug] Cancel pending cells
13:24:57.483 [debug] Cancel executions after closing notebook ~/test.ipynb
13:24:57.489 [debug] Shutdown session d5448347-0106-46ee-b9c1-5e912171d6a9, .jvsc74a57bd0af59e808e2bb2d49f2aad3fcaa4e3b4707b54f609965d9d8e3585c2a4131334f.~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher - shutdown complete
13:24:57.529 [debug] Disposed Kernel process 27304.
13:24:57.542 [debug] KernelProcess Exited, Exit Code - undefined
13:30:47.966 [info] Start refreshing Interpreter Kernel Picker
13:30:47.968 [info] Start refreshing Kernel Picker<PHONE_NUMBER>968)
13:30:47.977 [debug] Initialize notebook communications for editor ~/test.ipynb
13:30:47.977 [debug] Resolving notebook UI Comms (resolve) for ~/test.ipynb
13:30:47.978 [debug] initialize CommonMessageCoordinator
13:30:47.979 [debug] IPyWidgetMessageDispatcher.initialize
13:30:47.980 [debug] Attempting to determine version of IPyWidgets
13:30:47.991 [debug] Preferred Remote kernel for ~/test.ipynb is undefined
13:30:48.167 [debug] Python API env change detected, add => '/bin/python3.6'
13:30:48.212 [debug] Search for KernelSpecs in Interpreter /usr/bin/python
13:30:48.213 [debug] Search for KernelSpecs in Interpreter /usr/bin/python
13:30:48.213 [debug] Search for KernelSpecs in Interpreter /bin/python
13:30:48.214 [debug] Search for KernelSpecs in Interpreter /usr/bin/python
13:30:48.214 [debug] Search for KernelSpecs in Interpreter /bin/python
13:30:48.214 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:48.215 [debug] Kernel Spec Root Paths, /usr/share/jupyter/kernels, /usr/local/share/jupyter/kernels, ~/.local/share/jupyter/kernels
13:30:48.220 [debug] Kernels for interpreter /usr/bin/python are
13:30:48.220 [debug] Kernels for interpreter /usr/bin/python are
13:30:48.221 [debug] Kernels for interpreter /bin/python are .jvsc74a57bd0e7370f93d1d0cde622a1f8e1c04877d8463912d04d973331ad4851f04de6915a./bin/python./bin/python.-m#ipykernel_launcher
13:30:48.221 [debug] Kernels for interpreter /bin/python are
13:30:48.221 [debug] Kernels for interpreter /usr/bin/python are .jvsc74a57bd0767d51c1340bd893661ea55ea3124f6de3c7a262a8b4abca0554b478b1e2ff90./usr/bin/python./usr/bin/python.-m#ipykernel_launcher
13:30:48.225 [debug] Kernels for interpreter /opt/miniconda/bin/python are .jvsc74a57bd04c2b8563932708ac4f64e3bc4797ea8eb43fc7530baa7f01daadf5b46d7b1fd4./opt/miniconda/python./opt/miniconda/python.-m#ipykernel_launcher
13:30:48.231 [debug] KernelProvider switched kernel to id = .jvsc74a57bd0af59e808e2bb2d49f2aad3fcaa4e3b4707b54f609965d9d8e3585c2a4131334f.~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher
13:30:48.231 [debug] start the kernel, options.disableUI=true for ~/test.ipynb
13:30:48.232 [debug] Waiting for IPyWidgets version
13:30:48.232 [debug] Waiting for IPyWidgets version promise
13:30:48.233 [debug] Initialize notebook communications for editor ~/test.ipynb
13:30:48.233 [debug] Resolving notebook UI Comms (resolve) for ~/test.ipynb
13:30:48.233 [debug] initialize CommonMessageCoordinator
13:30:48.233 [debug] Registering commtarget jupyter.widget
13:30:48.233 [debug] IPyWidgetMessageDispatcher.initialize
13:30:48.233 [debug] Attempting to determine version of IPyWidgets
13:30:48.234 [debug] Controller selection change completed
13:30:48.235 [debug] Waiting for IPyWidgets version
13:30:48.235 [debug] Waiting for IPyWidgets version promise
13:30:48.235 [info] Starting Kernel startUsingPythonInterpreter, .jvsc74a57bd0af59e808e2bb2d49f2aad3fcaa4e3b4707b54f609965d9d8e3585c2a4131334f.~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher  (Python Path: ~/.conda/envs/praxis_env/bin/python, Conda, praxis_env, 3.9.18) for '~/test.ipynb' (disableUI=true)
13:30:48.235 [debug] Creating raw notebook for resource '~/test.ipynb'
13:30:48.240 [debug] Getting activated env variables, Class name = $a (started execution), Arg 1: "~", Arg 2: "~/.conda/envs/praxis_env/bin/python", Arg 3: undefined
13:30:48.241 [debug] Get Custom Env Variables, Class name = Ul (started execution), Arg 1: "~", Arg 2: "RunPythonCode"
13:30:48.242 [debug] Get Custom Env Variables, Class name = Ul, completed in 2ms, has a truthy return value, Arg 1: "~", Arg 2: "RunPythonCode"
13:30:48.242 [debug] Got env vars with python ~/.conda/envs/praxis_env/bin/python, with env var count 51 in 2ms.
PATH value is ~/.conda/envs/praxis_env/bin:~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:30:48.242 [debug] Prepend PATH with python bin for ~/.conda/envs/praxis_env/bin/python,
PATH value is ~/.conda/envs/praxis_env/bin:~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:30:48.243 [debug] Activated Env Variables for ~/.conda/envs/praxis_env/bin/python,
PATH value is ~/.conda/envs/praxis_env/bin:~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:30:48.243 [debug] Getting activated env variables, Class name = $a, completed in 3ms, has a truthy return value, Arg 1: "~", Arg 2: "~/.conda/envs/praxis_env/bin/python", Arg 3: undefined
13:30:48.281 [info] Process Execution: ~/.conda/envs/praxis_env/bin/python -m pip list
13:30:48.284 [debug] Kernel Launcher. launch, Class name = Fv (started execution), Arg 1: "~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher", Arg 2: 60000, Arg 3: "~/test.ipynb", Arg 4: "~", Arg 5: ""
13:30:48.289 [debug] Getting activated env variables, Class name = $a (started execution), Arg 1: "~/test.ipynb", Arg 2: "~/.conda/envs/praxis_env/bin/python", Arg 3: undefined
13:30:48.289 [debug] Get Custom Env Variables, Class name = Ul (started execution), Arg 1: "~/test.ipynb", Arg 2: "RunPythonCode"
13:30:48.290 [debug] Get Custom Env Variables, Class name = Ul, completed in 1ms, has a truthy return value, Arg 1: "~/test.ipynb", Arg 2: "RunPythonCode"
13:30:48.290 [debug] Got env vars with python ~/.conda/envs/praxis_env/bin/python, with env var count 51 in 1ms.
PATH value is ~/.conda/envs/praxis_env/bin:~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:30:48.290 [debug] Prepend PATH with python bin for ~/.conda/envs/praxis_env/bin/python,
PATH value is ~/.conda/envs/praxis_env/bin:~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:30:48.290 [debug] Activated Env Variables for ~/.conda/envs/praxis_env/bin/python,
PATH value is ~/.conda/envs/praxis_env/bin:~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux and
Path value is undefined
13:30:48.290 [debug] Getting activated env variables, Class name = $a, completed in 1ms, has a truthy return value, Arg 1: "~/test.ipynb", Arg 2: "~/.conda/envs/praxis_env/bin/python", Arg 3: undefined
13:30:48.323 [info] Process Execution: ~/.conda/envs/praxis_env/bin/python -c "import ipykernel; print(ipykernel.version); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.file)"
13:30:48.331 [debug] Python API env change detected, update => '/bin/python3.6'
13:30:48.352 [debug] Python API env change detected, update => '/bin/python3.6'
13:30:48.361 [debug] Search for KernelSpecs in Interpreter /bin/python3.6
13:30:48.362 [debug] Search for KernelSpecs in Interpreter /usr/bin/python
13:30:48.362 [debug] Search for KernelSpecs in Interpreter /bin/python
13:30:48.362 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:48.362 [debug] Search for KernelSpecs in Interpreter /usr/bin/python
13:30:48.363 [debug] Search for KernelSpecs in Interpreter /bin/python
13:30:48.363 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:48.364 [debug] Search for KernelSpecs in Interpreter /usr/bin/python
13:30:48.364 [debug] Search for KernelSpecs in Interpreter /bin/python
13:30:48.365 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:48.365 [debug] Full interpreter list is length: 7, /usr/bin/python::Unknown:/usr/bin/python, /bin/python::Unknown:/bin/python, ~/.conda/envs/praxis_env/bin/python:praxis_env:Conda:~/.conda/envs/praxis_env/bin/python, /opt/miniconda/bin/python:base:Conda:/opt/miniconda/bin/python, ~/sandbox/bin/python:sandbox:Venv:~/sandbox/bin/python, /usr/bin/python3.6::Unknown:/usr/bin/python3.6, /bin/python3.6::Unknown:/bin/python3.6
13:30:48.377 [debug] Kernels for interpreter /bin/python3.6 are .jvsc74a57bd0db0f6cbdde3eb805f0a229b988d6bd72d452c42e640dd9958b4355934ec01bf5./bin/python3.6./bin/python3.6.-m#ipykernel_launcher
13:30:48.377 [debug] Kernels for interpreter /usr/bin/python are
13:30:48.377 [debug] Kernels for interpreter /bin/python are
13:30:48.377 [debug] Kernels for interpreter /opt/miniconda/bin/python are
13:30:48.378 [debug] Kernels for interpreter /opt/miniconda/bin/python are
13:30:48.378 [debug] Kernels for interpreter /usr/bin/python are
13:30:48.378 [debug] Kernels for interpreter /opt/miniconda/bin/python are .jvsc74a57bd04c2b8563932708ac4f64e3bc4797ea8eb43fc7530baa7f01daadf5b46d7b1fd4./opt/miniconda/python./opt/miniconda/python.-m#ipykernel_launcher
13:30:48.378 [debug] Kernels for interpreter /bin/python are
13:30:48.378 [debug] Kernels for interpreter /usr/bin/python are .jvsc74a57bd0767d51c1340bd893661ea55ea3124f6de3c7a262a8b4abca0554b478b1e2ff90./usr/bin/python./usr/bin/python.-m#ipykernel_launcher
13:30:48.378 [debug] Kernels for interpreter /bin/python are .jvsc74a57bd0e7370f93d1d0cde622a1f8e1c04877d8463912d04d973331ad4851f04de6915a./bin/python./bin/python.-m#ipykernel_launcher
13:30:48.379 [debug] Launching kernel in kernelProcess.ts, Class name = Lv (started execution), Arg 1: "~", Arg 2: ""
13:30:48.387 [debug] Kernel Env Variables for ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/temp/jupyter/kernels/pythonjvsc74a57bd0af59e808e2bb2d49f2aad3fcaa4e3b4707b54f609965d9d8e3585c2a4131334f/kernel.json, PATH value is ~/.conda/envs/praxis_env/bin:~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/local/bin:~/.vscode-server/bin/b3e4e68a0bc097f0ae7907b217c1119af9e03435/bin/remote-cli:~/.conda/envs/bin:/opt/python-3.9.12/bin:/opt/python-3.9.12/bin:~/.conda/envs/bin:~/.conda/envs/praxis_env/bin:/opt/miniconda/condabin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/usr/local/nz/bin:/usr/local/nz/bin64:/usr/local/texlive/2022/bin/x86_64-linux:/usr/local/nz/bin:/usr/local/nz/bin64:~/.fzf/bin:/usr/local/texlive/2022/bin/x86_64-linux
13:30:48.420 [info] Process Execution: ~/.conda/envs/praxis_env/bin/python -m ipykernel_launcher --f=~/.local/share/jupyter/runtime/kernel-v2-26886wFaeSj1SQeKP.json
> cwd: ~
13:30:48.421 [debug] Launching kernel in kernelProcess.ts, Class name = Lv, completed in 41ms, has a truthy return value, Arg 1: "~", Arg 2: ""
13:30:48.457 [debug] Search for KernelSpecs in Interpreter /usr/bin/python
13:30:48.457 [debug] Search for KernelSpecs in Interpreter /bin/python
13:30:48.457 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:48.481 [debug] Kernels for interpreter /usr/bin/python are .jvsc74a57bd0767d51c1340bd893661ea55ea3124f6de3c7a262a8b4abca0554b478b1e2ff90./usr/bin/python./usr/bin/python.-m#ipykernel_launcher
13:30:48.481 [debug] Kernels for interpreter /bin/python are .jvsc74a57bd0e7370f93d1d0cde622a1f8e1c04877d8463912d04d973331ad4851f04de6915a./bin/python./bin/python.-m#ipykernel_launcher
13:30:48.481 [debug] Kernels for interpreter /opt/miniconda/bin/python are .jvsc74a57bd04c2b8563932708ac4f64e3bc4797ea8eb43fc7530baa7f01daadf5b46d7b1fd4./opt/miniconda/python./opt/miniconda/python.-m#ipykernel_launcher
13:30:48.678 [debug] Python API env change detected, update => '/usr/bin/python3.6m'
13:30:48.694 [debug] Python API env change detected, update => '/usr/bin/python3.6m'
13:30:48.700 [debug] Search for KernelSpecs in Interpreter /usr/bin/python3.6m
13:30:48.700 [debug] Search for KernelSpecs in Interpreter /usr/bin/python
13:30:48.700 [debug] Search for KernelSpecs in Interpreter /bin/python
13:30:48.700 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:48.701 [debug] Search for KernelSpecs in Interpreter /usr/bin/python
13:30:48.701 [debug] Search for KernelSpecs in Interpreter /bin/python
13:30:48.701 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:48.702 [debug] Search for KernelSpecs in Interpreter /usr/bin/python
13:30:48.702 [debug] Search for KernelSpecs in Interpreter /bin/python
13:30:48.702 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:48.703 [debug] Full interpreter list is length: 7, /usr/bin/python::Unknown:/usr/bin/python, /bin/python::Unknown:/bin/python, ~/.conda/envs/praxis_env/bin/python:praxis_env:Conda:~/.conda/envs/praxis_env/bin/python, /opt/miniconda/bin/python:base:Conda:/opt/miniconda/bin/python, ~/sandbox/bin/python:sandbox:Venv:~/sandbox/bin/python, /usr/bin/python3.6m::Unknown:/usr/bin/python3.6m, /bin/python3.6::Unknown:/bin/python3.6
13:30:48.706 [debug] Kernels for interpreter /usr/bin/python3.6m are .jvsc74a57bd0fdb70176b9f68a63fad060439e1eecc9dfd60edecc2378a4464637b9f14b2c93./usr/bin/python3.6m./usr/bin/python3.6m.-m#ipykernel_launcher
13:30:48.706 [debug] Kernels for interpreter /usr/bin/python are
13:30:48.707 [debug] Kernels for interpreter /bin/python are
13:30:48.707 [debug] Kernels for interpreter /opt/miniconda/bin/python are
13:30:48.707 [debug] Kernels for interpreter /usr/bin/python are
13:30:48.707 [debug] Kernels for interpreter /bin/python are .jvsc74a57bd0e7370f93d1d0cde622a1f8e1c04877d8463912d04d973331ad4851f04de6915a./bin/python./bin/python.-m#ipykernel_launcher
13:30:48.707 [debug] Kernels for interpreter /bin/python are
13:30:48.707 [debug] Kernels for interpreter /opt/miniconda/bin/python are
13:30:48.707 [debug] Kernels for interpreter /usr/bin/python are .jvsc74a57bd0767d51c1340bd893661ea55ea3124f6de3c7a262a8b4abca0554b478b1e2ff90./usr/bin/python./usr/bin/python.-m#ipykernel_launcher
13:30:48.707 [debug] Kernels for interpreter /opt/miniconda/bin/python are .jvsc74a57bd04c2b8563932708ac4f64e3bc4797ea8eb43fc7530baa7f01daadf5b46d7b1fd4./opt/miniconda/python./opt/miniconda/python.-m#ipykernel_launcher
13:30:49.085 [info] ipykernel version & path 6.26.0, ~/.conda/envs/praxis_env/lib/python3.9/site-packages/ipykernel/init.py for ~/.conda/envs/praxis_env/bin/python
13:30:49.497 [debug] Attempting to determine version of IPyWidgets
13:30:49.497 [debug] Attempting to determine version of IPyWidgets
13:30:49.497 [debug] Waiting for IPyWidgets version
13:30:49.497 [debug] Waiting for IPyWidgets version promise
13:30:49.497 [debug] Waiting for IPyWidgets version
13:30:49.497 [debug] Waiting for IPyWidgets version promise
13:30:49.516 [debug] Python API env change detected, update => '/bin/python'
13:30:49.517 [debug] Python API env change detected, update => '/bin/python3.6'
13:30:49.518 [debug] Python API env change detected, update => '/usr/bin/python'
13:30:49.520 [debug] Python API env change detected, update => '/usr/bin/python3.6m'
13:30:49.521 [debug] Python API env change detected, update => '~/.conda/envs/praxis_env/bin/python'
13:30:49.524 [debug] Python API env change detected, update => '~/sandbox/bin/python'
13:30:49.525 [debug] Python API env change detected, update => '/opt/miniconda/bin/python'
13:30:49.540 [debug] Search for KernelSpecs in Interpreter /bin/python
13:30:49.540 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:49.541 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:49.542 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:49.542 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:49.550 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:49.561 [debug] Search for KernelSpecs in Interpreter /opt/miniconda/bin/python
13:30:49.562 [debug] Full interpreter list is length: 7, /usr/bin/python::Unknown:/usr/bin/python, /bin/python::Unknown:/bin/python, ~/.conda/envs/praxis_env/bin/python:praxis_env:Conda:~/.conda/envs/praxis_env/bin/python, /opt/miniconda/bin/python:base:Conda:/opt/miniconda/bin/python, ~/sandbox/bin/python:sandbox:Venv:~/sandbox/bin/python, /usr/bin/python3.6m::Unknown:/usr/bin/python3.6m, /bin/python3.6::Unknown:/bin/python3.6
13:30:49.562 [debug] Refreshed Environments
13:30:49.578 [debug] Kernels for interpreter /bin/python are .jvsc74a57bd0e7370f93d1d0cde622a1f8e1c04877d8463912d04d973331ad4851f04de6915a./bin/python./bin/python.-m#ipykernel_launcher
13:30:49.578 [debug] Kernels for interpreter /opt/miniconda/bin/python are
13:30:49.578 [debug] Kernels for interpreter /opt/miniconda/bin/python are
13:30:49.578 [debug] Kernels for interpreter /opt/miniconda/bin/python are
13:30:49.578 [debug] Kernels for interpreter /opt/miniconda/bin/python are
13:30:49.578 [debug] Kernels for interpreter /opt/miniconda/bin/python are
13:30:49.579 [debug] Kernels for interpreter /opt/miniconda/bin/python are .jvsc74a57bd04c2b8563932708ac4f64e3bc4797ea8eb43fc7530baa7f01daadf5b46d7b1fd4./opt/miniconda/python./opt/miniconda/python.-m#ipykernel_launcher
13:30:50.706 [info] Handle Execution of Cells 0 for ~/test.ipynb
13:30:50.708 [debug] start the kernel, options.disableUI=false for ~/test.ipynb
13:30:51.719 [debug] KernelProcess output: NOTE: When using the ipython kernel entry point, Ctrl-C will not work.
To exit, you will have to explicitly quit this process, by either sending
"quit" from a client, or using Ctrl-\ in UNIX-like environments.
To read more about this, see https://github.com/ipython/ipython/issues/2049
To connect another client to this kernel, use:
--existing kernel-v2-26886wFaeSj1SQeKP.json
13:30:51.721 [debug] Kernel Output: To connect another client to this kernel, use: --existing kernel-v2-26886wFaeSj1SQeKP.json
13:30:51.908 [debug] Kernel Launcher. launch, Class name = Fv, completed in 3623ms, has a truthy return value, Arg 1: "~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher", Arg 2: 60000, Arg 3: "~/test.ipynb", Arg 4: "~", Arg 5: ""
13:30:51.922 [debug] Waiting for Raw Session to be ready in postStartRawSession
13:30:51.922 [debug] Waiting for Raw session to be ready, currently connected
13:30:51.922 [debug] Raw session connected
13:30:51.922 [debug] Waiting for Raw session to be ready for 30s
13:30:51.923 [debug] Waited for Raw session to be ready & got connected
13:30:51.923 [debug] Successfully waited for Raw Session to be ready in postStartRawSession
13:30:51.923 [debug] Kernel status before requesting kernel info and after ready is unknown
13:30:51.923 [debug] Sending request for kernelInfo
13:30:51.934 [debug] Got response for requestKernelInfo
13:30:51.934 [debug] Successfully completed postStartRawSession
13:30:51.939 [debug] Begin sendTelemetryForPythonKernelExecutable
13:30:51.939 [debug] Executing silently Code (idle) = import sys as _VSCODE_sys\nprint(_VSCODE_sys.executable); del _VSCODE_sys
13:30:51.957 [debug] Executing silently Code (completed) = import sys as _VSCODE_sys\nprint(_VSCODE_sys.executable); del _VSCODE_sys with 1 output(s)
13:30:51.958 [debug] End sendTelemetryForPythonKernelExecutable
13:30:51.958 [debug] Started running kernel initialization for ~/test.ipynb
13:30:51.959 [debug] Executing silently Code (idle) = try:\nimport ipywidgets as _VSCODE_ipywidgets\nprint("e976ee50-99ed-4aba-9b6b-9dcd5634d07d:IPy
13:30:52.158 [debug] Executing silently Code (completed) = try:\nimport ipywidgets as _VSCODE_ipywidgets\nprint("e976ee50-99ed-4aba-9b6b-9dcd5634d07d:IPy with 1 output(s)
13:30:52.158 [debug] Determined IPyWidgets Version as 8 and event fired
13:30:52.159 [debug] Version of IPyWidgets 8 determined after 4.179s
13:30:52.159 [debug] Version of IPyWidgets 8 determined after 2.662s
13:30:52.159 [debug] Version of IPyWidgets 8 determined after 3.926s
13:30:52.160 [debug] Version of IPyWidgets 8 determined after 2.663s
13:30:52.163 [debug] Executing silently Code (idle) = import os as _VSCODE_os\nimport sys as _VSCODE_sys\n%cd "/~"\nif _VSCODE_os.getcwd() not in
13:30:52.185 [debug] Executing silently Code (completed) = import os as _VSCODE_os\nimport sys as _VSCODE_sys\n%cd "/~"\nif _VSCODE_os.getcwd() not in with 1 output(s)
13:30:52.185 [debug] Executing silently Code (idle) = import os\nos.environ['PATH']='/usr/local/texlive/2022/bin/x86_64-linux:' + os.environ['PATH']
13:30:52.192 [debug] Executing silently Code (completed) = import os\nos.environ['PATH']='/usr/local/texlive/2022/bin/x86_64-linux:' + os.environ['PATH'] with 0 output(s)
13:30:52.192 [debug] Requesting Kernel info
13:30:52.193 [debug] Got Kernel info
13:30:52.193 [debug] End running kernel initialization, now waiting for idle
13:30:52.193 [debug] Waiting for 60000ms idle on (kernel): b764dc3d-ea49-4705-ba5a-7077f5c76ecf -> idle
13:30:52.193 [debug] Finished waiting for idle on (kernel): b764dc3d-ea49-4705-ba5a-7077f5c76ecf -> idle
13:30:52.193 [debug] End running kernel initialization, session is idle
13:30:52.194 [debug] IPyWidgetMessageDispatcher.initialize
13:30:52.195 [debug] IPyWidgetScriptSource.initialize
13:30:52.198 [debug] Execution Request Sent to Kernel for cell 0
13:30:52.769 [debug] Start cell 0 execution @<PHONE_NUMBER>768 (clear output)
13:30:52.769 [info] Kernel acknowledged execution of cell 0 @<PHONE_NUMBER>768
13:30:52.773 [info] End cell 0 execution @<PHONE_NUMBER>772, started @<PHONE_NUMBER>768, elapsed time = 0.004s
13:30:52.774 [debug] Cell 0 executed with state Success
13:30:52.877 [debug] IPyWidgetMessageDispatcher.initialize
13:30:52.877 [debug] Web view is ready to receive widget messages
13:30:52.877 [debug] IPyWidgetMessageDispatcher.initialize
13:30:52.877 [debug] Web view is ready to receive widget messages
13:30:53.025 [debug] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
13:30:53.025 [debug] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
13:30:53.026 [debug] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
13:30:53.026 [debug] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
13:30:53.038 [debug] IPyWidgetMessageDispatcher.initialize
13:30:53.038 [debug] IPyWidgetMessageDispatcher.initialize
13:30:53.054 [debug] IPyWidgetMessageDispatcher.initialize
13:30:53.054 [debug] IPyWidgetMessageDispatcher.initialize
13:30:53.054 [debug] Widget Message: data-base-url set to https://vscode-remote%2Bssh-002dremote-002bpraxis.vscode-resource.vscode-cdn.net~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/temp/scripts/ad52e412420ea2a6c522dbfacb04928f3ea2fd56dabce877e2e13497b6ebdf6f/jupyter
13:30:53.054 [debug] Widget Message: data-base-url set to https://vscode-remote%2Bssh-002dremote-002bpraxis.vscode-resource.vscode-cdn.net~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/temp/scripts/ad52e412420ea2a6c522dbfacb04928f3ea2fd56dabce877e2e13497b6ebdf6f/jupyter
13:30:53.055 [debug] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
13:30:53.055 [debug] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
13:30:53.055 [debug] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
13:30:53.055 [debug] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
13:30:53.055 [debug] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
13:30:53.055 [debug] Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
13:30:53.055 [debug] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
13:30:53.055 [debug] Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
13:30:53.055 [debug] Widget Message: data-base-url set to https://vscode-remote%2Bssh-002dremote-002bpraxis.vscode-resource.vscode-cdn.net~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/temp/scripts/ad52e412420ea2a6c522dbfacb04928f3ea2fd56dabce877e2e13497b6ebdf6f/jupyter
13:30:53.055 [debug] Widget Message: data-base-url set to https://vscode-remote%2Bssh-002dremote-002bpraxis.vscode-resource.vscode-cdn.net~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/temp/scripts/ad52e412420ea2a6c522dbfacb04928f3ea2fd56dabce877e2e13497b6ebdf6f/jupyter
13:30:55.923 [info] End refreshing Kernel Picker<PHONE_NUMBER>968)
13:30:56.183 [debug] Jupyter completion time: 96
13:30:57.854 [debug] Jupyter completion time: 110
13:30:59.529 [debug] Jupyter completion time: 41
13:31:00.073 [debug] Jupyter completion time: 39
13:31:00.185 [debug] Jupyter completion time: 38
13:31:01.344 [debug] Jupyter completion time: 36
13:31:03.264 [debug] Jupyter completion time: 106
13:31:03.982 [debug] Jupyter completion time: 15
13:31:04.579 [debug] Updating cache with Local kernels startUsingLocalKernelSpec:'.praxis_env.~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher (interpreter id = ~/.conda/envs/praxis_env/bin/python)', Added = , Updated = , Removed =
13:31:05.463 [debug] Jupyter completion time: 13
13:31:05.950 [info] Handle Execution of Cells 1 for ~/test.ipynb
13:31:05.957 [debug] start the kernel, options.disableUI=false for ~/test.ipynb
13:31:05.960 [debug] Execution Request Sent to Kernel for cell 1
13:31:05.973 [debug] Start cell 1 execution @<PHONE_NUMBER>973 (clear output)
13:31:05.973 [info] Kernel acknowledged execution of cell 1 @<PHONE_NUMBER>973
13:31:06.318 [info] End cell 1 execution @<PHONE_NUMBER>318, started @<PHONE_NUMBER>973, elapsed time = 0.345s
13:31:06.319 [debug] Cell 1 executed with state Success
13:31:07.825 [debug] Jupyter completion time: 41
13:31:12.607 [debug] Jupyter completion time: 16
13:31:13.214 [debug] Jupyter completion time: 12
13:31:15.273 [debug] Jupyter completion time: 851
13:31:17.346 [debug] Jupyter completion time: 634
13:31:17.717 [debug] Jupyter completion time: 17
13:31:20.144 [debug] Jupyter completion time: 44
13:31:24.400 [debug] Jupyter completion time: 44
13:31:25.489 [debug] Jupyter completion time: 644
13:31:27.271 [debug] Jupyter completion time: 109
13:31:29.289 [debug] Jupyter completion time: 18
13:31:31.289 [info] Handle Execution of Cells 2 for ~/test.ipynb
13:31:31.294 [debug] start the kernel, options.disableUI=false for ~/test.ipynb
13:31:31.300 [debug] Execution Request Sent to Kernel for cell 2
13:31:31.324 [debug] Start cell 2 execution @<PHONE_NUMBER>324 (clear output)
13:31:31.324 [info] Kernel acknowledged execution of cell 2 @<PHONE_NUMBER>324
13:31:32.005 [info] End cell 2 execution @<PHONE_NUMBER>005, started @<PHONE_NUMBER>324, elapsed time = 0.681s
13:31:32.006 [debug] Cell 2 executed with state Success
13:31:32.585 [debug] Jupyter completion time: 46
13:31:32.977 [debug] Jupyter completion time: 39
13:31:33.831 [debug] Jupyter completion time: 43
13:31:34.548 [debug] Jupyter completion time: 415
13:31:40.314 [debug] Jupyter completion time: 53
13:31:40.817 [debug] Jupyter completion time: 133
13:31:41.031 [debug] Jupyter completion time: 17
13:31:41.971 [debug] Jupyter completion time: 25
13:31:42.148 [debug] Jupyter completion time: 33
13:31:43.722 [debug] Jupyter completion time: 39
13:31:45.243 [info] Handle Execution of Cells 3 for ~/test.ipynb
13:31:45.248 [debug] start the kernel, options.disableUI=false for ~/test.ipynb
13:31:45.251 [debug] Execution Request Sent to Kernel for cell 3
13:31:45.259 [debug] Start cell 3 execution @<PHONE_NUMBER>259 (clear output)
13:31:45.259 [info] Kernel acknowledged execution of cell 3 @<PHONE_NUMBER>259
13:32:12.085 [info] End cell 3 execution @<PHONE_NUMBER>084, started @<PHONE_NUMBER>259, elapsed time = 26.825s
13:32:12.086 [debug] Cell 3 executed with state Success
13:32:21.142 [debug] Disposing request as the cell was deleted ~/test.ipynb
13:32:21.585 [debug] Disposing request as the cell was deleted ~/test.ipynb
13:32:21.967 [debug] Disposing request as the cell was deleted ~/test.ipynb
13:32:22.949 [debug] Disposing request as the cell was deleted ~/test.ipynb
13:32:25.192 [info] Dispose Kernel '~/test.ipynb' associated with '~/test.ipynb'
13:32:25.192 [debug] Cancel pending cells
13:32:25.194 [debug] Shutdown session b764dc3d-ea49-4705-ba5a-7077f5c76ecf, .jvsc74a57bd0af59e808e2bb2d49f2aad3fcaa4e3b4707b54f609965d9d8e3585c2a4131334f.~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher - start called from Error:
at Wv.shutdown (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:24:99398)
at Wv.disposeAsync (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:24:98866)
at ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:17:212646
at Ng.dispose (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:17:212860)
at Jg.disposeOldKernel (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:17:205145)
at Jg. (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:17:203478)
at c.y (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at c.z (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1972)
at c.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:2188)
at Dc. (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.10.1100000000-linux-x64/out/extension.node.js:2:2351987)
at c.y (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at c.z (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1972)
at c.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:2188)
at t.$acceptDocumentAndEditorsDelta (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:127:95776)
at n.S (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:134:10836)
at n.Q (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:134:10602)
at n.M (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:134:9686)
at n.L (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:134:8901)
at h.value (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:134:7565)
at c.y (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at c.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at d.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:96:14047)
at h.value (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:153:7918)
at c.y (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at c.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at d.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:96:14047)
at s.z (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:96:17112)
at h.value (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:96:15564)
at c.y (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at c.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at h.acceptChunk (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:96:11821)
at h.value (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:96:11108)
at c.y (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:1902)
at c.fire (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:80:2119)
at c.z (~/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:150:19388)
13:32:25.194 [info] Dispose Kernel process 28334.
13:32:25.243 [debug] Kernel got disposed, hence there is no longer a kernel associated with ~/test.ipynb
13:32:25.247 [debug] Cancel executions after closing notebook ~/test.ipynb
13:32:25.247 [debug] Cancel pending cells
13:32:25.247 [debug] Cancel executions after closing notebook ~/test.ipynb
13:32:25.247 [debug] Cancel pending cells
13:32:25.247 [debug] Cancel executions after closing notebook ~/test.ipynb
13:32:25.247 [debug] Cancel pending cells
13:32:25.247 [debug] Cancel executions after closing notebook ~/test.ipynb
13:32:25.253 [debug] Shutdown session b764dc3d-ea49-4705-ba5a-7077f5c76ecf, .jvsc74a57bd0af59e808e2bb2d49f2aad3fcaa4e3b4707b54f609965d9d8e3585c2a4131334f.~/.conda/envs/praxis_env/python.~/.conda/envs/praxis_env/python.-m#ipykernel_launcher - shutdown complete
13:32:25.294 [debug] Disposed Kernel process 28334.
13:32:25.321 [debug] KernelProcess Exited, Exit Code - undefined

Super weird but this just resolved on its own.
I am completely clueless what happened and how to learn to fix it next time.

Given that nothing changed in VS Code, I suspect this was purely environmental.
Though I have no idea whta it was.
Thanks for the update.
Lets close this issue for now, if you do run into this again, please do let me know


pluralize function for common/string

title, should be useful
currently we use export const pluralize = (word: string, n: number) => (n !== 1 ? word + 's' : word); which is nice but this Should Work for 99.9% of words now
okay yes technically fucky words like soliloquy aren't supported but english is fucked
thought VOWELS might be useful for consumers

probably not, will discuss in future with shadow


Issue7

Fixes #7

Description

Change the type from  Integer  to  Long  on  line 28 of the  Product  class.

This change will cause the application to no longer compile with maven, because you have to update all classes related to the  Product  entity ID field.

List of Classes needed to Modified

Finally, in the SQL script  schema.sql  change the type to  BIGINT  on line 20 and line 97.

@Sofiyan-coder Please check the compilation process, because it has failed.
The problem may be ShoppingListController.java.
https://github.com/despensa-app/despensa-rest-api/actions/runs/11132954558/job/30939121344

ok I will take a look at it and Update you

@nmarulo  I tried one last time. Please check now to see if the error occurs again. I can understand your actions regarding this issue #7
Thank you

@nmarulo  is it working now?

@Sofiyan-coder Thanks


[Feature Request] TTS Improvements

Thanks for including TTS support on your recent updates! Just a few more features related to TTS that are still not implemented, but is common in all readers with TTS support.

Controls for speech rate / speed
Controls for seeking where to start, move forward, go back, etc.
Text highlighting for current sentence being read by TTS.

These features are found in most epub readers (i.e. Moon+ Reader) and the late Ranobe app.

Oh, that'd be awesome I'd love that

Yes please. I want this so much. Also, another feature: Start tts from the selected part/word/sentence.

This was requested almost a year ago, sadge.

Is this still being worked on?

3 was done in plugins branch

Thanks, primarily looking for 1 and 2 as I listen to audiobooks mainly and doing that for LNs is kind of a pain, you have to download them manually.

I'm kinda interested in working on this. @satvikpendem could you perhaps clarify on what point 2 is? I know point 1 is just controlling the speed at which the voice goes at but what does point 2 mean?

@cactusoftheday Check out how Moon+ Reader Pro does it, it starts the TTS at the top of the current page or when you highlight a piece of text. LNReader currently starts at the beginning of the chapter regardless of how far along you are in the chapter.

implemented in 2.0 version

you can try v2 beta version, or wait for it stable release


refactor(shared-data): Add well groups with metadata to definitions2

overview
Blocked by #3489. Will rebase this PR over edge once 3489 is merged
This PR adds per-well-group metadata to all labware definitions and closes #3241. The shape of a well group is:
export type LabwareBrand = {|
  brand: string,
  brandId?: Array<string>,
  links?: Array<string>,
|}

export type LabwareWellGroupMetadata = {|
  displayName?: string,
  displayCategory?: LabwareDisplayCategory,
  wellBottomShape?: WellBottomShape,
|}

export type LabwareWellGroup = {|
  wells: Array<string>,
  metadata: LabwareWellGroupMetadata,
  brand?: LabwareBrand,
|}

Each definition now has:
// ...
groups: Array<LabwareWellGroup>
// ...

changelog

refactor(shared-data): Add well groups with metadata to definitions2

review requests
If you look at the ticket, this original spec for this work said to name the field grids instead of groups. After discussing various irregular labware with the UX team, I realized that grids implies regularity inside the groups that won't strictly line up with actual real-world irregular labware (like crystallography plates). Accordingly, went with the slightly more general "groups".
Unlike #3489, this PR only adds information to the definitions, so it shouldn't mess with anything downstream. Please do still give PD and Labware Library a once over, though.
Please also check the added information against the master spreadsheet. I had to make the following two judgement calls:

Spreadsheet was missing bottom shape for generic_96_wellplate_300ul_pcr

Assumed “v”

Spreadsheet had two conflicting bottom shapes listed for opentrons_24_aluminumblock_generic_2ml_screwcap

Went with “u”

@mcous  on opentrons_24_aluminumblock_generic_2ml_screwcap, screwcap tubes tend to be tiny v bottoms, but I'm not sure how we are explaining these well bottom types to users so may be better to keep as a u


Linux Terminal h2oGPT

Hello,
I am trying to make h2oGPT work in my linux terminal. Meaning I want to ask it and recieve the answer in my terminal, without having to go to the website.
curl https://api.openai.com/v1/chat/completions   -H "Content-Type: application/json"   -H "Authorization: Bearer MY_API_KEY"   -d '{
     "model": "h2o_gpt",
     "messages": [{"role": "user", "content": "Where is australia located?"}],
     "temperature": 0.7
   }'

and then I get the response:
 {
    "error": {
        "message": "The model `h2o_gpt` does not exist",
        "type": "invalid_request_error",
        "param": null,
        "code": null
    }
}

When the model was gpt 3.5 turbo, the default it was working fine. I'd like to use the h20_model.
Thanks,

You are using a curl on openai and trying to  use h2oGPT model. That won't work.


Removing one character

There was a typo. An extra right paren in the table header

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

This was already taken care of in a different PR


[Service Bus] atomManagement API - Fix test failures

A couple of tests related to createTopic() failed due to the change in response received from the service. Updated the expected response as per the new response observed.

@nemakam Any idea why the response for the createTopic() atom xml api has changed? isExpress was previously returning false, but not anymore

do we know if the service team made this change intentionally?

Not sure, but I guess so.
If there is a reason, they might eventually change the others to undefined too.

@HarshaNalluru Can we have the same for the 1.1.7 branch?


Prepare the Portal Environment for Creating Sites

Tutorial URL: https://developers.sap.com/tutorials/cp-portal-cloud-foundry-getting-started.html
Please specify the step you are referring to
Hi colleagues,
I can subscribe the portal in my trail account. but in our dev environment, I cannot find it in the subscriptions. Do I need any authorization or any settings?

Hi,
You can follow this document for required permissions to have Portal in your productive env: https://www.sap.com/documents/2019/08/6c6b960b-5e7d-0010-87a3-c30de2ffd8ff.html search for Entitlements part
If you have any problem, you can email me. Please note this issues should be used for problems in the started scenario and less for generic questions like this one..
Thanks
Iris

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


Initial Commit for scripted Google Translated files.

base.json is the original file. renamed from en.json to not interfere with script. en.json and cs.json output manually removed due to already covered in master branch

From Discord, I don't think Froox is accepting Google Translated Languages at this time.
Additionally, the JSON output for each language is in a minified form which while valid JSON makes it hard to read and process updates. Could you Pretty Print the JSON ouputs?
There may be a way to use these files if they are manually reviewed by a speaker of the languages provided. It should be an easy way to jump start those languages once a reviewer who speaks the language can be found.

Froox explicitly said that he's not accepting machine translations due to the quality of the translations being uncertain without someone who knows the language doing it.
I'd also highly recommend against it because machine translations often produce complete garbage. The idea behind this was to have users of the target language do the translation so that it's at least of a passing grade by a native speaker.

I will rerun script to pretty print the json, and to fix the use of unicode escape sequences.


choco upgrade ros-melodic-desktop_full does not upgrade rosdeps

We recently made a change to rViz which requires the new ogre release. When upgrading in-place, the new ogre drop is not brought in. This leads to a build break when compiling rViz plugins, like MoveIt.
Workaround:
choco upgrade all

The ROS dependencies and ROS itself are in the single installer package (inno setup), and this should be no longer a problem for upgrading.


[macOS] Remove old android SDK versions

Description
Remove old android SDK versions from macOS 11 and macOS 12 images.
Related issue:

#8952

Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run macos11, macos12


Plugins authentication with oauth

New plugins are really nice. I would like to try and create a plugin for Dropbox but the only authentication mechanism they have is oauth. Have you thought about how plugins will authenticate the user with oauth ?

That's a great question! Maybe we could do it a bit how zeit does the oauth login in their CLI? We need somehow to proxy the oauth request since dropbox wants to talk to an http endpoint correct? 🤔

dropbox wants to talk to an http endpoint correct?

Looks like it can be localhost:

Still probably need Kap to run a server to intercept the authorization code from DB and then exchange it for access / refresh tokens
Dropbox also supports implicit flow but the access tokens are short lived.

I recommend the approach I took on now gcp login: just create an HTTP server that listens on a "random" port to receive the data via the callback 👌

That's awesome, thanks @matheuss
We should probably provide an API for this so we can use one server in Kap and not let all plugins run their own? Thoughts @sindresorhus @sallar

Related issue: https://github.com/wulkano/kap/issues/286

We open a Window for authenticating with DropBox and it's not so complicated... It can be done from the plugin itself too.
https://github.com/buttercup/buttercup-desktop/blob/master/src/renderer/system/auth.js#L25

Plugin developers can support this in their configuration


Invalid "distclean" option in scripts

The refine scripts:

refine
refine.bat

contain the invalid "distclean" option.
For maven, "distclean" is not a processable goal or directive for any plugin.  It is not included in the clean plugin.
To Reproduce
Steps to reproduce the behavior:

./refine distclean

Current Results

An error.
Expected Behavior

The"distclean" option should likely perform a process including the "mvn clean" command along with several forced directory removals to clean the distribution compiles.
Screenshots

None
Versions

Operating System: N/A
Browser Version: N/A
JRE or JDK Version: N/A
OpenRefine: All

Datasets

N/A
Additional context

None

I think mvn clean already includes deleting the packaged versions of the software (the .jar files and packaging/target/) so I would be in favour of just removing the distclean option.

Hi, could I work on this one? I've already looked at the code and think it's pretty straightforward.


NEP: Simulation of Consensus Nodes Assignment

Simulation of Consensus Nodes Assignment

https://github.com/lerider/proposals/pull/1
https://github.com/lerider/proposals/pull/2


Allow block after bracket call syntax

Fixes #13975. I've been hitting this issue very much lately, I'm using self.[] in many of my projects for "smart constructors" and they sometimes require blocks. There's also a bug in the rough vicinity, foo[&.bar] and foo[1, &.bar] etc. causing the formatter to crash, maybe I'll try to fix it sometime later.

This PR does not actually add support for foo[&.bar] at the moment, right?

If by "add support" you mean parsing it's already parsed correctly, and works perfectly fine, and was working perfectly fine prior to this PR.
The problem is with the formatter. Some of my code in particular uses foo[&.bar] and so on (and it's quite expected for someone using x[...] { ... } to try using x[..., &...] at some point). This and variations on this break the formatter.
I tried looking into it, but the formatter code is too... complicated for me as an outsider, I guess. What I saw (or what I believe I saw) is that x[] and x[...] are handled separately from normal calls (which is expected, I guess...) and it seems that someone didn't anticipate a block getting in there, maybe?.. Maybe not?.. So perhaps someone else more familiar with the formatter could pick this up? It's a separate issue in the topic/tag sense, but it's related to this one, that's why I've mentioned it in the first place. So maybe it'd be better if I or someone else creates a separate issue for this?
Anyway. Sorry for the long response, I couldn't resist :)

It's also possible that foo[&.bar] works only by accident. I couldn't find any occurrences of it at all.
Though in Ruby this syntax also works

OK let's clarify this:
Block case
class C
  def [](n, &f)
    n.times do
      f.call
    end
  end
end

c = C.new
c[1] { puts "OK" }

Ruby:
OK

Crystal before:
 10 | c[1] { puts "OK" }
         ^
Error: unexpected token: "{"

Crystal after:
OK

Crystal formatter before:
syntax error: unexpected token: "{"

Crystal formatter after:
Deletes   { puts "OK" } and succeeds
-- not good

Block arg case
class C
  def [](&f)
    f.call(X.new)
  end
end

class X
  def test
    puts "OK"
  end
end

c = C.new
c[&.test]

Ruby:
N/A

Crystal before:
 14 | c[&.test]
     ^
Error: wrong number of block parameters (given 1, expected 0)

Crystal after:
Same syntax error as before

Crystal formatter before: crash
expecting ], not `&, `, at :14:3 (Exception)

Crystal formatter after:
Same crash as before

With this in mind:

@homonoidian, could you clarify why you say that foo[&.bar] already works? As far as I see, it doesn't work.

Additionally, I'm thinking maybe it shouldn't work??

This PR sadly leaves the formatter in a dangerous state (syntax error before, bad behavior after)

Gosh, it removes it?! Okay. Let's see. This is getting more complicated than I thought :) As it always does...

So regarding the block arg case, what you call "syntax error" is correct (in that it should be an error) in both "before" and "after", it's due to f.call(arg) while the block is expecting no arguments (as is stated in the method signature def [](&f) aka def [](&f : ->)). Changing it to def [](&f : X ->) makes the example work. Or using yield instead of f.call makes it work in any case, because yield doesn't seem to take the signature into account (for whatever reason). And the crash? That's the crash I was talking about, yes. Bad bad bad.
That the formatter removes the block... Well, I suppose someone (that someone being me!) didn't even try to run it... That's human factor in play here. As I've said my assumption is that the formatter doesn't know about the block, it doesn't even try to render it. Therefore, it doesn't render it and that's what we see as "removal".
So I guess it's the same issue.  Just two different kinds of blocks. In one case it's emitting junk because the block is part of "arguments" and it's at least trying to do something about it. The other case (do ... end or { }) the formatter simply isn't aware of. The block property is (after this PR) set by the parser but it is not read by the formatter.
So I do agree that this PR probably shouldn't be merged as is, without the formatter working as it should. I should probably look into the code. Maybe it isn't that hard after all to fix it.
I think it should work, but if and only if all the tools support it. It's better to have a syntax error guard than a portal to bug land. But I'm kind of going against myself here, as I'm already using it in quite a lot of code, and up to this point it only crashed the formatter, never removed anything. Gosh.

Okay, so I looked into the code. The fix for x[1, 2, &foo] is really really straightforward. Because &foo is a block arg, and in the formatter format_args simply wasn't given the argument for the block argument. So it's a few characters kind of change right here. What's worse is &.foo. It's "rewritten" into a block in the parser (so &.foo becomes do |__arg0| __arg0.foo end). And there's some dark arts if block = node.block code that's dealing with this with the help of the lexer.
I did succeed in fixing the formatter issue, mostly. By refactoring the body of this condition into a separate method, let's say format_call_block, and then calling it roughly before the closing bracket is written, under a similar condition if block = node.block. That's roughly the fix. This results in more code than I'm comfortable adding to this PR. So I do think it's better to have a separate issue/PR for this, and I can upload most of the fix now but not all of it. "Not all of it" means there are a few failing tests out of those that I've added, and I couldn't find a way to fix them yet. Additionally, I've found a bug where formatting
foo(
  1,
  # 2,
  # 3,
  &.foo
)

... fails in a very very ugly way:
foo(
  1 # 2,
# 3,
,
  &.foo
)

Additionally the following:
foo(
  # Comment
  &.z
)

... formats to this:
foo(
  # Comment
&.z)

I suspect there are more issues like these ones, maybe some of them are already known. And my fix inherits them, causing a few failing tests. I've tested the above in 1.11.2, same kind of failure, so it's not me. Formatting foo[&...]? and foo[...]? { } is also mostly uncharted territory in my fix, more tests are needed. Formatting foo[] {} and foo[] do ... end works with the fix, as far as I can tell. And I suppose more tests are needed for calls too as the existing ones didn't catch the above. Without fixing calls [] won't format properly also (I mean, it will format properly in most common cases, it already does; but not in all cases).
And in the end, I'm lost! :rofl:

Do you have a branch with your changes available?

Here it is: https://github.com/homonoidian/crystal/tree/brackets-block-formatting

It's working on my projects, I'm already using it and I don't think it broke any one of my files. But formatting bugs begin when indentation and multiline appear. I think I remember writing column where I presumably shouldn't... Probably responsible for some of the bugs. After months of writing 2-3 line methods my head is spinning. Everything is so convoluted there and my additions make it worse, as I don't have the bigger picture. Nah. Anyway.

@HertzDevil The formatter also inserts a bad comma whenever one introduces a newline. E.g. "x[\n&.a\n]" (crash) or "foo[\n  1, 2, &.x]"  which doesn't crash but results in:
foo[
  1, 2,
, &.x]

It would be awesome to have this merged. My use case:
I want to replace Foo.new(...).call by Foo[...], but it works only if the #call doesn't accept a block, if I do:
Foo[...] do
  # do something
end

I get # Error: expecting token 'EOF', not 'do'.


support edge browser

See PR #96  . Verified main tests on linux, mac, windows edge browser. MacOS tests failed with double the screenshot size that was expected. Edge tests passed on windows and linux.


add font awesome to repo

add font awesome to repo so we can use the free font awesome symbols in the wiki and documentation.
it might just need a couple lines of this code and it's done (unsure of how easy they make it sound).
https://gkoberger.github.io/Font-Awesome/get-started/
reference repo:  https://github.com/FortAwesome/Font-Awesome

Can't be done: https://stackoverflow.com/questions/51956361/custom-css-file-for-readme-md-in-a-github-repo/51956450#51956450


Make Keptn Governance Committee available on the site

Keptn now has a governance committee. Currently it is only shown on this comment on GitHub.
I understand there will be tasks to document this more fully, but most likely those documents will remain on GitHub.
I feel that it is important to be upfront and transparent about the governance committee members and the timings of terms - so this issue proposes that this information is directly accessible via the main Keptn website (and any sub-websites that appears forthwith).
I feel that this transparency is important for v1.0.0

@aepfli @DavidPHirsch before I start on this, I see https://github.com/keptn/community/pull/247 and then it is reverted https://github.com/keptn/community/pull/251. How should we proceed with this?

i am actively workin on a different approach for KLT - https://github.com/keptn/lifecycle-toolkit/pull/1077 - which we should also apply to the main site afterwards. this way, we can have it on one page. also see - https://github.com/keptn/community/pull/258 where i try to get the community repo into a renderable shape :)

close as not planned


[joy-ui][Radio][Input] Fix inheritance of disabled prop

Before
https://codesandbox.io/s/vigorous-leaf-l4ynj3?file=/src/index.tsx
After
https://codesandbox.io/s/elastic-sunset-7fykcs?file=/src/Demo.tsx
In both Input and Radio disabled prop from theme were taking precedence over disabled prop from FormControl. This PR fixes the issue.

[x] I have followed (at least) the PR section of the contributing guide.

Have you checked if this is implemented across the other input components?

Switch, Checkbox were looking good. Input is also having same issue, fixed in this commit https://github.com/mui/material-ui/pull/39934/commits/015b6149280ed630fa2c25d0698c9c19f229a8be


Questions about how to run the training process?

Hi, I read your paper and it was very exciting and inspiring. I hope you can provide some training details, such as how the dataset is placed(e.g. training.txt), and the related download address. Being able to run through your code would be a great help to subsequent researchers.

Thank you for your appreciation. For the dataset, send me an email with the purpose of your research and I will provide the link.
The .txt are in another repository https://github.com/IIT-PAVIS/acoustic-images-self-supervision/tree/master/lists which has been created for the paper presenting the dataset. Write to my email<EMAIL_ADDRESS>for any other information.

Thank you for your appreciation. For the dataset, send me an email with the purpose of your research and I will provide the link. The .txt are in another repository https://github.com/IIT-PAVIS/acoustic-images-self-supervision/tree/master/lists which has been created for the paper presenting the dataset. Write to my email<EMAIL_ADDRESS>for any other information.

Thanks for the kindly reply, I've figured out how to run the training, thanks again!


Checking if user_data object exists before getting user email for metrics purposes

Basically we are trying to get the user email for metrics purposes, and user_data object is not defined in that view.
Fixes #3913
cc @matallo @saleiva @viddo

I've seen lot of window.user_data.email for metrics purposes. Not sure if this is the best way to get that info @matallo. @viddo, what do you think if we create application helper functions to get that info?

Frontend tests were OK :+1: (details)

oop, sorry to come late to the party; I agree about using helpers at some point, just replicated old codebase for new metrics, in the mean time +1

Frontend tests were OK :+1: (details)


Long running time of M3C2 on entire point cloud compared to CloudCompare

With the help of this git issue I'm able to run M3C2 algorithm with (I think) the same params used in CloudCompare. However, the M3C2 algorithm takes roughly 100x times longer than the implementation of CloudCompare.
Cloudcompare M3C2: ~2 seconds
py4dgeo M3C2: 271 seconds
I put all the files to recreate the experiment here.
Is the time difference caused by a param that I forgot to configure in the py4dgeo implementation? Here is the config file (default settings exported from CloudCompare): m3c2_params.txt

Thanks for providing all the configuration and date. I will reproduce and investigate this next week.

Hey @chrise96 Thanks again for providing test data and configuration, this has been really helpful. I found a few things that went in favor of CloudCompare in your comparison - some can be fixed, some can be documented and some will need future work in py4dgeo (remember we are in early dev):

CloudCompare's scale parameters are diameters, while py4dgeo uses radii. This lead to py4dgeo operating with a 4x larger search cylinder. I am currently fixing this for the CloudCompareM3C2 class in #129, but you can also just divide your radii by 2.
Your M3C2 configuration contains SubsampleEnabled=true which means that you are not using the input cloud as the set of core points, but a downsampled version of it that contains only a fraction of points (in my testing with CC and your data, only 1%). You are explicitly telling py4dgeo to use the entire point cloud though with corepoints = epoch1.cloud. The M3C2 algorithm is linear in the number of corepoints which makes this one particularly important. Can you doublecheck the number of corepoints from the CC logs?
CloudCompare has a (quite undocumented) option called UseSinglePass4Depth that if set to false enables a performance optimization that py4dgeo has not (yet) implemented (see #88 ). You might want to set that to true to better compare against py4dgeos current state.

Here is a modified version of your notebook. It does the same thing, only that it splits py4dgeos application of M3C2 into a few substeps: Searchtree construction, Normal Calculation, Distance Calculation. All of these have always been performed, but lazily evaluated during run().
Can you run again on your end and see how performance compares?

Thank you for the very detailed update!
I see now indeed that the config .txt file I provided contains SubsampleEnabled=true, this must be false... I updated the branch with this change. It takes now 19.5 seconds in CloudCompare.
I didn't know about this UseSinglePass4Depth option (In the advanced tab in M3C2 CloudCompare "Do not use multiple pass for depth").
Here a complete screenshot of the modified notebook run (dividing radii by 2 really speeds it up):

I already feared it would not be as easy as the downsampling setting :disappointed:.
I am assuming you run this on Windows - correct? I made some tests between Linux and Windows on the same machine (dual boot, no virtualization) and found the results to be quite surprising:

Setup
py4dgeo Normals
CC Normals
py4dgeo Distances
CC Distances

Windows 6 Threads
13s
6s
127s
30s

Windows 1 Thread
28.4s
--
275s
--

Windows 6 Threads (Blocking)
10s
--
97s
--

Linux 6 Threads
2.7s
--
34s
--

Linux 1 Thread
14s
--
201s
--

I conclude that we have a toolchain issue on Windows that introduces a significant performance penalty. There is a multithreading related aspect to it (Linux scales roughly optimal, Windows not at all), but sequential performance is also clearly affected. The Blocking variant in above table lets OpenMPs dynamic scheduler work on chunks of 128 corepoints. My next experiments will be to vary the Windows toolchain to get a better understanding of where the problem might be.

The M3C2 distance results in py4dgeo are very different compared to the CloudCompare results. Points in some static objects, for example a street sign in the provided point clouds, do not come close to the 0 value for the M3C2 distance. How do you choose the best configuration params for py4dgeo?


OnRemoveByHandle not working with Redis

Hi,
I've configured my cache as below, but am not getting the OnRemoveByHandle called.
Configuration = new ConfigurationBuilder() 				.WithJsonSerializer() 				.WithRedisConfiguration("redis", c => 				{ 					var connectionString = cp.DataOptions.Cache.Split(":"); 					c 						.WithAllowAdmin() 						.EnableKeyspaceEvents() 						.WithEndpoint(connectionString[0], int.Parse(connectionString[1])); 				}) 				.WithRedisBackplane("redis") 				.WithRedisCacheHandle("redis", true).Build();
Cache is being created like so:
 _cache = CacheFactory.FromConfiguration<T>(Configuration); _cache.OnRemoveByHandle += OnExpiry;
I see the item being added and expired from the cache in RedisDesktopManager.
Any idea what I could be doing wrong?

Do you have key space events with the required settings enabled on the Redis server?

What value does that need to be set to in the redis.conf?

https://github.com/MichaCo/CacheManager/blob/dev/src/CacheManager.StackExchange.Redis/RedisConfigurationBuilderExtensions.cs#L44

Figured it out. Thanks!

Great ;)


gather-logs: Remove support for specifying the server type / chef server 11

We ship this here. There's no need to support stuff from 2013 in this script. Also remove support for gathering data on reporting since that won't install into 14.x. Not this does change the testing syntax to be the 1st argument instead of the 2nd.
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

https://buildkite.com/chef/chef-chef-server-master-omnibus-adhoc/builds/2989


[FIX]: Change twitter Logo to X Logo

What would you like to share?
The Logo of Twitter needed to be Changed to X as the logo is outdated now,
Additional information
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

make sure to do in dev branch

can I work on this issue ?

@kabir0x23 please Check Pull Request #515, And Can you please make this PR under HacktoberFest? It will be helpful.


populate event names and add filters to contract events

https://web3py.readthedocs.io/en/stable/filters.html#event-log-filters

@sentilesdal claims this is done, not sure what PR. Closing issue.


CP-23051: Change default kube-state-metrics behavior to use Cloudzero subchart

Description
This PR does the following:

enables the CloudZero KSM by default.
Modifies the KSM annotations so as not to be discoverable by other  scrape jobs.

Testing

Test Case 1: Validate that the CloudZero KSM is deployed with the correct name:

Test Case 2: Validate that other observability services cannot scrape the CloudZero KSM, given the annotation change:
TBD

Checklist

[ ] I have added documentation for new/changed functionality in this PR
[x] All active GitHub checks for tests, formatting, and security are passing
[x] The correct base branch is being used, if not main

lgtm! this will be released as a beta version, right? will it be a minor or patch?

I think a beta version is a good idea. Maybe OpenNet would be willing to give it a go for us.


Document current known issues in 24.03.02

Description
By Submitting this PR I confirm:

I am familiar with the Contributing Guidelines.
When the PR is ready for review, new or existing tests cover these changes.
When the PR is ready for review, the documentation is up to date with these changes.

/merge


Add Simple Chinese Translation and Picture

Add Simpled Chinese Translation.

PTAL. @cpettitt @mwaldstein @hypergeometric @styfle

Here is feature issue: https://github.com/dagrejs/graphlib/issues/183


tuya-panel-layout && tuya-panel-core && tuya-panel-i18n && tuya-panel-text && tuya-panel-topbar

Description
add tuya-panel-layout && tuya-panel-core && tuya-panel-i18n && tuya-panel-text && tuya-panel-topbar.
Type of change
Please select the relevant option.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Codecov Report

Merging #133 (4114544) into master (0edf2f9) will decrease coverage by 0.56%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #133      +/-   ##
==========================================
- Coverage   90.73%   90.16%   -0.57%
==========================================
  Files         155      146       -9
  Lines        7381     6498     -883
  Branches     2034     1829     -205
==========================================
- Hits         6697     5859     -838
+ Misses        563      518      -45
  Partials      121      121

Impacted Files
Coverage Δ

packages/tuya-panel-utils/src/json.ts

packages/tuya-panel-utils/src/number.ts

packages/tuya-panel-utils/src/string.ts

packages/tuya-panel-utils/src/color.ts

packages/tuya-panel-utils/src/ratio.ts

packages/tuya-panel-utils/src/temperature.ts

packages/tuya-panel-utils/src/index.ts

packages/tuya-panel-utils/src/time.ts

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0edf2f9...4114544. Read the comment docs.


Extend on Commands function and contributors mention.

I've created a new function similar to linux cssh command where opening multiple windows and have keys sent to all windows (imagining opening VIM on multiple machines and editing all at the same time).
I've got this working but lacking all the keys properly due to windows funny way to handle key capturing. But something like this would benefit me more than the "Commands" option available
Also mentioned in google code some time back (Issue #318), would be nice to add acknowledgements to contributors like myself for a number of patches that have made it through.

Can you not simply add the patch for the 2nd part of the question. attached the original patch from goolecode
DevelopedBy.patch.txt

Hi George,
Little stale -- sorry! I'm busy with other projects, glad to revisit this if you submit it in a pull request. I have added a link in the acknowledgements tab to code contributors.


Write documentations

I'm reopening this because we're yet to finalize the docs. Also, I want to improve it a bit, with more code examples.

[ ] CLI
[ ] Changelog
[ ] API Reference


buttons: resize to a more usable 240x80px

Fixes https://github.com/flathub/website/issues/1595

The font in the preview svg button seems broken (yes, I think it was broken even before?)

@barthalion please add replacing these on the mirrors to your todo list


AWSS3Provider - ensure credentials error No Auth module registered in Amplify

I've follow the Storage implementation but when i select a file from AmplifyFileInput or AmplifyImageInput i see this error in console:
AWSS3Provider - ensure credentials error No Auth module registered in Amplify
No credentials
The storage is not public (require valid user) but i'm logged into react-admin with "Admin" user and i see all other data
How can i do?

I've reinstall @aws-amplify/auth and now the image is loader... but when i save my form i've an error about "images" field name:
"The variables input contains a field name 'images' that is not defined for input object type 'CreatePillInput' " but into my schema.graphql i've added this fiels...
type Pill
  @model{
  id: ID!
  title: String
  images: [S3Object]
}

I've find CreatePillInput object into amplify/backend/api/APPNAME/build/schema.graphql and here the field is missing.
input CreatePillInput {
id: ID
title: String
}
Why????

Hi @mgiorgi-github,
Looks like something is wrong in your schema, did you also add the S3Object type in your schema:
type S3Object {
  bucket: String!
  region: String!
  key: String!
}

and sorry I have to ask... did you amplify push?

Hi, i've added the S3Object... i've delete and create a new project and it work fine.


Fix 9621

Description of changes

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Closing since this has conflicts and is stale.