local upgrade fails

[letrec]

Pre-Check

Can't find this bug being previously reported

Environment

• Add the result of rebar3 report to your message:

Rebar3 report version 3.18.0 generated at 2022-06-19T12:51:27+00:00

Please submit this along with your issue at https://github.com/erlang/rebar3/issues (and feel free to edit out private information, if any)

Task: rebar3 Entered as: rebar3 local upgrade

Operating System: x86_64-pc-linux-gnu ERTS: Erlang/OTP 25 [erts-13.0.1] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [jit:ns] Root Directory: /home/user/kerl/25.0.1 Library directory: /home/user/kerl/25.0.1/lib

Loaded Applications: bbmustache: 1.12.2 certifi: 2.8.0 cf: 0.3.1 common_test: 1.23 compiler: 8.2 crypto: 5.1.1 cth_readable: 1.5.1 dialyzer: 5.0.1 edoc: 1.2 erlware_commons: 1.5.0 eunit: 2.7.1 eunit_formatters: 0.5.0 getopt: 1.0.1 inets: 8.0 kernel: 8.4.1 providers: 1.9.0 public_key: 1.13 relx: 4.6.0 sasl: 4.2 snmp: 5.13 ssl_verify_fun: 1.1.6 stdlib: 4.0.1 syntax_tools: 3.0 tools: 3.5.3

---

Escript path: undefined Providers: app_discovery as clean compile compile cover ct deps dialyzer do edoc escriptize eunit get-deps help install install_deps list lock new path pkgs release relup report repos shell state tar tree unlock update upgrade upgrade upgrade version xref

• Verify whether the version of rebar3 you're running is the latest release (see https://github.com/erlang/rebar3/releases)
• If possible, include information about your project and its structure. Open source projects or examples are always easier to debug. If you can provide an example code base to reproduce the issue on, we will generally be able to provide more help, and faster.

Current behaviour

Describe the current behaviour. In case of a failure, crash, or exception, please include the result of running the command with debug information:

DIAGNOSTIC=1 rebar3 local upgrade ===> Expanded command sequence to be run: [] ===> Running provider: do ===> Expanded command sequence to be run: [{local,upgrade}] ===> Running provider: {local,upgrade} =NOTICE REPORT==== 19-Jun-2022::20:52:39.667658 === TLS client: In state certify at ssl_handshake.erl:2100 generated CLIENT ALERT: Fatal - Handshake Failure

• {bad_cert,max_path_length_reached} ===> Request to "https://s3.amazonaws.com/rebar3/rebar3" failed: {failed_connect, [{to_address, {"s3.amazonaws.com", 443}}, {inet, [inet], {tls_alert, {handshake_failure, "TLS client: In state certify at ssl_handshake.erl:2100 generated CLIENT ALERT: Fatal - Handshake Failure\n {bad_cert,max_path_length_reached}"}}}]} ===> Unable to fetch latest rebar3 escript. Please try again later. ===> Uncaught error in rebar_core. Run with DIAGNOSTIC=1 to see stacktrace or consult rebar3.crashdump ===> Uncaught error: {try_clause,ok} ===> Stack trace to the error location: [{rebar_core,do,2, [{file,"/home/runner/work/rebar3/rebar3/src/rebar_core.erl"}, {line,155}]}, {rebar_prv_do,do_task,5, [{file,"/home/runner/work/rebar3/rebar3/src/rebar_prv_do.erl"}, {line,87}]}, {rebar_core,do,2, [{file,"/home/runner/work/rebar3/rebar3/src/rebar_core.erl"}, {line,155}]}, {rebar3,run_aux,2, [{file,"/home/runner/work/rebar3/rebar3/src/rebar3.erl"},{line,183}]}, {rebar3,main,1, [{file,"/home/runner/work/rebar3/rebar3/src/rebar3.erl"},{line,66}]}, {init,start_em,1,[]}, {init,do_boot,3,[]}] ===> When submitting a bug report, please include the output of rebar3 report "your command"

Expected behaviour

I expect upgrade of rebar3 to the latest version to succeed.

[tsloughter]

This has been resolved in 3.19.0. Sadly you'll have to download 3.19.0 to get it because of this issue with cert depth, https://s3.amazonaws.com/rebar3/rebar3