Pete Peterson

I would love to use the bash-native list of hosts for completion through fzf. Any chance you still have your proof of concept to share? It looks like #1149 might...

Real questions: Should the script be split into development is hooked onto `CONDA_ENV` and production connected to `CONDA_BUILD`? The code needs more work, but I think that is the distinction...

Documenting conversation with @martyngigg. The new logic (for `CONDA_BUILD=on`) is Get install location (current `INSTALL_DIR`) * if it matches `CONDA_PREFIX` then launch mantid as usual * else if `conda` exists...

Variables that are useful for this: * `CONDA_DEFAULT_ENV` points at the name of the conda environment that is active (e.g. `mantid-dev`) * `CONDA_PREFIX` contains the full path of the current...

This would be a good bit of documentation to link into the PR template (in `.github/PULL_REQUEST_TEMPLATE.md`) so it pops up automatically

The build issue has to do with sphinx warnings. You need to fix your release notes ``` 08:48:34 release/v6.8.0/indirect_geometry:4: WARNING: Bullet list ends without a blank line; unexpected unindent. 08:48:34...

I have a vague memory of there being an issue of solid angle not accounting of the occlusion of a pixel by its neighbors. I do not recall if this...

Does this behavior still happen when you use the wrapper scripts that are installed? The are in `..../bin/mantidworkbench`. They are bash and currently do the following (in order): 1. `LD_PRELOAD`...

There is an additional issue hiding in here. Currently we get a segfault when starting mantidworkbench on rhel9 (fine on rhel7). Commenting out the lines from the launch script ```sh...

Also not that `conda info` says (truncated) on rhel7 ``` virtual packages : __archspec=1=skylake_avx512 __cuda=12.2=0 __glibc=2.17=0 __linux=3.10.0=0 __unix=0=0 ``` and on rhel9 ``` virtual packages : __archspec=1=cascadelake __cuda=12.4=0 __glibc=2.34=0 __linux=5.14.0=0...