[erlang-questions] Erlang/OTP 21.0-rc1 (Release Candidate)

Tristan Sloughter t@REDACTED
Fri May 4 18:55:43 CEST 2018


We cut a new release today, 3.5.2, that builds with 21 fine.

Tristan

On Fri, May 4, 2018, at 7:58 AM, Andreas Schultz wrote:
> Hi,
> 
> The RC breaks rebar3 badly, not sure if it's rebar's fault or a
> problem with the new logger...> 
> With an up to date rebar3 clone:
> 
>     rebar3$ ./bootstrap
>     (no logger present) unexpected logger message: {log,error,"Error
>     in process ~p with exit value:~n~p~n",[<0.39.0>,{badarg,[{ets,loo-
>     kup,[logger,proc_lib],[]},{logger_config,allow,3,[{file,"logger_c-
>     onfig.erl"},{line,42}]},{proc_lib,crash_report,4,[{file,"proc_lib-
>     .erl"},{line,508}]},{proc_lib,exit_p,3,[{file,"proc_lib.erl"},{li-
>     ne,269}]}]}],#{error_logger=>#{emulator=>true,tag=>error},gl=><0.-
>     37.0>,pid=><0.39.0>,time=>-576460751953591}}>     (no logger present) unexpected logger message: {log,error,"Error
>     in process ~p with exit value:~n~p~n",[<0.39.0>,{badarg,[{ets,loo-
>     kup,[logger,proc_lib],[]},{logger_config,allow,3,[{file,"logger_c-
>     onfig.erl"},{line,42}]},{proc_lib,crash_report,4,[{file,"proc_lib-
>     .erl"},{line,508}]},{proc_lib,exit_p,3,[{file,"proc_lib.erl"},{li-
>     ne,269}]}]}],#{error_logger=>#{emulator=>true,tag=>error},gl=><0.-
>     37.0>,pid=><0.39.0>,time=>-576460751953591}}>    ...
> 
> And so on...
> 
> Regards
> Andreas
> 
> Henrik Nord X <henrik.x.nord@REDACTED> schrieb am Mi., 2. Mai 2018
> um 13:38 Uhr:>> OTP 21 Release Candidate 1
>> 
>>  This is the first of two planned release candidates before the
>>  OTP 21>>  release. The intention whit this release is that you as users try it>>  and give us feedback if something does not work as expected.
>>  Could be a>>  bug,an unexpected incompatibility, a significant change of
>>  characteristics in a negative direction, etc. 
>> 
>>  Erlang/OTP 21 is a new major release with new features,
>>  improvements as>>  well as incompatibilities.
>> 
>>  Potential Incompatibilities
>> 
>>   * All Corba applications are now moved from the OTP repository
>>      * A new Corba repository will be created
>>        https://github.com/erlang>>   * New applications ftp and tftp, moved from inets
>>   * ssl no longer supports 3_DES cipher suites or RSA-key exchange
>>  cipher suites by default
>>   * erlang:monitor on a primitive node (erl_interface, jinterface,
>>     etc)>>  will no longer fail with badarg exception. Instead a monitor will be>>  created, but it will only supervise the connection to the node.
>> 
>>   Highlights
>> 
>>   Erts:
>> 
>>      * Enhanced IO scalability
>>      * Support for usage of distribution controller processes for
>>        alternative transports, routing etc
>>      * compact instructions on 64bit systems for code below 4GB 20%
>>        less>>        memory for loaded code
>>      * Rewrite of the efile-driver with NIFs and "Dirty schedulers"
>>        resulting in faster file operations
>>      * non-smp VM removed
>>      * link and monitor optimized for scalability
>>      * os:getenv/putenv now work on thread-safe emulation. No longer
>>        in>>        sync with libc getenv(3). Manual synchronization will be
>>        needed.>> 
>>  Compiler:
>>      * Misc compiler optimizations including contributions from the
>>        Elixir team resulting in 10% improvements in benchmarks
>>      * "Tuple calls" have been removed from the run-time system.
>>      * Code such as f({ok, Val}) -> {ok, Val} is now automatically
>>        rewritten to f({ok, Val} = Tuple) -> Tuple. this reduces code>>        size, execution time, and removed GC pressure.
>>      * More information in stacktrace from a number of operators
>>      * erlang:get_stacktrace/0 deprecated to be replaced with try ...>>        catch C:R:Stacktrace -> ...
>>      * Creation of small maps with literal keys optimized.
>> 
>>  Security:
>>      * DTLS support in SSL
>>      * Enhanced support for distribution over TLS
>>      * "unsecure" ciphers removed from defaults in SSL and SSH.
>>      * A new option value defined to facilitate implementing exec
>>        servers. Old option kept for compatibility, but now gives
>>        errors>>        on stderror.
>> 
>>  Standard libraries:
>>      * New API for logging, logger
>>      * New uri_string module for parsing URIs according to "The
>>        standard"
>>      * New function lists:search(list,fun/1) -> {ok, Value} | false
>>      * Changed default behaviour of .erlang loading. escript, erlc,
>>        dialyzer and typer no longer load an .erlang at all.
>> 
>>  For more details see
>> http://erlang.org/download/otp_src_21.0-rc1.readme
>> 
>>  Pre built versions for Windows can be fetched here:
>> http://erlang.org/download/otp_win32_21.0-rc1.exe
>> http://erlang.org/download/otp_win64_21.0-rc1.exe
>> 
>>  Online documentation can be browsed here:
>> http://erlang.org/documentation/doc-10.0-rc1/doc/
>> 
>>  The Erlang/OTP source can also be found at GitHub on the official
>>  Erlang repository,
>> https://github.com/erlang/otp with tag OTP-21.0-rc1
>> 
>> 
>>  Thank you for all your contributions!
>>  _______________________________________________
>>  erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
> -- 
> --
> Dipl.-Inform. Andreas Schultz
>
> ----------------------- enabling your networks ----------------------
> Travelping GmbH                     Phone:  +49-391-81 90 99 0
> Roentgenstr. 13                     Fax:    +49-391-81 90 99 299 39108
> Magdeburg                     Email:  info@REDACTED GERMANY
> Web:    http://www.travelping.com
>> Company Registration: Amtsgericht Stendal        Reg No.:   HRB 10578> Geschaeftsfuehrer: Holger Winkelmann          VAT ID No.: DE236673780
> ---------------------------------------------------------------------> _________________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180504/f886fc5c/attachment.htm>


More information about the erlang-questions mailing list