You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting from some point, the encon library decodes PID's incorrectly and returns previously cached PID instead of creating the new one:
"ENCON GOT: [\"#PID<0.671.0>\"]
while JInterface got: #Pid<nonode@nohost.896.0>
896 is the right id of a PID that was sent from Elixir side.
Could you also ditch the caching function while creating atom return (T) ErlangAtom.cached(type, buffer) in ErlangTerm newInstance function? Just in case.
The text was updated successfully, but these errors were encountered:
It was a premature optimization to make the caches for ErlangPid, ErlangAtom instances. Moreover, it wasn't tested well, and the approach was too naive.
Right now I removed ErlangPid and ErlangAtom caches at all. A new release 1.6.7 was built, published and will be available in few hours at maven central.
In the next major release, I am going to use atom cache reference index at distribution header.
Starting from some point, the encon library decodes PID's incorrectly and returns previously cached PID instead of creating the new one:
"ENCON GOT: [\"#PID<0.671.0>\"]
while
JInterface got: #Pid<nonode@nohost.896.0>
896 is the right id of a PID that was sent from Elixir side.
Could you also ditch the caching function while creating atom
return (T) ErlangAtom.cached(type, buffer)
inErlangTerm newInstance
function? Just in case.The text was updated successfully, but these errors were encountered: