Closed svetlyak40wt closed 5 months ago
https://github.com/fukamachi/dexador/commit/bee5f13d658d042d6666ba58d2c559cfaf960e40#diff-c750a8a8d4c464f04f1487153c5674b703e223f05574f38ecc8520403f4e5c4a
This commit replaced :use of :dexador package and instead of
(:use :cl #-windows #:dexador.backend.usocket #+windows #:dexador.backend.winhttp)
we now have:
(:use :cl)
Because of that IGNORE-AND-CONTINUE function, defined like this in dexador.lisp:
IGNORE-AND-CONTINUE
(defun ignore-and-continue (e) (let ((restart (find-restart 'ignore-and-continue e))) (when restart (invoke-restart restart))))
searches for a wrong restart name. Previosly symbol ignore-and-continue was taken from the dexador.backend.usocket.
ignore-and-continue
dexador.backend.usocket
How to reproduce an issue? Call this in the REPL:
(handler-bind ((dex:http-request-failed #'dex:ignore-and-continue)) (dex:get "https://httpbin.org/get/404"))
DEXADOR.ERROR:HTTP-REQUEST-NOT-FOUND error will be opened in the debugger.
DEXADOR.ERROR:HTTP-REQUEST-NOT-FOUND
Expected behaviour – function dex:get returned a response and 404 code as a second value.
dex:get
I've found RETRY-REQUEST is also broken because of the same reason.
It would be nice to have some tests on the critical features.
Thank you for reporting. I'm working on it.
Great! Thank you!!!
https://github.com/fukamachi/dexador/commit/bee5f13d658d042d6666ba58d2c559cfaf960e40#diff-c750a8a8d4c464f04f1487153c5674b703e223f05574f38ecc8520403f4e5c4a
This commit replaced :use of :dexador package and instead of
we now have:
Because of that
IGNORE-AND-CONTINUE
function, defined like this in dexador.lisp:searches for a wrong restart name. Previosly symbol
ignore-and-continue
was taken from thedexador.backend.usocket
.How to reproduce an issue? Call this in the REPL:
DEXADOR.ERROR:HTTP-REQUEST-NOT-FOUND
error will be opened in the debugger.Expected behaviour – function
dex:get
returned a response and 404 code as a second value.