dexador icon indicating copy to clipboard operation
dexador copied to clipboard

dexador and network unreachable

Open brulint opened this issue 4 years ago • 0 comments

Hi,

I don't understand why dexador takes so long to detect that the network is unreachable.

I turn off the network and try this:

(time (handler-case (dex:get "https://www.google.com")
         (error (e) (warn "~s" e))))

and I get this (at the first time, after it works quickly):

WARNING: #<USOCKET:NS-HOST-NOT-FOUND-ERROR {1004689883}>
Evaluation took:
1080.867 seconds of real time
[blalba]

18 minutes! it's tooooo long, no ?

did i miss something ?

Backtrace:

  0: (USOCKET::HANDLE-CONDITION #<SB-BSD-SOCKETS:HOST-NOT-FOUND-ERROR {10056916A3}> NIL "www.google.com")
  1: (SB-KERNEL::%SIGNAL #<SB-BSD-SOCKETS:HOST-NOT-FOUND-ERROR {10056916A3}>)
  2: (ERROR SB-BSD-SOCKETS:HOST-NOT-FOUND-ERROR :ERROR-CODE -2 :SYSCALL "getaddrinfo")
  3: (SB-BSD-SOCKETS::ADDRINFO-ERROR "getaddrinfo" -2)
  4: (SB-BSD-SOCKETS:GET-HOST-BY-NAME #<unavailable argument>)
  5: (USOCKET:GET-HOSTS-BY-NAME "www.google.com")
  6: (USOCKET:SOCKET-CONNECT "www.google.com" 443 :PROTOCOL :STREAM :ELEMENT-TYPE (UNSIGNED-BYTE 8) :TIMEOUT 10 :DEADLINE NIL :NODELAY T :LOCAL-HOST NIL :LOCAL-PORT NIL)

brulint avatar Aug 11 '20 10:08 brulint