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
I would really appreciate it if somebody told me what the plans are for this gem. I would guess that a lot of custom types that are built using this gem will fail on Ruby 3.2 and thus Puppet8. So I would guess somebody at Perforce/Puppet would have a plan for this?
@hajee I'm sorry I didn't get back to you earlier, I was out of the office when you initially pinged me on this ticket.
I created a ticket in our system, https://tickets.puppetlabs.com/browse/PUP-11866, to track this issue.
I don't have an expected timeline but this issue is now on our radar. Thank you for reporting this.
Munging fails on Integer data type when passed value is an integer or a float
In Ruby 3.2, the Integer and float data type no longer supports the
=~
operator. Causing correct values passed to te munger to fail.Running the unit tests on Ruby 3.2 shows all these errors. The log is attached to this issue.
Environment
Additional Context
Add any other context about the problem here.
unit-test.log
The text was updated successfully, but these errors were encountered: