Skip to content
  • Jean Boussier's avatar
    a3d05309
    Get rid of `ForkTracker.check!` · a3d05309
    Jean Boussier authored
    Now that we require Ruby 3.1, we can assume `Process._fork` is
    defined on MRI, hence we can trust that our decorator will
    reliably detect forks so we no longer need to check the if
    the pid changed in critical spots.
    a3d05309
    Get rid of `ForkTracker.check!`
    Jean Boussier authored
    Now that we require Ruby 3.1, we can assume `Process._fork` is
    defined on MRI, hence we can trust that our decorator will
    reliably detect forks so we no longer need to check the if
    the pid changed in critical spots.
Loading