Cannot connect to jupyter kernel on remote connection

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
I'm unable to use jupyter notebooks when connected to a remote server; this only started recently.  I'm using anaconda on the remote server, and I have the correct environment selected in jupyter, but when I try to execute a cell I get a
| Running cells with 'Python 3.9.12 64-bit ('base': conda)' requires jupyter and notebook.
popup error.  When I activate that environment in the remote terminal, both packages are installed and up-to-date.  If I select "install" from the popup, it tries to install those packages but it also finds that they are already installed.
VS Code Version
Version: 1.62.3 (Universal) Commit: ccbaa2d27e38e5afa3e5c21c1c7bef4657064247 Date: 2021-11-17T07:59:13.865Z Electron: 13.5.2 Chrome: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Darwin x64 21.3.0
Jupyter Extension Version
v2021.10.1101450599
Jupyter logs
Info 2022-06-16 12:07:43: Setting setActiveController for file:///mnt/labnas/jbergner/grain_trajectories/twhya/plotting/Save_traj_Rob.ipynb
Info 2022-06-16 12:07:43: KernelProvider switched kernel to id = .jvsc74a57bd07356241a38552ec98b58963ac56d73e1c5f9be70b80edfbf3428764e5766126c./home/jbergner/anaconda3/python./home/jbergner/anaconda3/python.-m#ipykernel_launcher
Info 2022-06-16 12:07:43: Starting Notebook in kernel.ts id = .jvsc74a57bd07356241a38552ec98b58963ac56d73e1c5f9be70b80edfbf3428764e5766126c./home/jbergner/anaconda3/python./home/jbergner/anaconda3/python.-m#ipykernel_launcher
Error 2022-06-16 12:07:43: Failed to get activated conda env variables for base: /home/jbergner/anaconda3/bin/python
Info 2022-06-16 12:07:43: Checking for server existence.
Info 2022-06-16 12:07:43: Process Execution: > ~/anaconda3/bin/python -m pip list
> ~/anaconda3/bin/python -m pip list
Info 2022-06-16 12:07:43: Checking for server usability.
Info 2022-06-16 12:07:43: Server not usable (should ask for install now)
Error 2022-06-16 12:07:43: Failed to get activated conda env variables for base: /home/jbergner/anaconda3/bin/python
Error 2022-06-16 12:07:43: Failed to get activated conda env variables for base: /home/jbergner/anaconda3/bin/python
Info 2022-06-16 12:07:43: Process Execution: > ~/anaconda3/bin/python -c "import jupyter"
> ~/anaconda3/bin/python -c "import jupyter"
Info 2022-06-16 12:07:43: Process Execution: > ~/anaconda3/bin/python -c "import notebook"
> ~/anaconda3/bin/python -c "import notebook"
Info 2022-06-16 12:07:43: Creating controller for jupyter-notebook with interpreter /home/jbergner/anaconda3/bin/python
Error 2022-06-16 12:07:43: failed to create INotebook in kernel, UI Disabled = true [o [Error]: Jupyter cannot be started. Error attempting to locate jupyter: Running cells with 'Python 3.9.12 64-bit ('base': conda)' requires jupyter and notebook.
	at S.startServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:936180)
	at async S.createServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:935464)
	at async c.getNotebook (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:985092)
	at async p.getOrCreateNotebook (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:932939)
	at async /home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:24:81978] {
  category: 'jupyterinstall',
  action: 'https://aka.ms/pyaiinstall',
  actionTitle: 'Get more help'
}
Error 2022-06-16 12:07:43: failed to start INotebook in kernel, UI Disabled = true [o [Error]: Jupyter cannot be started. Error attempting to locate jupyter: Running cells with 'Python 3.9.12 64-bit ('base': conda)' requires jupyter and notebook.
	at S.startServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:936180)
	at async S.createServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:935464)
	at async c.getNotebook (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:985092)
	at async p.getOrCreateNotebook (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:932939)
	at async /home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:24:81978] {
  category: 'jupyterinstall',
  action: 'https://aka.ms/pyaiinstall',
  actionTitle: 'Get more help'
}
Error 2022-06-16 12:07:43: Failed to get activated conda env variables for base: /home/jbergner/anaconda3/bin/python
Info 2022-06-16 12:07:43: Process Execution: > ~/anaconda3/bin/python -m pip list
> ~/anaconda3/bin/python -m pip list
Info 2022-06-16 12:07:43: Find preferred kernel for file:///mnt/labnas/jbergner/grain_trajectories/twhya/plotting/Save_traj_Rob.ipynb with metadata {"kernelspec":{"display_name":"Python 3","language":"python","name":"python3"},"language_info":{"codemirror_mode":{"name":"ipython","version":3},"file_extension":".py","mimetype":"text/x-python","name":"python","nbconvert_exporter":"python","pygments_lexer":"ipython3","version":"3.9.12"}} & preferred interpreter {"sysPrefix":"/home/jbergner/anaconda3","envType":"Conda","envName":"base","envPath":"/home/jbergner/anaconda3","path":"/home/jbergner/anaconda3/bin/python","architecture":3,"sysVersion":"3.9.12 (main, Apr  5 2022, 06:56:58) \n[GCC 7.5.0]","version":{"raw":"3.9.12","major":3,"minor":9,"patch":12,"build":[],"prerelease":["final","0"]},"companyDisplayName":"Anaconda, Inc.","displayName":"Python 3.9.12 64-bit ('base': conda)"}
Info 2022-06-16 12:07:43: findPreferredKernel score for speclanguage=python, Python 3.4.10 64-bit is -1
Info 2022-06-16 12:07:43: findPreferredKernel score for Python3, Python 3.4.10 64-bit is 2
Info 2022-06-16 12:07:43: findPreferredKernel score for Python 3.4.10 64-bit is 2
Info 2022-06-16 12:07:43: findPreferredKernel score for speclanguage=python, Python 3.4.10 64-bit is -1
Info 2022-06-16 12:07:43: findPreferredKernel score for Python3, Python 3.4.10 64-bit is 2
Info 2022-06-16 12:07:43: findPreferredKernel score for Python 3.4.10 64-bit is 2
Info 2022-06-16 12:07:43: findPreferredKernel score for speclanguage=python, Python 2.7.5 64-bit is -1
Info 2022-06-16 12:07:43: findPreferredKernel score for Python 2.7.5 64-bit is 1
Info 2022-06-16 12:07:43: findPreferredKernel score for speclanguage=python, Python 2.7.5 64-bit is -1
Info 2022-06-16 12:07:43: findPreferredKernel score for Python 2.7.5 64-bit is 1
Info 2022-06-16 12:07:43: findPreferredKernel score for speclanguage=python, Python 3.6.8 64-bit is -1
Info 2022-06-16 12:07:43: findPreferredKernel score for Python3, Python 3.6.8 64-bit is 2
Info 2022-06-16 12:07:43: findPreferredKernel score for Python 3.6.8 64-bit is 2
Info 2022-06-16 12:07:43: findPreferredKernel score for speclanguage=python, Python 3.7.6 64-bit ('base': conda) is 0
Info 2022-06-16 12:07:43: findPreferredKernel score for Python3, Python 3.7.6 64-bit ('base': conda) is 2
Info 2022-06-16 12:07:43: findPreferredKernel score for Python 3.7.6 64-bit ('base': conda) is 5
Info 2022-06-16 12:07:43: findPreferredKernel score for speclanguage=python, Python 3.8.9 64-bit is -1
Info 2022-06-16 12:07:43: findPreferredKernel score for Python3, Python 3.8.9 64-bit is 2
Info 2022-06-16 12:07:43: findPreferredKernel score for Python 3.8.9 64-bit is 2
Info 2022-06-16 12:07:43: findKernel found Python 3.7.6 64-bit ('base': conda)
Info 2022-06-16 12:07:43: Find kernel spec, Class name = k, completed in 731ms, has a truthy return value, Arg 1: <Uri:/mnt/labnas/jbergner/grain_trajectories/twhya/plotting/Save_traj_Rob.ipynb>, Arg 2: {"kernelspec":{"display_name":"Python 3","language":"python","name":"python3"},"language_info":{"codemirror_mode":{"name":"ipython","version":3},"file_extension":".py","mimetype":"text/x-python","name":"python","nbconvert_exporter":"python","pygments_lexer":"ipython3","version":"3.9.12"}}, Arg 3: {"_isCancelled":false,"_emitter":{"_disposed":false,"_listeners":{"_first":{"next":{},"prev":{}},"_last":{"next":{},"prev":{}},"_size":1}}}, Return Value: {"kind":"startUsingPythonInterpreter","kernelSpec":{"specFile":"/home/jbergner/.local/share/jupyter/kernels/python376jvsc74a57bd07356241a38552ec98b58963ac56d73e1c5f9be70b80edfbf3428764e5766126c/kernel.json","interpreterPath":"/home/jbergner/anaconda3/bin/python","name":"python376jvsc74a57bd07356241a38552ec98b58963ac56d73e1c5f9be70b80edfbf3428764e5766126c","argv":["/home/jbergner/anaconda3/bin/python","-m","ipykernel_launcher","-f","{connection_file}"],"language":"python","path":"/home/jbergner/anaconda3/bin/python","display_name":"Python 3.7.6 64-bit ('base': conda)","metadata":{"originalSpecFile":"/home/jbergner/anaconda3/share/jupyter/kernels/python3/kernel.json","interpreter":{"sysPrefix":"/home/jbergner/anaconda3","envType":"Conda","envName":"base","envPath":"/home/jbergner/anaconda3","path":"/home/jbergner/anaconda3/bin/python","architecture":3,"sysVersion":"3.7.6 (default, Jan  8 2020, 19:59:22) \n[GCC 7.3.0]","version":{"raw":"3.7.6","major":3,"minor":7,"patch":6,"build":[],"prerelease":["final","0"]},"companyDisplayName":"Anaconda, Inc.","displayName":"Python 3.7.6 64-bit ('base': conda)"}},"env":{"MANPATH":"/software/slurm-current-el7-x86_64/share/man:/software/emacs-24-el7-x86_64/share/man:/opt/xcat/share/man:/opt/xcat/share/man::/usr/share/man:/usr/local/share/man","XDG_SESSION_ID":"12212","HOSTNAME":"ravenwood.uchicago.edu","_LMFILES__modshare":"/etc/modulefiles/env/ravenwood:1:/etc/modulefiles/slurm/current:1:/software/modulefiles/emacs/24:1","MODULEPATH_modshare":"/software/modulefiles:24:/etc/modulefiles:8","SHELL":"/bin/bash","HISTSIZE":"1000","SSH_CLIENT":"<IP_ADDRESS> 58210 22","TMPDIR":"/tmp","DISTARCH":"el7-x86_64","LIBRARY_PATH":"/software/slurm-current-el7-x86_64/lib64:/software/slurm-current-el7-x86_64/lib","LIBRARY_PATH_modshare":"/software/slurm-current-el7-x86_64/lib64:1:/software/slurm-current-el7-x86_64/lib:1","CONDA_SHLVL":"1","PYTHONUNBUFFERED":"1","CONDA_PROMPT_MODIFIER":"(base) ","VSCODE_EXTHOST_WILL_SEND_SOCKET":"true","QTDIR":"/usr/lib64/qt-3.3","QTINC":"/usr/lib64/qt-3.3/include","PERL_BADLANG":"0","QT_GRAPHICSSYSTEM_CHECKED":"1","PYTHONIOENCODING":"utf-8","USER":"jbergner","LS_COLORS":"","LD_LIBRARY_PATH":"/software/slurm-current-el7-x86_64/lib64:/software/slurm-current-el7-x86_64/lib","VSCODE_VERBOSE_LOGGING":"true","XCATROOT":"/opt/xcat","CONDA_EXE":"/home/jbergner/anaconda3/bin/conda","CPATH":"/software/slurm-current-el7-x86_64/include","VSCODE_PIPE_LOGGING":"true","VSCODE_LOG_STACK":"false","VSCODE_INJECT_NODE_MODULE_LOOKUP_PATH":"/home/jbergner/.vscode-server/bin/7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e/remote/node_modules","VSCODE_AMD_ENTRYPOINT":"vs/server/remoteExtensionHostProcess","VSCODE_AGENT_FOLDER":"/home/jbergner/.vscode-server","_CE_CONDA":"","PATH":"/home/jbergner/.vscode-server/bin/7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e/bin:/home/jbergner/anaconda3/bin:/mnt/labnas/jbergner/apps/casa-pipeline-release-5.6.1-8.el7/bin:/software/bin:/software/slurm-current-el7-x86_64/bin:/srv/adm/bin:/software/emacs-24-el7-x86_64/bin:/opt/xcat/bin:/opt/xcat/sbin:/opt/xcat/share/xcat/tools:/home/jbergner/.vscode-server/bin/7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e/bin:/home/jbergner/anaconda3/bin:/mnt/labnas/jbergner/apps/casa-pipeline-release-5.6.1-8.el7/bin:/home/jbergner/anaconda3/bin:/home/jbergner/anaconda3/condabin:/opt/xcat/bin:/opt/xcat/sbin:/opt/xcat/share/xcat/tools:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/opt/ibutils/bin:/opt/dell/srvadmin/bin:/home/jbergner/.local/bin:/home/jbergner/bin:/home/jbergner/.local/bin:/home/jbergner/bin","MAIL":"/var/spool/mail/jbergner","CONDA_PREFIX":"/home/jbergner/anaconda3","PWD":"/home/jbergner","VSCODE_HANDLES_UNCAUGHT_ERRORS":"true","_LMFILES_":"/software/modulefiles/emacs/24:/etc/modulefiles/slurm/current:/etc/modulefiles/env/ravenwood","LANG":"en_US.UTF-8","MODULEPATH":"/software/modulefiles:/etc/modulefiles","LOADEDMODULES":"emacs/24:slurm/current:env/ravenwood","CPATH_modshare":"/software/slurm-current-el7-x86_64/include:1","VSCODE_LOG_NATIVE":"false","HISTCONTROL":"ignoredups","_CE_M":"","HOME":"/home/jbergner","SHLVL":"5","PATH_modshare":"/usr/bin:1:/software/bin:1:/home/jbergner/anaconda3/condabin:999999999:/home/jbergner/.vscode-server/bin/7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e/bin:999999999:/srv/adm/bin:1:/usr/local/bin:1:/opt/xcat/sbin:1:/opt/dell/srvadmin/bin:1:/opt/ibutils/bin:1:/home/jbergner/.local/bin:999999999:/mnt/labnas/jbergner/apps/casa-pipeline-release-5.6.1-8.el7/bin:999999999:/opt/xcat/bin:1:/opt/xcat/share/xcat/tools:1:/usr/sbin:1:/software/slurm-current-el7-x86_64/bin:1:/home/jbergner/anaconda3/bin:999999999:/software/emacs-24-el7-x86_64/bin:1:/usr/lib64/qt-3.3/bin:1:/usr/local/sbin:1:/home/jbergner/bin:999999999","APPLICATION_INSIGHTS_NO_DIAGNOSTIC_CHANNEL":"true","VSCODE_NLS_CONFIG":"{\"locale\":\"en\",\"availableLanguages\":{}}","DIST":"el7","MANPATH_modshare":"/usr/local/share/man:1::1:/usr/share/man:1:/software/slurm-current-el7-x86_64/share/man:1:/opt/xcat/share/man:1:/software/emacs-24-el7-x86_64/share/man:1","LOGNAME":"jbergner","MODULERCFILE":"/srv/adm/modules/init/modulerc","CONDA_PYTHON_EXE":"/home/jbergner/anaconda3/bin/python","QTLIB":"/usr/lib64/qt-3.3/lib","CVS_RSH":"/usr/bin/ssh","LD_LIBRARY_PATH_modshare":"/software/slurm-current-el7-x86_64/lib64:1:/software/slurm-current-el7-x86_64/lib:1","SSH_CONNECTION":"<IP_ADDRESS> 58210 <IP_ADDRESS> 22","SOFTPATH":"/software","VSCODE_IPC_HOOK_CLI":"/run/user/20012/vscode-ipc-be36522e-9645-46c4-b5ad-02c4fdc59ca7.sock","MODULESHOME":"/srv/adm/modules","LESSOPEN":"||/usr/bin/lesspipe.sh %s","CONDA_DEFAULT_ENV":"base","BROWSER":"/home/jbergner/.vscode-server/bin/7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e/bin/helpers/browser.sh","LOADEDMODULES_modshare":"env/ravenwood:1:slurm/current:1:emacs/24:1","ARCH":"x86_64","XDG_RUNTIME_DIR":"/run/user/20012","VSCODE_CWD":"/home/jbergner","BASH_FUNC_module()":"() {  eval `$TCLSH /srv/adm/modules/modulecmd.tcl bash $*`\n}","_":"/home/jbergner/anaconda3/bin/python"}},"interpreter":{"sysPrefix":"/home/jbergner/anaconda3","envType":"Conda","envName":"base","envPath":"/home/jbergner/anaconda3","path":"/home/jbergner/anaconda3/bin/python","architecture":3,"sysVersion":"3.9.12 (main, Apr  5 2022, 06:56:58) \n[GCC 7.5.0]","version":{"raw":"3.9.12","major":3,"minor":9,"patch":12,"build":[],"prerelease":["final","0"]},"companyDisplayName":"Anaconda, Inc.","displayName":"Python 3.9.12 64-bit ('base': conda)"},"id":".jvsc74a57bd07356241a38552ec98b58963ac56d73e1c5f9be70b80edfbf3428764e5766126c./home/jbergner/anaconda3/python./home/jbergner/anaconda3/python.-m#ipykernel_launcher"}
Info 2022-06-16 12:07:43: PreferredConnection: .jvsc74a57bd07356241a38552ec98b58963ac56d73e1c5f9be70b80edfbf3428764e5766126c./home/jbergner/anaconda3/python./home/jbergner/anaconda3/python.-m#ipykernel_launcher found for NotebookDocument: file:///mnt/labnas/jbergner/grain_trajectories/twhya/plotting/Save_traj_Rob.ipynb
Info 2022-06-16 12:07:43: TargetController found ID: .jvsc74a57bd07356241a38552ec98b58963ac56d73e1c5f9be70b80edfbf3428764e5766126c./home/jbergner/anaconda3/python./home/jbergner/anaconda3/python.-m#ipykernel_launcher for document file:///mnt/labnas/jbergner/grain_trajectories/twhya/plotting/Save_traj_Rob.ipynb
Info 2022-06-16 12:07:43: Setting controller affinity for file:///mnt/labnas/jbergner/grain_trajectories/twhya/plotting/Save_traj_Rob.ipynb .jvsc74a57bd07356241a38552ec98b58963ac56d73e1c5f9be70b80edfbf3428764e5766126c./home/jbergner/anaconda3/python./home/jbergner/anaconda3/python.-m#ipykernel_launcher
Info 2022-06-16 12:07:43: Hiding default kernel spec Python 3 (ipykernel), python
Info 2022-06-16 12:07:43: Kernel python376jvsc74a57bd07356241a38552ec98b58963ac56d73e1c5f9be70b80edfbf3428764e5766126c matches Python 3.9.12 64-bit ('base': conda) based on metadata path.
Info 2022-06-16 12:07:43: Kernel python389jvsc74a57bd031f2aee4e71d21fbe5cf8b01ff0e069b9275f58929596ceb00d14d90e3e16cd6 matches Python 3.6.8 64-bit based on metadata path.
Info 2022-06-16 12:08:34: Execute Cells request 1 0
Info 2022-06-16 12:08:34: Execute Cell 0 file:///mnt/labnas/jbergner/grain_trajectories/twhya/plotting/Save_traj_Rob.ipynb
Info 2022-06-16 12:08:34: Starting Notebook in kernel.ts id = .jvsc74a57bd07356241a38552ec98b58963ac56d73e1c5f9be70b80edfbf3428764e5766126c./home/jbergner/anaconda3/python./home/jbergner/anaconda3/python.-m#ipykernel_launcher
Info 2022-06-16 12:08:34: Checking for server existence.
Info 2022-06-16 12:08:34: Checking for server usability.
Info 2022-06-16 12:08:34: Server not usable (should ask for install now)
Error 2022-06-16 12:08:34: Failed to get activated conda env variables for base: /home/jbergner/anaconda3/bin/python
Error 2022-06-16 12:08:34: Failed to get activated conda env variables for base: /home/jbergner/anaconda3/bin/python
Info 2022-06-16 12:08:34: Process Execution: > ~/anaconda3/bin/python -c "import jupyter"
> ~/anaconda3/bin/python -c "import jupyter"
Info 2022-06-16 12:08:34: Process Execution: > ~/anaconda3/bin/python -c "import notebook"
> ~/anaconda3/bin/python -c "import notebook"
Error 2022-06-16 12:08:34: failed to create INotebook in kernel, UI Disabled = undefined [o [Error]: Jupyter cannot be started. Error attempting to locate jupyter: Running cells with 'Python 3.9.12 64-bit ('base': conda)' requires jupyter and notebook.
	at S.startServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:936180)
	at async S.createServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:935464)
	at async c.getNotebook (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:985092)
	at async p.getOrCreateNotebook (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:932939)
	at async /home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:24:81978] {
  category: 'jupyterinstall',
  action: 'https://aka.ms/pyaiinstall',
  actionTitle: 'Get more help'
}
Error 2022-06-16 12:08:34: failed to start INotebook in kernel, UI Disabled = undefined [o [Error]: Jupyter cannot be started. Error attempting to locate jupyter: Running cells with 'Python 3.9.12 64-bit ('base': conda)' requires jupyter and notebook.
	at S.startServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:936180)
	at async S.createServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:935464)
	at async c.getNotebook (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:985092)
	at async p.getOrCreateNotebook (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:932939)
	at async /home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:24:81978] {
  category: 'jupyterinstall',
  action: 'https://aka.ms/pyaiinstall',
  actionTitle: 'Get more help'
}
Error 2022-06-16 12:08:34: Failed to execute cells in CellExecutionQueue [o [Error]: Jupyter cannot be started. Error attempting to locate jupyter: Running cells with 'Python 3.9.12 64-bit ('base': conda)' requires jupyter and notebook.
	at S.startServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:936180)
	at async S.createServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:935464)
	at async c.getNotebook (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:985092)
	at async p.getOrCreateNotebook (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:932939)
	at async /home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:24:81978] {
  category: 'jupyterinstall',
  action: 'https://aka.ms/pyaiinstall',
  actionTitle: 'Get more help'
}
Info 2022-06-16 12:08:34: Cancel pending cells
Error 2022-06-16 12:08:34: Failed to get activated conda env variables for base: /home/jbergner/anaconda3/bin/python
Error 2022-06-16 12:08:34: Failed to get activated conda env variables for base: /home/jbergner/anaconda3/bin/python
Info 2022-06-16 12:08:34: Process Execution: > ~/anaconda3/bin/python -c "import jupyter"
> ~/anaconda3/bin/python -c "import jupyter"
Info 2022-06-16 12:08:34: Process Execution: > ~/anaconda3/bin/python -c "import notebook"
> ~/anaconda3/bin/python -c "import notebook"
Error 2022-06-16 12:08:36: DataScience Error [o [Error]: Jupyter cannot be started. Error attempting to locate jupyter: Running cells with 'Python 3.9.12 64-bit ('base': conda)' requires jupyter and notebook.
	at S.startServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:936180)
	at async S.createServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:935464)
	at async c.getNotebook (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:985092)
	at async p.getOrCreateNotebook (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:66:932939)
	at async /home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2021.10.1101450599/out/client/extension.js:24:81978] {
  category: 'jupyterinstall',
  action: 'https://aka.ms/pyaiinstall',
  actionTitle: 'Get more help'
}

Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
conda 4.13.0
Running Jupyter locally or remotely?
Remote

@jbergner Looks like you are on a rather old version of the Jupyter extension. Could you try updating to the newest version and see if you are still reproing the issue?

Thanks @IanMatthewHuff -- I updated the Jupyter extension and am getting a similar error still:
info 16:42:48.504: Execute Cell 0 /mnt/labnas/jbergner/grain_trajectories/twhya/plotting/Save_traj_Rob.ipynb
info 16:42:48.504: Starting Jupyter Session id = 'startUsingPythonInterpreter:.jvsc74a57bd07356241a38552ec98b58963ac56d73e1c5f9be70b80edfbf3428764e5766126c./home/jbergner/anaconda3/python./home/jbergner/anaconda3/python.-m#ipykernel_launcher' (Python Path: /home/jbergner/anaconda3, EnvType: Conda, EnvName: 'base', Version: 3.9.12) for '/mnt/labnas/jbergner/grain_trajectories/twhya/plotting/Save_traj_Rob.ipynb' (disableUI=false)
info 16:42:48.507: Checking for server existence.
info 16:42:48.508: Checking for server usability.
info 16:42:48.508: Server not usable (should ask for install now)
info 16:42:48.568: Process Execution: > ~/anaconda3/bin/python -c "import jupyter"

~/anaconda3/bin/python -c "import jupyter"
info 16:42:48.576: Process Execution: > ~/anaconda3/bin/python -c "import notebook"
~/anaconda3/bin/python -c "import notebook"
warn 16:42:48.593: Error occurred while trying to start the kernel, options.disableUI=false [i [Error]: Jupyter cannot be started. Error attempting to locate jupyter: Running cells with 'Python 3.9.12 ('base')' requires jupyter and notebook package.
at b.startServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:411047)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async b.createServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:410167)
at async l.connect (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:387351)
at async f.create (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:407907)
at async m.createJupyterSession (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:478153)
at async m.start (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:472173)
at async Function.wrapKernelMethodImpl (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:499766)] {
category: 'jupyterinstall'
}
warn 16:42:48.594: Kernel Error, context = start [i [Error]: Jupyter cannot be started. Error attempting to locate jupyter: Running cells with 'Python 3.9.12 ('base')' requires jupyter and notebook package.
at b.startServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:411047)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async b.createServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:410167)
at async l.connect (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:387351)
at async f.create (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:407907)
at async m.createJupyterSession (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:478153)
at async m.start (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:472173)
at async Function.wrapKernelMethodImpl (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:499766)] {
category: 'jupyterinstall'
}
info 16:42:48.645: Process Execution: > ~/anaconda3/bin/python -c "import jupyter"
~/anaconda3/bin/python -c "import jupyter"
info 16:42:48.653: Process Execution: > ~/anaconda3/bin/python -c "import notebook"
~/anaconda3/bin/python -c "import notebook"
info 16:42:50.132: Dispose Kernel '/mnt/labnas/jbergner/grain_trajectories/twhya/plotting/Save_traj_Rob.ipynb' associated with '/mnt/labnas/jbergner/grain_trajectories/twhya/plotting/Save_traj_Rob.ipynb'
error 16:42:50.133: Error in execution [i [Error]: Jupyter cannot be started. Error attempting to locate jupyter: Running cells with 'Python 3.9.12 ('base')' requires jupyter and notebook package.
at b.startServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:411047)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async b.createServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:410167)
at async l.connect (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:387351)
at async f.create (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:407907)
at async m.createJupyterSession (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:478153)
at async m.start (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:472173)
at async Function.wrapKernelMethodImpl (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:499766)] {
category: 'jupyterinstall'
}
error 16:42:50.133: Error in execution (get message for cell) [i [Error]: Jupyter cannot be started. Error attempting to locate jupyter: Running cells with 'Python 3.9.12 ('base')' requires jupyter and notebook package.
at b.startServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:411047)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async b.createServer (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:410167)
at async l.connect (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:387351)
at async f.create (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:407907)
at async m.createJupyterSession (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:478153)
at async m.start (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:472173)
at async Function.wrapKernelMethodImpl (/home/jbergner/.vscode-server/extensions/ms-toolsai.jupyter-2022.5.1001601848/out/extension.node.js:2:499766)] {
category: 'jupyterinstall'
}

I also experience the same error over and over again. First the kernel slows down, then the connection drops, I restart vscode, pull up the remote-ssh, connect to the running jupyter-lab server, assign the running kernel to the respective notebook and nothing happens. Neither can I interrupt nor restart the kernel and the only solution is to kill the ipykernel subprocess on the remote machine. If I am training any models that requires hours of CPU/GPU time, and whose pre-processing steps take several minutes, even if I can save the progress along the way, relying on vscode to manage it seems to have been a big mistake.
I sincerely expected more from vscode, and I am starting regretting to have converted my workflow from jupyter-lab to it.


DSR execution doesn't show until you logout and log back in as admin

When you make a bunch of subject requests, it won't show up on the admin console in the privacy center until you exit the admin console and then log back in.
I'm putting my docker-compose.yaml in the comments

services:
############################################################
FidesCTL and FidesCLS - For datamapping and hyper-speed classification
############################################################
fides-poc:
image: ethyca/fidesctl-plus:1.1.3
container_name: fides-poc
#healthcheck:
#  test:
#   [
#    "CMD",
#      "curl",
#     "-f",
#     "http://<IP_ADDRESS>:8080/api/v1/health"
#   ]
# interval: 15s
# timeout: 5s
# retries: 5
depends_on:
fidesctl-db:
condition: service_healthy
application_db:
condition: service_healthy
expose:
- 8080 # Fides WebUI
- 8765 # Fidescls  API
ports:
- "8080:8080"
- "8765:8765"
volumes:
- type: bind
source: .fides
target: /fidesctl_plus/.fides
read_only: False
fidesctl-db:
image: postgres:12
healthcheck:
test: [ "CMD-SHELL", "pg_isready -U postgres" ]
interval: 15s
timeout: 5s
retries: 5
volumes:
- postgres:/var/lib/postgresql/data
expose:
- 5432
ports:
- "5432:5432"
environment:
POSTGRES_USER: "postgres"
POSTGRES_PASSWORD: "fidesctl"
POSTGRES_DB: "fidesctl"
This is the watchdog service that emulates a CI/CD integrating FidesCTL and FidesOps.
FidesCTL creates the systems and datasets. Fidesops uses part of this for DSRs.
This watches the .fides folder for changes, and then HTTP "POST"s those changes over to FidesOps.
This is one of the many ways you can integrate us into your pipelines
fidesbridge:
image: fidesbridge
build:
context: ./containers/fidesbridge
depends_on:
#fides-poc:
# condition: service_healthy
fidesops-webserver:
condition: service_healthy
volumes:
- type: bind
source: .fides
target: /.fides
read_only: False
environment:
# Note - the environment variables below should match the database you are performing
# the DSR against.. Note - in our case, it's our sample web application database all the way on
# the bottom of this docker-compose file.
WEBAPP_POSTGRES_USER: "postgres"
WEBAPP_POSTGRES_PASSWORD: "applicationdb"
WEBAPP_POSTGRES_DB: "applicationdb"
WEBAPP_POSTGRES_PORT: "6432"
WEBAPP_POSTGRES_SERVER: "host.docker.internal"
FIDESOPS_CONNECTION_KEY: "SampleWebApplication"  # This is the logical name of the system we are connecting above
FIDESOPS_DATASET_YML: "application_db_dataset.yml" # This is outputted by the POC guide, however, this can match whatever you name the file
  # Note - The below are the configs to the FidesOps server.
  # This should match whats in ./containers/fidesops/fidesops.toml
  FIDESOPS_URL: "http://host.docker.internal:8081"
  FIDESOPS_CLIENT_ID: "fidesopsadmin"
  FIDESOPS_CLIENT_SECRET: "fidesopsadminsecret"
  FIDESOPS_USERNAME: "root_user"
  FIDESOPS_PASSWORD: "Testpassword1!"

#########################################################
Fidesops and Privacy center - Used to Orchestrate DSRs
#########################################################
fidesops-webserver:
image: ethyca/fidesops:1.8.1
# profiles:
#   - donotstart
depends_on:
- fidesops-db
- fidesops-redis
expose:
- 8081
healthcheck:
test: [ "CMD", "curl", "-f", "http://<IP_ADDRESS>:8081/health" ]
interval: 30s
timeout: 10s
retries: 6
start_period: 1s
ports:
- "8081:8081"
volumes:
#  Used to get the fidesops.toml for config. We will use env var to map it to this directory
- type: bind
source: ./containers/fidesops
target: /fidesops/customConfig
read_only: False
environment:
- FIDES__CONFIG_PATH=/fidesops/customConfig
- FIDESOPS__SECURITY__LOG_LEVEL=debug
- FIDESOPS__HOT_RELOAD=True
fidesops-db:
image: postgres:12
# profiles:
#     - donotstart
volumes:
- fidesops-db:/var/lib/postgresql/data/pgdata
environment:
- PGDATA=/var/lib/postgresql/data/pgdata
- POSTGRES_USER=postgres
- POSTGRES_PASSWORD=216f4b49bea5da4f84f05288258471852c3e325cd336821097e1e65ff92b528a
- POSTGRES_DB=fidesops
expose:
- 5432
ports:
- "7432:5432"
deploy:
placement:
constraints:
- node.labels.fidesops.app-db-data == true
fidesops-redis:
image: "redis:6.2.5-alpine"
# profiles:
#     - donotstart
command: redis-server --requirepass testpassword
environment:
- REDIS_PASSWORD=testpassword
expose:
- 6379
ports:
- "<IP_ADDRESS>:6379:6379"
fidesops-worker:
image: ethyca/fidesops:1.8.1
# profiles:
#     - donotstart
command: fidesops worker
depends_on:
fidesops-redis:
condition: service_started
restart: always
volumes:
#  Used to get the celery.toml for config. We will use env var to map it to this directory
- type: bind
source: ./containers/fidesops
target: /fidesops/customConfig
read_only: False
- ./containers/fides_uploads:/fidesops/fides_uploads
environment:
- FIDES__CONFIG_PATH=/fidesops/customConfig
- FIDESOPS__EXECUTION__CELERY_CONFIG_PATH=/fidesops/customConfig
- FIDESOPS__SECURITY__LOG_LEVEL=debug
fidesops-privacy-center:
image: ethyca/fides-privacy-center:1.8.1
depends_on:
- fidesops-webserver
# profiles:
#     - donotstart
restart: always
volumes:
#  Used to get the celery.toml for config. We will use env var to map it to this directory
- type: bind
source: ./containers/fides-privacy-center-customizations/config
target: /app/config
read_only: False
expose:
- 3000
ports:
- "3000:3000"
################################################
Webapplication to simulate your application!
################################################
application_db:
image: applicationdb
container_name: applicationdb
healthcheck:
test: [ "CMD-SHELL", "pg_isready -U postgres" ]
interval: 15s
timeout: 5s
retries: 5
build:
context: ./containers/applicationdb
ports:
- "6432:5432"
environment:
POSTGRES_USER: "postgres"
POSTGRES_PASSWORD: "applicationdb"
POSTGRES_DB: "applicationdb"
webapp:
image: webapp-ecommerce
container_name: webapp-ecommerce
depends_on:
application_db:
condition: service_healthy
build:
context: ./containers/webapp
ports:
- "2000:2000"
# Point this to our application_db noted above
environment:
POSTGRES_URL: "postgresql://postgres:applicationdb@host.docker.internal:6432/applicationdb"
volumes:
postgres: null
applicationdb: null
fidesops-worker: null
fidesops-db: null

I can reproduce this pretty reliably. What happens is that if you have a valid session object in your browser from a different instance of Fides, we don't handle the 403 error gracefully in the UI and force a client-side logout:

I think the specific steps to reproduce this are:

Run nox -s test_env to setup the local test environment and open the Admin UI
Login with the test user (fidestest // Atestpassword1!)
Shutdown the test environment
Run nox -s test_env to get a new test environment and open the Admin UI
Check the console for session errors (see the 403 in the screenshot above)

I was able to reproduce by directly deleting the client row from the database, which is a bit easier to work with wiping the whole environment.
One thing this ticket highlights that by using localStorage instead of sessionStorage, we are choosing to authenticate and cache data in a way that never expires. The user has to explicitly log out, and our javascript has to run, for the data to be cleared.


P6 [Q4] Develop functionality for users to report Groups

Description
Give ability to flag any other content type than Account, Post and Comment
Detail
Provide ability for user to “Flag“ Components, Groups (if existing) and Chat (if existing) for moderation no matter where the object is displayed on the platform (e.g. feed, search etc…).
Flagging the object should enqueue the content into our current moderation queue (https://near.org/mob.near/widget/Flagged.Feed)
Similar to when reporting posts or comments we should also display a confirmation message to users that the content has being flagged and will be reviewed.
When flagging a post or comment we usually hide the content from the reporter’s view. Once the reporter report an object, offer them the possibility to also hide the object so that they can’t interact with it anymore.
### Tasks
- [ ] https://github.com/near/Pagoda-Roadmap/issues/27

Error


Provide a selectable list of reasons when requesting deletion of a file[WIP]

Provide a selectable list of reasons when requesting deletion of a file
Fixes # 1768
Description (required)
Added reasons in drop down menu list
Need to work on UI
Tests performed (required)
Tested on ProdDebug.
Screenshots showing what changed (optional)
{Only for user interface changes, otherwise remove this section. See how to take a screenshot}
Note: Please ensure that you have read CONTRIBUTING.md if this is your first pull request.

Codecov Report

Merging #1824 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1824      +/-   ##
=========================================
- Coverage    3.63%   3.61%   -0.02%
=========================================
  Files         192     193       +1
  Lines        9806    9846      +40
  Branches      863     865       +2
=========================================
  Hits          356     356
- Misses       9425    9465      +40
  Partials       25      25

Impacted Files
Coverage Δ

...fr/free/nrw/commons/media/MediaDetailFragment.java
0% <0%> (ø)
:arrow_up:

...java/fr/free/nrw/commons/delete/ReasonBuilder.java
0% <0%> (ø)

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 2fdcddd...de52177. Read the comment docs.

@tanvidadu This might be helpful https://github.com/commons-app/apps-android-commons/issues/1943#issuecomment-435588982

Thanks @maskaravivek !

The PR works perfectly for me. Happy to merge it once one more person is able to test it.
I nominated 2 files for deletion using this PR, selecting different reasons.
https://commons.wikimedia.org/wiki/File:Elephant_6.jpg
https://commons.wikimedia.org/wiki/File:Elephant_7.jpg


Pull request to update OCI compute-hardware

Created new content for OCI compute-hardware: OCI Compute shape naming convention. Also replaced confidential compute link with public link (it was pointing to Confluence).

Created new content for OCI compute-hardware: OCI Compute shape naming convention. Also replaced confidential compute link with public link (it was pointing to Confluence).

Created new content for OCI compute-hardware: OCI Compute shape naming convention. Also replaced confidential compute link with public link (it was pointing to Confluence).

Created new content for OCI compute-hardware: OCI Compute shape naming convention. Also replaced confidential compute link with public link (it was pointing to Confluence).

Approved


Add ansys installation information in the docs

Add documentation to clarify ADR installation via ansys installer

Codecov Report

Merging #67 (86943ac) into main (ccec2ad) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #67   +/-   ##
=======================================
  Coverage   76.51%   76.51%
=======================================
  Files          16       16
  Lines        4837     4837
  Branches     1026     1026
=======================================
  Hits         3701     3701
  Misses        796      796
  Partials      340      340


Bug: render Parser default value with empty array

PHP Version
7.4
CodeIgniter4 Version
4.2.6
CodeIgniter4 Installation Method
Composer (using codeigniter4/appstarter)
Which operating systems have you tested for this bug?
Windows
Which server did you use?
apache
Database
MySQL 5.7
What happened?
See comment #6550, empty array cannot parsing default value.
Steps to Reproduce
$parser = new Parser($this->config, $this->viewsDir, $this->loader);

$obj = (object) '';

$data = [
      'value1' => 0.0,
      'value2' => [],
      'value3' => $obj->scalar,
      'value4' => false,
];

$template = '{ value1|default(foo) } { value2|default(bar) } { value3|default(baz) } { value4|default(john) }';
$parser->setData($data);

echo $parser->renderString($template);

Expected Output
Result is foo bar baz john
Anything else?
No response

What do you want to show when you set an array to a variable ?
Or why do you need to set an array?

That's odd! empty([]) is definitely true - I wonder if this is somehow getting interpolated as empty['']) (which is false)? I think that we still allow array types here, and address this as a bug in another PR.

@MGatner say need still allow array types. When testing with [] or [''] get result error.

An array cannot be converted to a string. So we cannot show an array in the web page.
Or it is converted to Array with PHP warning if we use PHP view.
I don't see the use case of an array.

    public function testDefaultManyValue()
    {
        $parser = new Parser($this->config, $this->viewsDir, $this->loader);

        $obj = (object) '';

        $data = [
            'value1' => 0.0,
            'value2' => [['test' => '']],
            'value3' => $obj->scalar,
            'value4' => false,
        ];

        $template = '{ value1|default(foo) } {value2}{ test|default(bar) }{/value2} { value3|default(baz) } { value4|default(john) }';

        $parser->setData($data);
        $this->assertSame('foo bar baz john', $parser->renderString($template));
    }

With this its OK, but if use case array from database is []?

By the way, when 0.0 comes, why do we return the default value?

With this its OK, but if use case array from database is []?

Do you mean the value of test is []?
In that case, what value will come when it is not empty array?

No, i mean what if 'data' => []
    public function testDefaultArrayValue()
    {
        $parser = new Parser($this->config, $this->viewsDir, $this->loader);

        $data = [
            'data' => [
                [
                    'field_no'    => 1,
                    'field_title' => 'Mouse',
                    'field_amount'=> 20,
                ],
                [
                    'field_no'    => 2,
                    'field_title' => 'Keyboard',
                    'field_amount'=> 44,
                ],
            ],
        ];

        $template = '{data}[{ field_no|default(bar) }] { field_title|default(bar) } = { field_amount|default(bar) }\n{/data}';

        $parser->setData($data);
        $this->assertSame('[1] Mouse = 20\n[2] Keyboard = 44\n', $parser->renderString($template));
    }

{blog_entries} is []?
Do you want {blog_entries|default(No data available)}?

Yes, like that


remove unused import

remove unused import in TBase.

FWIW, the impsort-maven-plugin is great for sorting imports, and removing unused ones.

FWIW, the impsort-maven-plugin is great for sorting imports, and removing unused ones.

yes, convenient tool. I just think that the source code will more readable.

.


Error 2: The system cannot find the file specified

I tried to install the Agent in Windows 10 Enterprise and I received the following Error
"Error: Failed to install Microsoft Azure Recovery Services Agent installation has failed
Problem : 2: The system cannot find the file specified"
Can you help on this?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c04356b4-e2a0-c095-5f47-b7fc1d2b574f
Version Independent ID: 72900c81-5858-bb03-06fb-4af272317f20
Content: Use Azure Backup agent to back up files and folders
Content Source: articles/backup/backup-configure-vault.md
Service: backup
GitHub Login: @markgalioto
Microsoft Alias: markgal

@theSARMproject
Thanks for your feedback! We will investigate and update as appropriate.

@theSARMproject
Closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


add Starwhale

What is this tool for?
Starwhale is an MLOps/LLMOps platform that brings efficiency and standardization to machine learning operations. It streamlines the model development liftcycle, enabling teams to optimize their workflows around key areas like model building, evaluation, release and fine-tuning.

What's the difference between this tool and similar ones?

Starwhale meets diverse deployment needs with three flexible configurations: Standalone, Server and Cloud.
Starwhale abstracts Model, Runtime and Dataset as first-class citizens - providing the fundamentals for streamlined operations.

Starwhale Model is a standard format for packaging machine learning models that can be used for various purposes, like model fine-tuning, model evaluation, and online serving.
Starwhale Dataset offers efficient data storage, loading, and visualization capabilities, making it a dedicated data management tool tailored for the field of machine learning and deep learning.
Starwhale Runtime aims to provide a reproducible and sharable running environment for python programs. You can easily share your working environment with your teammates or outsiders, and vice versa.

Starwhale further delivers tailored capabilities for common workflow scenarios including:

Models Evaluation - Implement robust, production-scale evaluations with minimal coding through the Python SDK.
Live Demo - Interactively assess model performance through user-friendly web interfaces.
LLM Fine-tuning - End-to-end toolchain from efficient fine-tuning to comparative benchmarking and publishing.

Thanks for your contribution! 🎉 👍


Fix linking of python bindings on Mac

Don’t link against python on Mac, and use -undefined dynamic_lookup to allow this.
I believe this fixes #1617, so RDKit works with recent versions of python in the conda defaults channel.
Note: For this to work, boost_python also has to be linked in this way. I think this may be the case since around boost 1.59?

@bp-kelley : this fixes the compile problems I was having with recent versions of conda on the Mac so, though I don't really understand why it helps, I think it makes sense to merge.
However, I am still, even with this fix applied, unable to make the conda-build stuff work.

Part of the problem is that, at some point, conda switched over to statically linked python libraries I think.
This flag prevents symbols from being found twice.
https://stackoverflow.com/questions/48289858/fatal-error-in-extension-pythreadstate-get-no-current-thread-when-using-swig-w
These are the errors I’ve seen when compiling.  I hadn’t tried Matt’s approach to not linking against python while using the flag.  This may be the correct approach, I’ll check tomorrow.  It may be that we need to build our own boost in addition.

I would really love it if we didn’t need to do our own boost build anymore.

If I can get it to work, I’ll see if we can change the default continuum boost recipe.

This works for me with an up-to-date conda version and the conda-rdkit build setup.
This is really exciting. :-)
@mcs07 : if you don’t manage to get to it, I will add the flags to make it optional as @bp-kelley suggests and do the merge tomorrow.


Error while Peeking first byte

Do you want to request a feature or report a bug?
bug
What did you do?
I deploy traefik 2.0.5 as daemonset(HostNetwork 80 and 443) on alicloud and txcloud，when use LoadBalance on alicloud and txcloud and turn on LoadBalance TCP healthcheck, the Traefik pod has a lot of errors.
I use wireshark to capture packets, loadbalancing uses tcp three-way handshake for health check, and RST is interrupted immediately after checked.
Output of traefik version: (What version of Traefik are you using?)
2.0.5
What is your environment & configuration (arguments, toml, provider, platform, ...)?
k8s
If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
kubectl logs --tail=20 -n traefik -f traefik-4fcs2
time="2019-10-15T01:51:44Z" level=error msg="Error while Peeking first byte: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:61659: read: connection reset by peer"
time="2019-10-15T01:51:44Z" level=error msg="Error while Peeking first byte: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:42823: read: connection reset by peer"
time="2019-10-15T01:51:45Z" level=error msg="Error while Peeking first byte: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:62255: read: connection reset by peer"
time="2019-10-15T01:51:45Z" level=error msg="Error while Peeking first byte: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:51043: read: connection reset by peer"
time="2019-10-15T01:51:49Z" level=error msg="Error while Peeking first byte: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:3104: read: connection reset by peer"
time="2019-10-15T01:51:49Z" level=error msg="Error while Peeking first byte: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:47346: read: connection reset by peer"
time="2019-10-15T01:51:49Z" level=error msg="Error while Peeking first byte: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:33006: read: connection reset by peer"
time="2019-10-15T01:51:50Z" level=error msg="Error while Peeking first byte: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:18426: read: connection reset by peer"
time="2019-10-15T01:51:50Z" level=error msg="Error while Peeking first byte: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:41629: read: connection reset by peer"
time="2019-10-15T01:51:50Z" level=error msg="Error while Peeking first byte: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:37347: read: connection reset by peer"
time="2019-10-15T01:51:50Z" level=error msg="Error while Peeking first byte: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:54091: read: connection reset by peer"
time="2019-10-15T01:51:50Z" level=error msg="Error while Peeking first byte: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:16593: read: connection reset by peer"
time="2019-10-15T01:51:54Z" level=error msg="Error while Peeking first byte: read tcp <IP_ADDRESS>:80-><IP_ADDRESS>:3195: read: connection reset by peer"

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
Issue templates help us help you by providing all necessary information.
Please edit your issue and use the available templates:

Feature request
Bug report

And remember: each time someone ignores the template, a cute little bunny dies.

#SaveTheCuteBunny :heart: :rabbit: :heart:

In case it helps debug/resolve: I got this error trying to view the Traefik Dashboard with proxy protocol enabled on my load balancer.
Still haven't figured out why some apps on k8s don't like the proxy protocol.

who can help me?

Hi @kong62 , your issue seems related to #5297 , but we are not completely sure as we are missing information for reproduction here.
Would you mind switching to our community forum to get help from the community? There is already a topic about this kind of errors as well: https://community.containo.us/t/error-while-peeking-first-byte-connection-reset-by-peer/1918 you might want to add your use case here.
Thanks a lot!


how do you render the chart in "fit" mode by default?

You can use .render().fit() but it makes it look weird because first it renders in the default setting and then it animates into "fit" view.

I don't think that there is an easy way around that.
I personally don't think that it's an issue, looks quite good to my eye
https://stackblitz.com/edit/js-nf6zcx?file=index.html


Fix concurrent map access for clients and inflights causes data race

As per #98 and #96 - a data race was occurring when the primary server routine and client routines attempted to access the client inflight messages map at the same time, causing fatal errors.
The issue was reproduced placing the server under heavy load with inovex/mqtt-stresser, using qos=2 for both the publisher and subscriber (see #98).
This PR fixes the issue by returning reference maps of the original values, values in the case of inflight messages, pointers to clients in the case of the client map.

The inflight messages are never modified by reference once set, so it is reasonable and more cost effective to copy the whole value.
The clients are passed by reference, and have more sophisticated locking mechanisms and isolation.

Profiling the solution before and after show a small but negligible reduction in mallocs. When running the above mentioned stress tests, data races or crashes are detected are no longer detected.
With many thanks to @muXxer for identifying the issue and providing a potential solution in #96 :)
Additionally, this PR increases the size of the inline publishing buffer in light of #95.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

13 of 13 (100.0%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.04%) to 97.843%

Files with Coverage Reduction
New Missed Lines
%

server/server.go
1
96.64%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
2767

Relevant Lines:
2828

💛  - Coveralls


OVS management through Netplan and Libvirt

This PR adds new ways to managed OVS bridges and virtual port through Netplan and Libvirt, on a standalone Seapath machine.

Using Netplan configuration file inventories/netplan_ovs_bridge_example.yaml.j2, it is now possible to create an OVS bridge from Netplan.
Using Libvirt  field, it is now possible to create OVS virtual port directly from Libvirt XML configuration file. The modification adds also the possibility to configure a VLAN.
These modifications are based on the current inventory OVS bridge  syntax.

Can you merge in one commit? This does not justify 4 differents commits...

Can you merge in one commit? This does not justify 4 differents commits...

As the modification are on 3 different files I would prefer to keep this granularity, easier in case of revert and for commit reliability

I find it easier to revert the whole change, and easier to understand the change if its explanation is not split in different commit descriptions. We had a talk about this in maintainers meeting.
1 feature or 1 fix = 1 commit with everything explained in its description (we do not count on the PR description since it not written in git).
@eroussy do you agree?

1 feature or 1 fix = 1 commit with everything explained in its description (we do not count on the PR description since it not written in git). @eroussy do you agree?

Here there are more than 1 feature, no?

if you feel there are different features then multiple commits are fine. I felt that justifying 4 full features with 25 lines changed in 3 files was a bit of a stretch but hey why not.


CUDA_ARCHITECTURES Problem

Hi Community:
when I star to cmake .. in tvm/build, I got this error:
CMake Error in CMakeLists.txt:
CUDA_ARCHITECTURES is empty for target "tvm_runtime_objs".
CMake Error in CMakeLists.txt:
CUDA_ARCHITECTURES is empty for target "tvm".
CMake Error in CMakeLists.txt:
CUDA_ARCHITECTURES is empty for target "tvm_runtime".

Maybe you don't have CUDA installed correctly. Please use https://discuss.tvm.apache.org/ for such question.

CUDA_ARCHITECTURES
But, nvcc -V is right, torch.cuda.is_available() is True
I'm confused.


fix: add a lib.js to export functions without running main

To use this package as a library, I moved the exported functions to lib.js.
This is a continuation of #47

I'd rather #69 be merged first to avoid conflicts.

I rebased your patch to resolve merge conflicts. Thanks!


javascript Waypoint: Manipulate Arrays With push checks for wrong value

The tests for this waypoint seem to be checking for the wrong value.
the prompt instructs to push ["dog",3] onto myArray, which is specified as
var myArray = ["John", 23, ["cat", 2]];
when I add the line myArray.push(["dog", 3]); and run the tests, I get the following error :
myArray should now equal ["John", 23, ["dog", 3]].  Looks like the test is expecting the myArray to be initialized as :
var myArray = ["John", 23];

never mind, seems I accidentally deleted a line of code that popped an element off of myArray before I was supposed to write my code.


[WIP][SPARK-25809][K8S][TEST] New K8S integration testing backends

What changes were proposed in this pull request?
Currently K8S integration tests are hardcoded to use a minikube based backend.  minikube is VM based so can be resource hungry and also doesn't cope well with certain networking setups (for example using Cisco AnyConnect software VPN minikube is unusable as it detects its own IP incorrectly).
This PR Adds a new K8S integration testing backend that allows for using the Kubernetes support in Docker for Desktop.  This is WIP towards generalising to be able to run the integration tests against an arbitrary Kubernetes cluster.
To Do:

[ ] General Kubernetes cluster backend
[ ] Documentation on Kubernetes integration testing

How was this patch tested?
Ran integration tests with Docker for Desktop and all passed:

Suggested Reviewers: @ifilonenko @srowen

Can one of the admins verify this patch?

@srowen Yes there are a lot of assumptions made by the integration tests that are not documented anywhere and I figured out by digging in the code and POMs.
Broadly speaking right now to run integration tests you need the following:

A runnable distribution of Spark built
minikube installed, configured with at least 4 CPUs and 8 GB memory and started

Probably the next thing I will do tomorrow on this is to improve the documentation.  There is a README.md in the integration testing module but it omits various details I have encountered working with these recently.

@rvesse this capability was in the old integration tests repo here.
In our fork we have merged  that part back, can we add that too? I find it really useful to test real platforms like Openshift etc.

@rvesse also the following memory limit works for me:
minikube config set memory 4096 so maybe g its too much.

@skonto Yep, I plan to do that tomorrow
At least for my minikube instance I found 4g insufficient and a couple of tests would fail because their pods didn't get scheduled.  8g is probably over allocating, somewhere in-between likely works also

@rvesse I use no vm:
sudo -E ./minikube start --vm-driver=none

@ifilonenko I have done the generalisation today since it was fairly trivial and it actually resolves a number of concerns about the first pass implementation
@skonto I have restored the cloud backend as requested, I ended up having two separate cloud backends.  One using the original code that simply takes a master URL and another that takes a desired K8S context and auto-configures itself from the K8S config file and the context specified.

Ran successfully against one of our dev K8S clusters today:

Will continue onto testing against one of our larger production clusters

@rvesse I want to take back my comment on bumping the version of the fabric8 client in the same PR. Based on the discussion so far, it seems more appropriate to do that in a separate PR, like in #22820. Can you revert the changes to bump the version? Sorry about that.

@liyinan926 I will rebase and squash appropriately once PR #22820 is merged

Did a bunch more testing on our internal K8S clusters today after rebasing this onto master. I am now happy that this is ready for final review and merging so I have removed the [WIP] tag

test this please

Test build #98277 has started for PR 22805 at commit 41af220.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-make-spark-distribution-unified/4636/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-make-spark-distribution-unified/4636/

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4636/
Test FAILed.

retest this please

Test build #98279 has started for PR 22805 at commit 41af220.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-make-spark-distribution-unified/4638/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4638/
Test PASSed.

@mccheah since he had some comments.

Test build #98277 has finished for PR 22805 at commit 41af220.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98277/
Test PASSed.

Test build #98279 has finished for PR 22805 at commit 41af220.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/98279/
Test PASSed.

@mccheah I have updated the comment to reference the follow up issue and opened a PR for that as #22904.  Can we go ahead and merge now?

Yes, this can be merged. Going into master now.


Physics system: update link poses if the canonical link pose has been updated

Signed-off-by: Ashton Larkin<EMAIL_ADDRESS>🦟 Bug fix

Related to #871
Fixes https://github.com/ignitionrobotics/ign-physics/issues/264#issuecomment-865123602
Fixes https://github.com/ignitionrobotics/ign-gazebo/pull/258#discussion_r468990490 in Dome (this has already been fixed in Edifice; see https://github.com/ignitionrobotics/ign-gazebo/pull/685)

Summary
As pointed out in https://github.com/ignitionrobotics/ign-physics/issues/264#issuecomment-865123602, if the pose of a model's canonical link changes, then the poses for all other links in this model must be updated (even if these links haven't moved) since these other link poses are given w.r.t. the model whose pose was just updated. I appeared to have removed this functionality in #669 (on accident, of course :slightly_smiling_face:) when working on physics system performance updates, so I am adding it back in this PR. I've also added logic (and test coverage) to support pose updates for canonical links that are not the first link of a model (this has already been fixed in Edifice, but wasn't fixed for Dome yet).
A note about nested models: since nested model support is limited in Dome, I wasn't able to write tests that check for pose updates of nested models in this PR. I have left a TODO note for myself to add this test coverage when we forward port these changes to Edifice. Since we don't have test coverage for nested models yet, we should probably leave #871 open until this PR is forward ported to Edifice and nested model test coverage is included.
It's also worth noting that the physics system in Edifice/Dome has a few differences that were made for performance. This means that we may have some conflicts to resolve when porting this forward - I'm expecting that the implementation for this bug fix in Edifice/Fortress will differ somewhat from the Dome implementation (I can handle merging this bug fix forward once this PR is merged).
Checklist

[x] Signed all commits for DCO
[x] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[x] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge

FYI, https://github.com/ignitionrobotics/ign-physics/issues/264 should be partially fixed by https://github.com/ignitionrobotics/ign-physics/pull/268

@azeey, this is ready for review now. I also left a note in the PR description about not being able to test nested models for this in Dome, as we discussed offline.


build and deploy mdbook

As part of #158 we should also build and deploy our documentation.
This include 2 parts:

backend code documentation
general documentation built using mdbook (see #180)

To build the backend code documentation you can run cargo doc in backend/.
The output can be found in target/doc/.
See here for further reference.
To build the general documentation run mdbook build in the projects root. For that Rust has to be installed as well as mdbook (cargo install mdbook) and the preprocessor (cargo install --version 0.1.0 --git https://github.com/kitzbergerg/mdbook-generate-summary mdbook-generate-summary, you can leave out the version to always get the newest one). This will automatically generate documentation out of our doc/ folder.
The output can be found in book/.
This has to run when code changes in either book.toml or doc/. Note that it might fails so there has to be validation in PRs.
Afterwards the documentation should be deployed and served.
TODOs:

[x] validate backend code doc in PRs (already done)
[ ] build backend code doc (master only)
[ ] deploy and serve backend code doc on a public URL (master only)
[ ] validate general doc in PRs (meaning mdbook build might fail if e.g. there is a missing README.md in a directory)
[ ] build general doc (master only)
[ ] deploy and serve general doc on a public URL (master only)
[ ] describe where documentation can be found in the projects root README (link to public URL). This should include backend code doc, general doc and API doc.

@lukashartl You can start as soon as #180 is merged.
@markus2330 Fell free do add suggestions.

The steps to deploy shouldn't change (apart from maybe an additional preprocessor). So I would prefer adding it to CI as in my opinion there is no real disadvantage and everybody can get a feel for how it behaves.
At least I thought the whole point of merging it now is that we finally have documentation everybody can easily access. Changing it later like reordering items or adding additional doc won't change the behaviour of the book.

So I would prefer adding it to CI as in my opinion there is no real disadvantage and everybody can get a feel for how it behaves.

Of course, everyone would prefer it but there is a big backlog in CI tasks and some of them are very severe and urgent. E.g. we cannot test the seed use case because the data is still not imported, see #211. There are people waiting for the release, which also cannot be done because the release pipeline is not ready. So please be patient here.

At least I thought the whole point of merging it now is that we finally have documentation everybody can easily access.

No, it is about being able to do the PR next week (improving documentation). I don't think it is a problem to run it locally.

@kitzbergerg you said you update the issue a bit, is this already done? What are the changes you propose?

@kitzbergerg you said you update the issue a bit, is this already done? What are the changes you propose?

It is done. There were no real changes, just updating the description so it is easier to follow.


fix: allow double backslashes

Fixes #9

Hey there,
This is a pretty old PR, but i was wondering why it was closed without merge, as the proposed solution works and solve errors in packages using pbxproj-dom
Thanks!


Upgrade to Django 2.2

Backup database before deploying
Upgrade steps in the live container:
root@xxx:/usr/src/ep2020# make install
root@xxx:/usr/src/ep2020# ./scripts/django2_migrate.sh /path/to/sqlite.database

Check the comments in django2_migrate.sh to learn more about the process.
Closes https://github.com/EuroPython/epcon/issues/848

https://github.com/EuroPython/epcon/pull/1240 should be merged first and then change the target branch for this merge to ep2020

This pull request has been reworked into PR #1337 which was merged. The DB fixer script is not part of the PR and is quire different than the one suggested here as it works on the DB itself and fixes its inconsistencies at the root. There is no issue with migrations. Thank you for the effort as it served as the basis for PR #1337.

Thanks for the update @fpierfed. Awesome job with the leet PR #1337 😬 Glad to see this migration is moving forward.


Fix for reconnect causing a full page error

Thank you a lot for contributing to Cosmos Voyager!

Issue

reconnect causes a full page error
❤ Thank you!

full page error does not happen on disconnect / reconnect.
however after first disconnect and reconnect, subsequent disconnect / reconnects fail


Page not found after clicking the Edit button for doc

Browser: Chrome

Steps to Reproduce:

Login to GitHub using account not associated with Microsoft/vscode
Go to https://code.visualstudio.com/docs/languages/identifiers
Click the Edit button

Failure:
Got 404 for the page: https://github.com/Microsoft/vscode-docs/blob/master/docs/languages/identifiers.md

This issue was moved to Microsoft/vscode-docs#910


After providing external configuration file no warnings / errors are shown

Works fine until I provide external configuration file (in this case tried https://raw.githubusercontent.com/arturbosch/detekt/805bb9c10db2e3c2e7d1e8b0110e6cd13a058804/detekt-cli/src/main/resources/default-detekt-config.yml)
Then no more warnings or errors are shown.

Are there any messages in the status bar shown?
Do you use absolute or relative paths?
I'm getting warnings if I enter /home/artur/Repos/detekt/detekt-cli/src/main/resources/default-detekt-config.yml as absolute path.

It might be important here that I'm on Windows 10.
I'm using absolute file path which is provided when I use configuration file explorer (by clicking ...) to choose configuration file. The path is like C:\work\project\backend\detekt.yml I also tried replacing all \ with / but no luck. Also tried different relative alternatives with no luck.
No info in status bar or logs...

Hmm, unfortunately I do not have a windows system to do some tests.
Could you please test normal detekt-cli run with windows specific paths. If this works we can say it is the intellij-plugin for sure.
Next we need to find out how intellij does debugging :)

Please try again with 0.2.0.
We now use the same logic as the cli module uses which got some fixes for windows etc.

Works fine in 0.2.0


az storage account update --default-action does not actually set

Environment summary
2.0.20 nightly pip on ubuntu 16.04 x64

Doc here: https://docs.microsoft.com/en-us/azure/storage/common/storage-network-security?toc=%2Fazure%2Fstorage%2Fblobs%2Ftoc.json
It appears that the --default-action setting is not up networkRuleSet.defaultAction which gets changed by the portal. The other cli commands appear to work fine.
The documentation appears to be incorrect where it references 'networkAcls.defaultAction' and bypass.
If I look at a --debug run - I don't ever actually see it issue any update either, though I may be misreading the output.
I was able to set it with an explicit --set though.

Looks like bypass setting is also affected.

Related to this - how do I use the generic update --set to set a field without it throwing away all the other elements? Or is this something broken server side?
i.e. if do --set networkRuleSet.defaultAction=Deny -- it takes effect, but it discards the bypass and actual rules in that same object.

@tjprescott can you help with the --default-action option? @williexu please take a look the generic set.

The issue with generic update is a bug in the CLI related to trying to leverage a crummy PATCH implementation in storage.  My PR #4853 addresses the issue, but in the future we may opt to stick with just using the PUT.


Fixed cluster list in burger menu having unnecessary horizontal scroll

Summary
Fixes #11809

Changed width setting so that it doesn't need scroller on smaller screens.
Tested on Chrome, Firefox and Safari
Occurred changes and/or fixed issues

N/A
Technical notes summary

N/A
Areas or cases that should be tested

Burger menu:

Check cluster list with burger menu with 1 cluster both open and collapsed. Try different window sizes.
Add more clusters (ie import custom clusters) until it requires virtual scroll in the side menu. Repeat step 1.
No horizontal scroll should be visible, clusters should be able to get pinned, layout should seem reasonable.

Areas which could experience regressions

N/A
Screenshot/Video
https://github.com/user-attachments/assets/e69cff4c-0597-4750-96dc-2e5884c8fd77
https://github.com/user-attachments/assets/fc64477b-a471-408a-bcc2-1efcc2a42356
Checklist

[x] The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
[x] The PR has a Milestone
[x] The PR template has been filled out
[x] The PR has been self reviewed
[x] The PR has a reviewer assigned
[x] The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
[x] The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

Updated css.

Updated css.

Interestingly I can't see the pins touch the edge of TopLevelMenu on my machine unlike your last screenshot, I tried changing the OS's scroll bar setting but still it doesn't happen. Personally I don't like the pins touching the edge, but at the end of the day that's up to the designers.
Besides that I found two issues after this change, tooltip position and pin icons distance from the edge
before:

after:


build: make sure nfs-utils is installed

Ceph is minimizing their container-images, which can cause the
nfs-utils package to be dropped. As Ceph-CSI supports mounting NFS, it
needs the /sbin/mount.nfs executable, so install the package (or a
no-op if it is installed already).
See-also: https://rook-io.slack.com/archives/C46Q5UC05/p1699188662893109
Signed-off-by: Niels de Vos<EMAIL_ADDRESS>

I think its better we run the entire ci just to be sure nothing breaks with this change.

@Mergifyio queue


Link setting error on homepage (index.md index.html)

When building a webpage using mkdocs-material and using the mkdocs-static-i18n plugin to set multiple language selection functions, the link settings on the homepage (index.md index.html) are incorrect

Hello @RonaldLN
This is because you are missing the site_url configuration in your mkdocs.yml file.
You should add: site_url: https://ronaldln.github.io/MyPamphlet

Hello @RonaldLN
This is because you are missing the site_url configuration in your mkdocs.yml file.
You should add: site_url: https://ronaldln.github.io/MyPamphlet

oh, it works, thanks you very much!! @ultrabug  😆


the guide is unavailable

Hi, the link to the "Test Lab Guide: Demonstrate DirectAccess Single Server Setup with Mixed IPv4 and IPv6" is not functioning.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4c8a4bbf-7d3a-58a5-2480-4f4cbcbc7ddc
Version Independent ID: 8b20ba72-23fe-eb4a-de0e-03c18866ce65
Content: STEP 1 Complete the DirectAccess Configuration
Content Source: WindowsServerDocs/remote/remote-access/directaccess/tlg-multisite/STEP-1-Complete-DirectAccess-Configuration.md
Product: windows-server-threshold
GitHub Login: @shortpatti
Microsoft Alias: pashort

@Pelago, try the link again.  I've tested the same link from other documents and it takes me to a download page.
Closing. Cannot reproduce.

it does not still work from Sweden.. i get this message when following the link..
https://go.microsoft.com/fwlink/p/?LinkId=237004
a pritty Picture of an helicopter in Blue and the text
We're sorry, this download is no longer available.
Perhaps one of the following links will help you find what you need.
Suggested for Windows
Get Windows 10
Get apps for Windows and Windows Phone
Microsoft Update
Suggested for Office
Try Office 365 for free
Buy Office for PC, Mac, and other devices
Download Center
Download Center home
Windows downloads

it does not matter if I use EDGE, Chrome, Firefox opera or IE11 browsers...

Hi @Pelago , can you access this URL?
https://www.microsoft.com/en-us/download/details.aspx?id=29031

Yes! thankyou
Patrik Lilja,
CEO
<EMAIL_ADDRESS>
[cid:image002.jpg@01CE269E.64BDC650]sip:patrik.lilja@pelam.com[cid:image003.jpg@01CE269E.64BDC650]tel:+46706000401[cid:image004.jpg<EMAIL_ADDRESS>Pelam Engineering AB, Box 10158, SE43422, Kungsbacka, Sweden. S-board +4630028954

This e-mail, including any attached files, may contain confidential and privileged Information for the sole use of the intended recipient(s). Any review, use, by others is strictly prohibited. If you are not the Intended recipient (or authorised to receive information for the recipient), please contact the sender by reply e-mail and delete all copies of this message. Thank you.
From: Corey Plett<EMAIL_ADDRESS>Sent: den 23 oktober 2018 00:10
To: MicrosoftDocs/windowsserverdocs<EMAIL_ADDRESS>Cc: Patrik Lilja<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windowsserverdocs] the guide is unavailable (#1634)
Hi @Pelagohttps://github.com/Pelago , can you access this URL?
https://www.microsoft.com/en-us/download/details.aspx?id=29031
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windowsserverdocs/issues/1634#issuecomment-432008386, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMMk61PrZvSXt3419ZhKAK676euUKLgtks5unkIigaJpZM4XXG7D.

But that was for server 2012 and I expected 2016
As per info on page https://docs.microsoft.com/en-us/windows-server/remote/remote-access/directaccess/tlg-multisite/step-1-complete-directaccess-configuration
Patrik Lilja,
CEO
<EMAIL_ADDRESS>
[cid:image002.jpg@01CE269E.64BDC650]sip:patrik.lilja@pelam.com[cid:image003.jpg@01CE269E.64BDC650]tel:+46706000401[cid:image004.jpg<EMAIL_ADDRESS>Pelam Engineering AB, Box 10158, SE43422, Kungsbacka, Sweden. S-board +4630028954

This e-mail, including any attached files, may contain confidential and privileged Information for the sole use of the intended recipient(s). Any review, use, by others is strictly prohibited. If you are not the Intended recipient (or authorised to receive information for the recipient), please contact the sender by reply e-mail and delete all copies of this message. Thank you.
From: Corey Plett<EMAIL_ADDRESS>Sent: den 23 oktober 2018 00:10
To: MicrosoftDocs/windowsserverdocs<EMAIL_ADDRESS>Cc: Patrik Lilja<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windowsserverdocs] the guide is unavailable (#1634)
Hi @Pelagohttps://github.com/Pelago , can you access this URL?
https://www.microsoft.com/en-us/download/details.aspx?id=29031
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windowsserverdocs/issues/1634#issuecomment-432008386, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMMk61PrZvSXt3419ZhKAK676euUKLgtks5unkIigaJpZM4XXG7D.

Yes, it works for both 2012 and 2016.

Thanks!
Patrik Lilja,
From: Patti Short<EMAIL_ADDRESS>Sent: den 23 oktober 2018 00:30
To: MicrosoftDocs/windowsserverdocs<EMAIL_ADDRESS>Cc: Patrik Lilja<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windowsserverdocs] the guide is unavailable (#1634)
Yes, it works for both 2012 and 2016.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windowsserverdocs/issues/1634#issuecomment-432013894, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMMk62GZNt5WejBAS8wMnNI6BWy0D6Ufks5unkbsgaJpZM4XXG7D.


How to edit a post?

Is there a way to edit a post that's already published?

You currently can only publish an article as a new draft. As far as I know, the Medium API does not allow to update a post. Usually I publish the piece as a draft and fix small formatting issues within the medium web editor before going live.

Well then mediums API is garbage haha. Maybe we can tap into something unofficial.


Deid 1765

What's Changed?
Added new objects, routes and functions to work with the reidentify text feature
PR Checklist

[x] Updated unit tests
[x] Ran unit tests

@zsolt-pai absolutely fair! lol
But I will also add that the similarity in how we've named everything is contributing the issue more than the case format is :D


Offer recommended config with JSX runtime

I was about to recommend usage of the jsx-runtime config, but then I noticed that it actually extends the all config, and not recommended. If this needs to be separate for some reason, we should at least offer a config that has the recommended options with JSX runtime compatibility.

The "recommended" config is poorly named and due to semver restrictions, doesn't actually match what's recommended (the airbnb config does, and is what's actually recommended).
If we ever have a semver-major, we'd likely delete the recommended config entirely.

Can we document it as deprecated instead?

Do note that the all config doesn't actually enable any of the rules, and that the jsx-runtime config overwrites rules from the all config - so that it literally does nothing except disable those two rules, so there's no reason not to recommend it :-)
As for deprecating the recommended config, I suppose we could, but it'd just be docs anyways, and most people use this plugin via the airbnb config anyways. What do you suggest?

If maintenance effort is going to be focused on Airbnb, I guess it's better to recommend that here and document the old configs as deprecated.

It's unclear if that will be the case in the future, it's just true at the moment. The main issue is that conflating the semver of a config with the semver of rules is problematic (much like when a package ships both types and JS), and so it's better for them to be separate packages.
I think longer term, i'd probably make the react configs a separate package from the rules, but that's a ways off.


GYM output filename is not correct.

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I recently update fastlane to the last version (2.71.0).
It seems that gym doesn't create an IPA with the right GYM_OUTPUT_NAME.
If I have this in my .env file :
GYM_OUTPUT_NAME='app.ipa'
IOS_IPA_PATH='./dist/app.ipa'

Then, the output file is named : app.api.api and the last version is not deploy on hockey app.
I have the impression that '.ipa' is no longer remove from the GYM_OUTPUT_NAME when gym generate the IPA file of my app.
Environment
| Key                         | Value                                       |
| --------------------------- | ------------------------------------------- |
| OS                          | 10.13.2                                     |
| Ruby                        | 2.3.4                                       |
| Bundler?                    | true                                        |
| Git                         | git version 2.14.3 (Apple Git-98)           |
| Installation Source         | ~/.rvm/gems/ruby-2.3.4/bin/fastlane         |
| Host                        | Mac OS X 10.13.2 (17C88)                    |
| Ruby Lib Dir                | ~/.rvm/rubies/ruby-2.3.4/lib                |
| OpenSSL Version             | OpenSSL 1.0.2l  25 May 2017                 |
| Is contained                | false                                       |
| Is homebrew                 | false                                       |
| Is installed via Fabric.app | false                                       |
| Xcode Path                  | /Applications/Xcode.app/Contents/Developer/ |
| Xcode Version               | 9.2                                         |

### System Locale

| Variable | Value       |   |
| -------- | ----------- | - |
| LANG     | en_GB.UTF-8 | ✅ |
| LC_ALL   |             |   |
| LANGUAGE |             |   |

### fastlane gems

| Gem      | Version | Update-Status |
| -------- | ------- | ------------- |
| fastlane | 2.71.0  | ✅ Up-To-Date  |

### Loaded fastlane plugins:

| Plugin                                 | Version | Update-Status |
| -------------------------------------- | ------- | ------------- |
| fastlane-plugin-increment_version_code | 0.4.3   | ✅ Up-To-Date  |

Loaded gems

| Gem                                    | Version      |
| -------------------------------------- | ------------ |
| did_you_mean                           | 1.0.0        |
| executable-hooks                       | 1.3.2        |
| bundler-unload                         | 1.0.2        |
| rubygems-bundler                       | 1.4.4        |
| bundler                                | 1.16.1       |
| io-console                             | 0.4.5        |
| CFPropertyList                         | 2.3.6        |
| public_suffix                          | 2.0.5        |
| addressable                            | 2.5.2        |
| babosa                                 | 1.0.2        |
| claide                                 | 1.0.2        |
| colored                                | 1.2          |
| colored2                               | 3.1.2        |
| highline                               | 1.7.10       |
| commander-fastlane                     | 4.4.5        |
| declarative                            | 0.0.10       |
| declarative-option                     | 0.1.0        |
| unf_ext                                | <IP_ADDRESS>      |
| unf                                    | 0.1.4        |
| domain_name                            | 0.5.20170404 |
| dotenv                                 | 2.2.1        |
| excon                                  | 0.60.0       |
| multipart-post                         | 2.0.0        |
| faraday                                | 0.13.1       |
| http-cookie                            | 1.0.3        |
| faraday-cookie_jar                     | 0.0.6        |
| faraday_middleware                     | 0.12.2       |
| fastimage                              | 2.1.1        |
| gh_inspector                           | 1.0.3        |
| jwt                                    | 2.1.0        |
| little-plugger                         | 1.1.4        |
| multi_json                             | 1.12.2       |
| logging                                | 2.2.2        |
| memoist                                | 0.16.0       |
| os                                     | 0.9.6        |
| signet                                 | 0.8.1        |
| googleauth                             | 0.6.2        |
| httpclient                             | 2.8.3        |
| mime-types-data                        | 3.2016.0521  |
| mime-types                             | 3.1          |
| uber                                   | 0.1.0        |
| representable                          | 3.0.4        |
| retriable                              | 3.1.1        |
| google-api-client                      | 0.13.6       |
| json                                   | 2.1.0        |
| mini_magick                            | 4.5.1        |
| multi_xml                              | 0.6.0        |
| plist                                  | 3.4.0        |
| rubyzip                                | 1.2.1        |
| security                               | 0.1.3        |
| slack-notifier                         | 1.5.1        |
| terminal-notifier                      | 1.8.0        |
| unicode-display_width                  | 1.3.0        |
| terminal-table                         | 1.8.0        |
| tty-screen                             | 0.6.4        |
| word_wrap                              | 1.0.0        |
| nanaimo                                | 0.2.3        |
| xcodeproj                              | 1.5.4        |
| rouge                                  | 2.0.7        |
| xcpretty                               | 0.2.8        |
| xcpretty-travis-formatter              | 1.0.0        |
| fastlane-plugin-increment_version_code | 0.4.3        |

Then, the output file is named : app.api.api and the last version is not deploy on hockey app.

Am I right in assuming that you mean app.ipa.ipa? Can you share your output? I am not deeply familiar with it but it looks like it should be removing the .ipa file at the end. There are tests to check that as well.
In the meantime, can you try to just give the file name without ipa?

Yes you right. The ouput filename is really app.ipa.ipa.
The solution we found is, like your suggest,  removing the .ipa file at the end of the GYM_OUTPUT_NAME variable => It works now.
'.ipa' seems to be no longer removed.
An other team updated  fastlane to 2.71 and they have experimented the same issue ...

Seems like it works using CLI, let me try with env variables

Yep, only doesn't work using env variables, I'll push a fix in a minute

Thanks for the report, this will be fixed in the next release 👍 https://github.com/fastlane/fastlane/pull/11377


Change for Indian markets IB range as 9:15 to 10:15

Hi, i wanted to thank you for your  wonderful project which enabled us to test MP concept programmatic.
I am trying to test in Indian market , could see that first 30 mins starts from 9:15 and IB will be 9:15 to 10:15 , right now I could see code is taking 9:00 to 9:30 as first A period & IB as 9:00 to 10:00 , so is there any way we can customize this to look  A period from 9:15 & take from that .. Like 9:15 to 9:45 - A Period,9:45 to 10:15 - B Period

Thanks. Yes, I changed in new version which I just uploaded.
It can be done easily. In the main file for static TPO. Around line number 47 there is a resample method.
dfresample = dfresample.resample(str(freq)+'min').agg({'symbol': 'last', 'datetime': 'first', 'Open': 'first', 'High': 'max',
'Low': 'min', 'Close': 'last', 'Volume': 'sum', 'rf': 'sum'})
change 'datetime': 'first' to
'datetime': 'last'

Thanks for the new version, but still after changing the datetime: first to datetime:last, only legend is getting changed from 9:16  to 9:29, but chart is taking first time period as 9:16 to 9:30. Attaching screenshot.
A period should be 9:16 to 9:45
B period should be 9:46 to 10:15
datetime:last

datetime:first

Hi - able to figure out , below code fixed the issue. Thanks
dfresample = dfresample.resample(str(freq)+'min',base=16).agg({'symbol': 'last', 'datetime': 'last', 'Open': 'first', 'High': 'max',
'Low': 'min', 'Close': 'last', 'Volume': 'sum', 'rf': 'sum'})


Use weave:peerGroupName tag to identify peers

Fixes #1
Improves #73
@bryanvaz PTAL. I have never used spot fleets, but the documentation shows they queried in the same way as normal instances, so I think this should work. I would appreciate if you could verify it though.

This is the only change pending the next release (https://github.com/weaveworks/integrations/pull/83) I will wait until tomorrow to see if @bryanvaz  has any comments, otherwise I will just do the customary testing and cut a release.

(CC @randywallace)

(CC @djeusette )

I have tested this successfully, merging. Release coming up soon.

@2opremio is this in the newest AMI (ami-4e36fe2d for ap-southeast-1)? It doesn't seem to work for me.

Here are screenshots, I have to sanatize the terraform before I can post it
ECS:

EC2:

m3 ASG:

hub ASG:

Security Group:

Weave Status (on m3):
        Version: 1.4.5

        Service: router
       Protocol: weave 1..2
           Name: 86:bd:96:92:f3:4d(ip-172-31-23-92)
     Encryption: disabled
  PeerDiscovery: enabled
        Targets: 0
    Connections: 0
          Peers: 1
 TrustedSubnets: none

        Service: ipam
         Status: ready
          Range: <IP_ADDRESS>-<IP_ADDRESS>
  DefaultSubnet: <IP_ADDRESS>/12

        Service: dns
         Domain: weave.local.
       Upstream: <IP_ADDRESS>
            TTL: 1
        Entries: 4

        Service: proxy
        Address: unix:///var/run/weave/weave.sock

@bryanvaz Your AMI ID is correct. However, your tag has key weave and value peerGroupName=fleetyars but it should have key weave:peerGroupName (note the colon) and value fleetyards.
I see that the confusion most probably comes from the documentation, sorry about that. I will clarify it further.

@bryanvaz Also, please make sure to allow ec2:DescribeTags actions from the instances, as explained at https://github.com/weaveworks/integrations/tree/master/aws/ecs#2-additional-amazon-ecs-api-action-permissions

So there is definitely something strange, creating a normal weave ASG works fine. As soon as I add the key, nothing but Scope boots up, no ECS, no weave, nothing. I'm going to modify the demo weave code for tags and send it over (sanitizing terraform is just too insane).

@bryanvaz For the machines in which it doesn't work please:

ssh into the machine
Get me the output of:

bash -x /etc/weave/peers.sh
docker ps
sudo initctl list
sudo grep 'scope\|init:' /var/log/messages
weave status
docker logs weave


Turn off console access in Production

Being able to hack the window (use the console) was something that @wehmoen discovered. This should not be available in production apps.

Is this still an open issue? Would be interested to take a look into it 😄

@Autarc, yes it's still open. You are welcome to try it :relaxed:


issue-181

I extended the current method with some optionals to match the current functionality which is available in Neo4j Cypher.

Will be in <IP_ADDRESS>!


SimpleNode is just Docker Compose 🙄

Do we really need the sub folders with config file ?

I think we need the bitcoind one? but the counterparty config files can probably just be examples in the docs

I think we need the bitcoind one? but the counterparty config files can probably just be examples in the docs

hum.. I think we need it only if we want to maintain a counterparty/bitcoind image with this default configuration else the parameters in compose.yml should be enough.

Ah yes, I forget why I did that! I think I just wanted people to be able run the bitcoind in docker without docker compose?? but there's probably no reason for that.
We can get rid of our bitcoind image.


upper case package issues with stack-stack-1.7.0

Describe the bug
cmake function find_package essentially breaks due to upper case variables located in spack-stack/1.7.0
the warning message looks like this:
-- Found PNG: /mnt/lfs4/HFIP/hfv3gfs/role.epic/spack-stack/spack-stack-1.7.0/envs/ue-intel/install/intel/2021.5.0/libpng-1.6.37-lpk5hek/lib64/libpng.so (found version "1.6.37")
CMake Warning (dev) at CMakeLists.txt:27 (find_package):
  Policy CMP0144 is not set: find_package uses upper-case <PACKAGENAME>_ROOT
  variables.  Run "cmake --help-policy CMP0144" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.

  Environment variable JASPER_ROOT is set to:

    /mnt/lfs4/HFIP/hfv3gfs/role.epic/spack-stack/spack-stack-1.7.0/envs/ue-intel/install/intel/2021.5.0/jasper-2.0.32-lydwve7

  For compatibility, find_package is ignoring the variable, but code in a
  .cmake module might still use it.
This warning is for project developers.  Use -Wno-dev to suppress it.

To Reproduce
git clone https://github.com/NOAA-GFDL/GFDL-VortexTracker.git
cd GFDL-VortexTracker
mkdir build && cd build
module use /mnt/lfs4/HFIP/hfv3gfs/role.epic/spack-stack/spack-stack-1.7.0/envs/ue-intel/install/modulefiles/Core/
module load stack-intel
module load cmake/3.28.1
module load szip
module load hdf5
module load netcdf
module load jasper
module load zlib-ng
module load libpng
module load g2
module load g2tmpl
module load bacio/
module load w3emc
module load w3nco
cmake ..                       --> warnings appear
make                            --> fails due to libraries not loading
Expected behavior
expected behavior is that the cmake successfully builds, compiles, and creates executables
System:
Jet and Hera, the steps on hera differ slightly but the results are the same
Additional context
these issues do not arise when using /mnt/lfs4/HFIP/hfv3gfs/role.epic/spack-stack/spack-stack-1.6.0/envs/unified-env-rocky8/install/modulefiles/Core/

@climbfuji  All good, @AlexanderRichert-NOAA suggested that I open this issue.
I do want to mention, that although what results due to the uppercase labeling, is only a warning, it does cause the build system to fail. With this being said, there are other spack environment

Thanks for the additional info. That must be something hardcoded like a hint package_ROOT in some CMakeLists.txt. If you plan to skip 1.7.0, then better not change your build. Sorry for the inconvenience, we shouldn't have adoped this change for 1.7.0.
I created this issue in spack develop https://github.com/spack/spack/issues/43569 and also mentioned it in the their slack channel (https://spackpm.slack.com/archives/C5W7NKZJT/p1712752096643619).

I've changed my mind. I would like to get this change reverted for 1.7.0 and fix the existing installations. There's a PR for this https://github.com/JCSDA/spack/pull/421 - still need the green light from my spack-stack colleagues on this, though.

Closed via https://github.com/JCSDA/spack-stack/pull/1068


SLING-4544 - Performance: MessageFormat shouldn't be used for logging…

… in SlingRequestProgressTracker

Implement fast MessageFormat implementation which falls back to original implementation for complex formatting

@joelrich - the Jira issue has been resolved, can you please close the pull request?