Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dexador and network unreachable #90

Open
brulint opened this issue Aug 11, 2020 · 0 comments
Open

dexador and network unreachable #90

brulint opened this issue Aug 11, 2020 · 0 comments

Comments

@brulint
Copy link

brulint commented Aug 11, 2020

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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant