fix: container timeout issue and new environment variables #4171
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes:
launch_fluent
. Now the container launcher respects thestart_timeout
argument, and thecontainer_dict["timeout"]
argument is marked as deprecatedtest_unsuccessful_fluent_connection
now works for containers as well and tests that their timeout config is working properlytest_container_timeout_deprecation
andtest_container_timeout_deprecation_override
for testing the deprecation behaviorPYFLUENT_FLUENT_LAUNCH_TIMEOUT
andPYFLUENT_FLUENT_AUTOMATIC_TRANSCRIPT
env vars - were useful previously for testing/developmentenv_var_to_bool
method to get the value from an env var and return the Boolean that represents it:pyfluent/src/ansys/fluent/core/utils/__init__.py
Lines 61 to 67 in 1b34713
env_var_to_bool
where it makes sense