Closed massemanet closed 3 years ago
just an annoying error handling misfeature. Would be better if the user got a "Network error" message.
$ DEBUG=1 rebar3 hex user auth ===> Evaluating config script "rebar.config.script" ===> Load global config file /Users/masse/.config/rebar3/rebar.config ===> Expanded command sequence to be run: [] ===> Expanded command sequence to be run: [{hex,user}] Username: ([])> massemanet Password: Generating API key... ===> Uncaught error in rebar_core. Run with DEBUG=1 to see stacktrace or consult rebar3.crashdump ===> Uncaught error: {case_clause, {error, {failed_connect, [{to_address,{"hex.pm",443}}, {inet,[inet],nxdomain}]}}} ===> Stack trace to the error location: [{rebar3_hex_http,post_map,3, ...}] $ rebar3 report "rebar3 hex user auth" Rebar3 report version 3.3.5 generated at 2017-04-14T14:17:32+00:00 ================= Task: rebar3 Entered as: rebar3 hex user auth ----------------- Operating System: x86_64-apple-darwin16.4.0 ERTS: Erlang/OTP 19 [erts-8.3] [source] [64-bit] [smp:4:4] [async-threads:0] [hipe] [kernel-poll:false] [dtrace] Root Directory: /usr/local/Cellar/erlang/19.3/lib/erlang Library directory: /usr/local/Cellar/erlang/19.3/lib/erlang/lib ----------------- Loaded Applications: bbmustache: 1.3.0 certifi: 0.4.0 cf: 0.2.2 common_test: 1.14 compiler: 7.0.4 crypto: 3.7.3 cth_readable: 1.2.3 dialyzer: 3.1 edoc: 0.8.1 erlware_commons: 1.0.0 eunit: 2.3.2 eunit_formatters: 0.3.1 getopt: 0.8.2 inets: 6.3.6 kernel: 5.2 providers: 1.6.0 public_key: 1.4 relx: 3.22.2 sasl: 3.0.3 snmp: 5.2.5 ssl_verify_fun: 1.1.1 stdlib: 3.3 syntax_tools: 2.1.1 tools: 2.9.1 ----------------- Escript path: /usr/local/bin/rebar3 Providers: app_discovery as clean compile compile config cover ct cut deps dialyzer do docs edoc escriptize eunit get-deps help info install install_deps key list lock new owner path pkgs publish release relup report search shell state tar tree unlock update upgrade upgrade upgrade user version xref
Ah, yea, you are right.
This issue was resolved some time ago. If I'm wrong about that, let's re-open, but closing for now.
just an annoying error handling misfeature. Would be better if the user got a "Network error" message.