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
In the OTP 20 release candidates the function erlang:term_to_binary/1 changed the encoding of all atoms from ATOM_EXT to ATOM_UTF8_EXT and SMALL_ATOM_UTF8_EXT. This is now changed so that only atoms actually containing unicode characters are encoded with the UTF8 tags while other atoms are encoded ATOM_EXT just as before.
and
Atoms can now contain arbitrary unicode characters which means that the DFLAG_UTF8_ATOMS capability in the distribution protocol must be supported if an OTP 20 node should accept the connection with another node or library. Third party libraries which uses the distribution protocol need to be updated with this.
EDIT 2
Details for ATOM_UTF8_EXT and SMALL_ATOM_UTF8_EXT can be found here . These need to be implemented in exterl.el.
Details for the DFLAG_UTF8_ATOMS can be found here. This needs to be updated in derl.el.
The text was updated successfully, but these errors were encountered:
Following my upgrade to OTP20 I began getting this error when attempting to connect.
The only Distel related response to this error I could find was here.
This issue seams to be pretty wide spread among other applications following the release of OTP20, for example and another.
EDIT
From the OTP20 Release notes
and
EDIT 2
Details for
ATOM_UTF8_EXT
andSMALL_ATOM_UTF8_EXT
can be found here . These need to be implemented in exterl.el.Details for the
DFLAG_UTF8_ATOMS
can be found here. This needs to be updated in derl.el.The text was updated successfully, but these errors were encountered: