Michael Oliver
Michael Oliver
@davidyaha this PR should be passing tests now and ready to merge. For some context, my company experienced issues where we had around ~50k subscribers, and this was causing the...
In terms of splitting this into multiple commits, I think it would be a lot of work to separate the 1.0.5 vs. style changes. A lot of code was auto-generated...
@benwilson512 I was able to find a solution to the second problem of having the server reconnect. We use a `GenServer` to manage our `Statix` connection, which looks a bit...
> Just to clarify - what you specified under "You should get a GraphQL error like the following" is the current behavior, yes? Yes
Similar test failure from a Travis build: ```elixir 1) test clients exit if the server dies handling a message (Thrift.Generator.ServiceTest) test/thrift/generator/service_test.exs:396 No message matching {:EXIT, ^client, {:error, :closed}} after 100ms....
This sounds great, I love the idea of being able to plug custom middleware into the middle of the `stack` to do things like tracing or logging. I think this...
This is a very well-thought-out approach, thanks for doing this @fishcakez. I believe it adds a couple layers of complexity by now having multiple protocols to reason about (`Thrift.Serializable` as...
Bit late to the party, but I will add that our infrastructure still relies on Kafka 0.8.1.1 quite a bit. There have been some efforts recently to upgrade, though as...
Ran into this same issue on Elixir 1.3.4, OTP 18. Managed to fix it by doing a `mix deps.update recon`. `mix.lock` change looks like: ```diff - "recon": {:hex, :recon, "2.3.2",...