Skip to content

Using set_config_option on an operator's config does not actually change it server-side. #1917

Open
@PProfizi

Description

@PProfizi

Before submitting the issue

  • I have checked for Compatibility issues
  • I have searched among the existing issues
  • I am using a Python virtual environment

Description of the bug

When using operator.config.set_config_option on an instance of an operator, the user would expect the config of the operator's instance to be modified in-place, which is not the case.

Steps To Reproduce

import ansys.dpf.core as dpf

op = dpf.operators.math.component_wise_divide_fc()
print(op.config.config_option_value("permissive"))

op.config.set_config_option(config_name="permissive", config_value=True)
print(op.config.config_option_value("permissive"))

new_config = op.default_config()
new_config.set_config_option(config_name="permissive", config_value=True)
print(new_config.config_option_value("permissive"))

op.config = new_config
print(op.config.config_option_value("permissive"))

Which Operating System causes the issue?

Windows, MacOS, Linux

Which DPF/Ansys version are you using?

DPF Server 2025.2.pre0

Which Python version causes the issue?

3.12

Installed packages

NA

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions