Re: Issues with PVXS

[Ralph Lange via Tech-talk <tech-talk at aps.anl.gov>]

Not good.

From a formal point of view...

If you look at the NT specification of the NTNDArray [1], the types of these parameters and attributes are not fixed in the specification, so both servers (the one using the original stack and the one using PVXS) are shipping different valid NTNDArrays.

To increase robustness, the general direction of fixing should be to make the receiving side cope with the allowed variability inside NTNDArray. The fastest and/or most practical approach might differ.

IOC crashes are unacceptable and bugs in any case, obviously.

I would be really surprised if PXVS changed any user-configured data types. Please verify that the new AD plugin really calls PVXS with data structures that are different from what you see on the network.

Cheers,
~Ralph

[1] https://docs.epics-controls.org/en/latest/pv-access/Normative-Types-Specification.html#ntndarray