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.
Is there support for marshalling
ATOM_UTF8_EXT
andSMALL_ATOM_UTF8_EXT
sinceATOM_EXT
andSMALL_ATOM_EXT
has been officially DEPRECATED? (https://erlang.org/doc/apps/erts/erl_ext_dist.html#atom_utf8_ext)Following my upgrade to OTP20, I began getting this error when attempting to connect.
Reproduce Steps
Environment
Relates to CHANGELOG
From the OTP20 Release notes
and
See: https://github.com/massemanet/distel/issues/61