-
Notifications
You must be signed in to change notification settings - Fork 9
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
Multiple issues when using latest quicklisp and carrier master #7
Comments
Try everything from master (just updated carrier). cl-async has gone through a good amount of changes since the last QL update (I think) and it's best to stay on master for a while until things quiet down. |
Thanks for looking this :) Using latest master of cl-async, cl-async-future (carrier still uses cl-async-future wrapper around blackbird so I got latest of that as well just in case), carrier, blackbird: CL-USER> (ql:quickload "carrier")
To load "carrier":
Load 1 ASDF system:
carrier
; Loading "carrier"
.....................
;
; caught ERROR:
; READ error during COMPILE-FILE:
;
; Symbol "SOCKADDR-IN6" not found in the LIBUV package.
;
; Line: 52, Column: 66, File-Position: 2352
;
; Stream: #<SB-SYS:FD-STREAM
; for "file /root/.quicklisp/libuv-local-projects/cl-async/src/util/foreign.lisp"
; {100BA416A3}>
;
; compilation unit aborted
; caught 3 fatal ERROR conditions
; caught 1 ERROR condition |
Im using libuv 1.0.0 (not rc), maybe i need 1.1.0, 1.20, or 1.2.1? |
Maybe I'm missing latest cl-libuv? Let me get master of that and try again :) |
try now :) |
working :) |
Thanks a TON for the fast response! ;) |
Glad it worked! |
Actually I still get a warning (but works): CL-USER> (as:with-event-loop ()
(bb:catcher
(bb:alet ((result (carrier:request "https://www.apple.com/" :return-body t)))
(format t "result: ~s" result))
(t (e) (format t "error: ~a" e))))
WARNING:
Passing event-cb as the fourth argument to tcp-connect is now deprecated. Please use the :event-cb keyword instead.
result: #(60 33 68 79 67 84 89 80 69 32 104 116 109 108 62 10 60 104 116 109 |
Ok, try cl-async master now. The warning should be gone. |
Great! Warning is gone, thanks!! ;) |
I dont think carrier was brought up to date with latest cl-async/blackbird stuff and is causing issues in latest ql.
When using normal http
When using https
The text was updated successfully, but these errors were encountered: