Jira (PUP-11866) Puppet-resource_api bug with ruby 3.2 and integer munging

[Christopher Thorn (Jira)]

Christopher Thorn created an issue

Puppet / PUP-11866 Puppet-resource_api bug with ruby 3.2 and integer munging Issue Type: Bug Assignee: Unassigned Created: 2023/05/24 1:05 PM Priority: Normal Reporter: Christopher Thorn Github user Hajee has submitted the following issue: 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. In the linked issue there is an attached log of specs running with a number of failures, here is an example of one: 11) Puppet::ResourceApi::DataTypeHandling#try_mungify(type, value) with a Optional[Float] type with 1 as value returns no value Failure/Error: if value =~ %r{^-?\d+$} || value =~ Puppet::Pops::Patterns::NUMERIC   NoMethodError: undefined method `=~' for 1:Integer Add Comment

This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)

[Tony Vu (Jira)]

Tony Vu updated an issue

Puppet / PUP-11866 Puppet-resource_api bug with ruby 3.2 and integer munging

Change By: Tony Vu Epic Link: PUP-11660

Add Comment

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-11866

Re: Puppet-resource_api bug with ruby 3.2 and integer munging Need to update https://github.com/puppetlabs/puppet-resource_api/blob/edbf55a7bd39ab1fe7426d6610a630b07753bcc3/.github/workflows/rspec_tests.yaml#L18-L20 to include Ruby 3.2 also

Add Comment