Hendrik
Hendrik
A dirty trick to resolve it would be to unset the Content-Encoding header in https://github.com/seancribbs/webmachine-ruby/blob/master/lib/webmachine/errors.rb#L14 because the length is also for the unencoded response.
Dunno if I would close it, since it is a bug
Maybe we could add a run! method to all adapters which have the ability to run in the background? @seancribbs @bethesque
Celluloid is a "wrapper" around Thread and Mutex, the Reel Adapter forces the Thread in which Reel runs to run in the foreground, making it impossible to run other stuff...
I know my stance is rather restrictive when it comes to cryptography, but it shouldn't be run in the same process as the "business logic". Have you taken a look...
can it be done with travis that each adapter runs in its own instance?
One could use a IO.pipe and wait on it till the server is started
``` ruby rd, wr = IO.pipe Thread.new { puts rd.read rd.close } Thread.new { wr.write('initialized') wr.close } ``` Or with a queue ``` ruby queue = Queue.new Thread.new { puts...
Got new errors from HTTPkit now, https://travis-ci.org/seancribbs/webmachine-ruby/builds/38243104
Does https://github.com/seancribbs/webmachine-ruby/blob/master/lib/webmachine/spec/adapter_lint.rb#L36 get run every time it checks something? it looks totally like it..