Monday, December 16, 2019
To provide a bit of background: until now, we used Unicorn in production so our thread-safe issues weren't a problem for us (we don't use threads in our code, even though some gems may do). And we tested with RSpec and Capybara, but without `js: true` (so without a server thread).
Now with system tests though, if we want to test JS, thread-safety becomes an issue since a server thread is spinned up and it might access the same code that our tests do. Is my assumption correct?
On Monday, 16 December 2019 15:57:18 UTC+2, San Ji wrote:
If you are running your Ruby code
on MRI (the official implementation) there is no way to make your Ruby code any threadsafer. They have global interpreter lock in place.Segfaults generally don't cause by Ruby code, and when it does it is a bug of the interpreter itself.
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/75b1b6e3-e6fb-456d-986b-d70fb13c89d9%40googlegroups.com.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment