Hallo, shared memory addon seems to be broken with 5.x, issue seems to be with internal serialization in VL.
hm strange, I can’t see my answer (probably I didnt press the reply button?)
so, I am aware of this issue but didnt have time to update the main branch properly, please switch to “deploy” and see if this issue persists!
Thanks!
With the 5.0 release we switched to .NET 6 which in turn introduced some new APIs around System.IO.Stream (used in your library). That lead to an ambiguity in our node resolver. However it was possible to address this ambiguity and you’ll find a fix in our latest preview.
4 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.