Hi team, Since moving from Ruby v 2.5.1 to 2.7.5 we've seen a spike in these error messages from this library. Is this a known issue or should we be on an earlier Ruby version?