Launch failures don't always report the cause #90
Description
When working with cellpose I ran into an error where I had an invalid environment on Windows. import cellpose (e.g. in fiji.py or a python script) causes python/fiji to crash because of the mis-configuration.
However, Jaunch printed no indication of the failure.
For other types of failure, e.g. import imaginarylibrary, Jaunch reported the failure appropriately. So there is something in cellpose's mechanism of failure that currently is missed by Jaunch and may necessitate more capturing or error handling.
For the record, the cellpose failure (e.g. from the repl) was:
>>> import cellpose.models
Welcome to CellposeSAM, cellpose v
cellpose version: 4.0.6
platform: win32
python version: 3.11.13
torch version: 2.8.0+cpu! The neural network component of
CPSAM is much larger than in previous versions and CPU excution is slow.
We encourage users to use GPU/MPS if available.
OMP: Error #15: Initializing libomp.dll, but found libiomp5md.dll already initialized.
OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://openmp.llvm.org/