Laurent

Thanks @natebird I will try to see those workarounds. Any ideas on if and when CanCan will support strong_parameters ? Thanks again Edit: As stated in https://github.com/ryanb/cancan/issues/571 one of the...

I changed for Cancancan and did not have to change even one line of code for it to work. And FYI the fix I talked about in my first post...

The request you mention is fine on it's own but we're actually fetching the hid inside a much more complex one that has many joins and sub-queries which is why...

this is actually linked to https://github.com/bripkens/lucene/issues/38

We've been facing some similar issue. Here is what we're doing, using java: In the query module ```java @Component // We are currently suppressing the warnings here because we weren't...

Hi, This is a fork of the original project. I never made or uploaded any builds besides the `1.03-port-java7` so yeah, 1.02 is an original java 8 build. So indeed,...

Hi @benjchristensen, @abersnaze Just as a follow up on this, would it be OK to have the following: ``` java public static Observable from(final ListenableFuture future) { from(future, Schedulers.computation()); }...

No, I haven't been able to reproduce it yet, only observe it in production. It isn't recent. I've tried switching to previous RxNetty version and still have the same behavior.

I currently fixed it using `switchIfEmpty(DEFAULT_RESPONSE.doOnNext(r -> metricFallback.increment()))` so I can track how often it happens. Visually, we oberved approximatly 5 of those per second for 1500QPS so that seems...

Also FYI, this is the same RxNetty client that has the pool exhausted problem (#503)