Alexis Mas

For the record, I went with the second option. Configuring the block in the HTTP layer did the trick.

Peeking through the forks some of them have fixes in place https://github.com/evanob/graphql-cache/commit/80083cc76eb9cce5287b22f8728fa801049d57ac https://github.com/visorgg/graphql-cache/commit/e567c04a5a9b3539b072f2287c84e5dcc22008b8

Hey @OlegIlyenko I'm taking a look at this issue and would like to double check that the approach we use internally fits what you have in mind. This is our...

I've been digging through `AstSchemaMaterializer` and `AstSchemaBuilder`. To get to know a bit of the internals I extracted the extend methods into its own interface, you can find the details...

For testing with Robolectric you can change android-async-http ThreadPoolExecutor Here you can find some guidance https://groups.google.com/forum/#!msg/robolectric/Z3Yg04gL4hg/iwYlnvHAkO4J

@dvdrlee That's probably because `AsyncHttpClient` is using the Android implementation instead Robolectric's. To fix that you need to make sure that Robolectric is before Android classes on the classpath. @timsaunders...

When serializing, `ActiveJob` only support certain type of objects, according to the [SerializationError docs](http://edgeapi.rubyonrails.org/classes/ActiveJob/SerializationError.html): > Raised when an unsupported argument type is set as a job argument. We currently support...

@aruprakshit No, I didn't had a chance to look further into it.

Yes, we have the same problem. We ended up using an ENV var for using one adapter of the other. That way we can create the DB in CI and...

Any news about this? I'm using the latest GWT Maps version from Maven central and I'm stilll having this issue. EDIT: As a workaround adding the latest version to my...