fix: container launch issues

[raph-luc]

There were issues running Fluent containers through PyFluent introduced at some point since version 0.30.5 (after which the simba-plugin-fluent tests started failing). The mount_source/mount_target/working_dir logic was not working properly, see first commit below for test that was showing the failure: 270495d

Notes:

• Main change: revised mount_source/mount_target logic, see code comments in fluent_container.py for more details
• Took the opportunity to do some refactoring:
  • New dict_to_str utility function to provide "pretty printed" string for dicts, also aware of hide log secrets env var for CI runs
  • Revised docstring for mount_source/mount_target
• New test, and test fixes related to this. In summary: we should not assume that the full paths that Fluent sees inside the container match exactly the full paths that PyFluent sees on the host system

[hpohekar]

Verified. All changes are working fine.

https://github.com/ansys/pyfluent/actions/runs/15723746346

https://github.com/ansys/pyfluent/actions/runs/15723743336

[hpohekar]

There were issues running Fluent containers through PyFluent introduced at some point since version 0.30.5 (after which the simba-plugin-fluent tests started failing). The mount_source/mount_target/working_dir logic was not working properly, see first commit below for test that was showing the failure: 270495d

Notes:

• Main change: revised mount_source/mount_target logic, see code comments in fluent_container.py for more details

• Took the opportunity to do some refactoring:

  • New dict_to_str utility function to provide "pretty printed" string for dicts, also aware of hide log secrets env var for CI runs
  • Revised docstring for mount_source/mount_target

• New test, and test fixes related to this. In summary: we should not assume that the full paths that Fluent sees inside the container match exactly the full paths that PyFluent sees on the host system

Yes, I agree. I came across a specific case related to the last point mentioned here, while working on the parametric workflow example. Fluent was changing current working directory on its own but container was launched with different working directory as a host path.

[prmukherj]

@raph-luc, Thanks for the descriptive tests. Looks good 👍

[hpohekar]

@raph-luc Merging to create a release.