Jira (PUP-9077) Inconsistent undef value received by 4.x API Ruby functions after touched by 3.x Ruby function

[Sean Millichamp (JIRA)]

Title: Message Title

Sean Millichamp created an issue   Puppet / PUP-9077 Inconsistent undef value received by 4.x API Ruby functions after touched by 3.x Ruby function Issue Type: Bug Affects Versions: PUP 5.5.3 Assignee: Unassigned Created: 2018/08/21 7:31 AM Priority: Normal Reporter: Sean Millichamp While trying to use the Stdlib function to_yaml() I believe I have discovered a bug in how Puppet handles data returned from Ruby 3.x API functions versions when passed into 4.x Ruby functions. It is easiest to explain with a reproducer. Give this code, where func3() and func4() are just Ruby API 3.x and 4.x functions respectively that each just return the value they were passed: $orig_hash = { 'mykey' => undef, 'otherkey' => 'test', }   $func4_hash = func4($orig_hash) notice("func4_hash: ${func4_hash}") notice("func4_hash_json: ${to_json($func4_hash)}") notice("func4_hash_yaml: ${to_yaml($func4_hash)}")   $func3_hash = func3($orig_hash) notice("func3_hash: ${func3_hash}") notice("func3_hash_json: ${to_json($func3_hash)}") notice("func3_hash_yaml: ${to_yaml($func3_hash)}") I get this output: $ puppet apply --modulepath=. test/test.pp Notice: Scope(Class[main]): func4_hash: {mykey => , otherkey => test} Notice: Scope(Class[main]): func4_hash_json: {"mykey":null,"otherkey":"test"} Notice: Scope(Class[main]): func4_hash_yaml: --- mykey: otherkey: test   Notice: Scope(Class[main]): func3_hash: {mykey => , otherkey => test} Notice: Scope(Class[main]): func3_hash_json: {"mykey":"undef","otherkey":"test"} Notice: Scope(Class[main]): func3_hash_yaml: --- mykey: :undef otherkey: test   Notice: Compiled catalog for msp-pumtl31.msp.secure-24.net in environment production in 0.02 seconds Notice: Applied catalog in 0.01 seconds Note how the original data structure is correctly passed to the 4.x function with a nil value the first time, but after passing through a 3.x function the 4.x function now receives :undef and not nil. The expected behavior is that a 4.x Ruby function would always receive nil when passed a Puppet undef value, regardless of whether it has passed through a 3.x style function or not. Thank you. Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.