Brendan Loudermilk
Brendan Loudermilk
Getting this same error, unfortunately. Pure Ruby works fine, but native is failing silently. @joshdevins did you ever find a solution for this?
@joshdevins Thanks for the update. I'm actually using the default Redis DB ("0" I guess) and still having issues with the native worker. Is this what you experienced? @paulasmuth Any...
It seems that the agent receives the `gateway:close` event when this happens (I think, it's hard to tell because we're using Node clustering), so I've just added some code to...
Restarting the workers as I mentioned above is working for us as a temporary solution, but I have a feeling the logic for the `gateway.close` handler should be changed so...
After updating the logic in the `gateway.close` handler, apnagent can now recover from these SSL errors gracefully. I'm running an updated version on my fork. Let me know if you're...
@logicalparadox I'll take a look at the test harness and see if I can simulate both! Thanks for the response.
I added a connection timeout to my fork, which fixed this issue. Let me know if you'd like a PR.
Thanks everyone for the responses so far–your promptness and thoughtfulness do well to answer my original question. @thiagopradi I know first hand the reality of past OSS work becoming personally...
"Useless" is pretty harsh ;)
@pmackay I'm hoping to use this gem for an OASv3 schema which relies heavily on the `components` section. Did you manage to make any progress here that you would want...