-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch from Typheous to Faraday #37
Comments
Thank you for bringing this up. We'll be working on switching to Faraday shortly. |
1 task
@NuckChorris We've now switched to Faraday in |
@jasonbosco We are running v3.0.0 and everything so far looks good |
Thank you for confirming! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Hi! I see this gem uses Typheous as an HTTP library. Unfortunately, Typheous is poorly-maintained (no commits in two years!) and often segfaults on Apple Silicon when combined with forking processes (a very common practice in Ruby). As this is a library, my recommendation is to switch to Faraday which allows users to switch the underlying HTTP library to something which doesn't segfault.
Noticed because I started having this happen more locally again (I cannot consistently reproduce, unfortunately):
The text was updated successfully, but these errors were encountered: