bruno
bruno
After the fixes in #608 there is no more issues when using the file servers.
Le [commentaire](https://github.com/KhiopsML/khiops/issues/216#issuecomment-2039818049) de l'issue #216 suggère de nettoyer le code lors de la suppression du code retour 2. Il est probable qu'on ai besoin d'avoir accès au compteur des erreurs...
Unable to reproduce this on Linux. Perhaps it is a macOS only bug. In that case, this commit 615fdf142ccd6023e586b1353a46234070d6a3dd is probably the source of the problem.
yes I think so
For windows the problem is that khiops-env is generated by the nsis script during the install process. There are two main issues: - the jre path is discover by scanning...
We can easily add a new option in the CMakeFiles.txt e.g. NO_MPI_SUFFIX. But it will introduce an inconsistency in cmake: if NO_MPI_SUFFIX=OFF, cpack will fail with DEB and RPM as...
Actually, the mpi suffix discovering process fails on conda (all mpi libs are located on the same directory, there is no information about the mpi implementation AFAIK). Then there is...
if JAVA_HOME is no longer valid, khiops prints an error. No need to catch it in the khiops-env script, but of course the user have to see it.
When using directly the MODL binary, the error is printed in the console. The problem comes from the khiops bash script: ```bash if [[ $# -eq 0 ]]; then #...
A proposal: A new environment variable in khiops_env: **KHIOPS_DRIVERS_LOCATION**. If it is set, Khiops will use it to looking for the drivers. If not, Khiops will looking for the drivers...