Closed nightshade427 closed 9 years ago
It looks like it does this with the latest cl-async (using libuv) as well.
It used to return from event loop when there was an error signaled, now it just hangs. :(
Hey, can you try again? We made a number of changes and improvements to the error handling system in cl-async. I'm wondering if this clears things up for you.
Nope still does it. I think I'm going to switch over completly to blackbird instead of continuing to use cl-async-future. Will let you know how it goes.
Hey any word on this?
I just tried to repo and can't. I think it's good.
Why does this hang when using branch using "pre libuv merge" release (cant switch over till the bugs in libuv cl-async and carrier are fixed up, see https://github.com/orthecreedence/carrier/issues/5)
It hangs and doesnt exit, even though carrier triggered (signal-error) and with-event-loop should catch it and exit (it used to)
It hangs with this as well:
But, this works as expected and exits the event-loop, with the same branches/releases used but using drakma instead (getting same error, the event loops returns).