You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
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: