Can a chain be built between ucx 1.12 and ucx1.14

[super-train]

When I want to build a chain using the ucx1.12 and ucx1.14 libraries,
1.12 as a client, 1.14 as a server, encountering problems:

1. If both parties set cm_use_all_device to yes
   When processing the chain building request sent by the client on the server side, there will be a stack throw

2. If both parties set cm_use_all_device to no, then the chain is successfully built
   Can someone give me some guidance on why cm_use_all_device fails when set to yes, and how to handle it
   Thank you.

PS: Due to some special reasons, both parties' cm_use'all_device must be set to yes

[gleon99]

Hi

Please provide more details on what exactly you are tryin to do and what is the result (output, logs, etc).
See also the template for reporting a bug, under "New Issue".

[super-train]

Hi

Please provide more details on what exactly you are tryin to do and what is the result (output, logs, etc). See also the template for reporting a bug, under "New Issue".

@gleon99 Thank you for your answer
I compared the submitted modifications for 1.12 and 1.14, combined with the log information, and found that the relevant modifications were
f2c1651
UCP/WIREUP: Always pack TL resource indices into CM private data
This modification was made in 1.14 to pack TL resource indicators into CM private data
The processing here did not match 1.12, resulting in failure
I rolled back this modification in 1.14, and the rolled back version can now be successfully linked to 1.12