Describe the bug
After the UCT caching changes in ucp_config_modify from #7019, it's not possible anymore to check whether a wrong/mistyped option was set. In UCX-Py we use UCS_ERR_NO_ELEM return status to identify a wrong user-specified option, but now all we get is a warning that doesn't really reflect the actual issue:
[1633640648.678052] [dgx13:79435:0] ucp_worker.c:1972 UCX WARN unused cached uct configuration: UNKOWN_OPTION
Steps to Reproduce
- Call
ucp_config_modify with any non-existing variable name;
- UCX master at b6197c8 or newer.
Describe the bug
After the UCT caching changes in
ucp_config_modifyfrom #7019, it's not possible anymore to check whether a wrong/mistyped option was set. In UCX-Py we useUCS_ERR_NO_ELEMreturn status to identify a wrong user-specified option, but now all we get is a warning that doesn't really reflect the actual issue:Steps to Reproduce
ucp_config_modifywith any non-existing variable name;