Jira (PUP-11515) Negative Lookbehind Regex Causes Duplicate Node Definition Errors

[Josh Cooper (Jira)]

Title: Message Title

Josh Cooper commented on PUP-11515   Re: Negative Lookbehind Regex Causes Duplicate Node Definition Errors Thanks for the detailed report. The problem is due to the way puppet keeps track of "regex" types of node names here. Both regexp are normalized to the same string: irb(main):005:0> @name = /(?<!a)sync/ => /(?<!a)sync/ irb(main):006:0> "__node_regexp__#{@name.source.downcase.gsub(/[^-\w:.]/,'').sub (/^\.+/,'')}" => "__node_regexp__async" irb(main):007:0> @name = /async/ => /async/ irb(main):008:0> "__node_regexp__#{@name.source.downcase.gsub(/[^-\w:.]/,'').sub (/^\.+/,'')}" => "__node_regexp__async" One simple fix is to specify "async" as a string and not a regex: node /(?<!a)sync/ { ... } node async { ... } Add Comment   This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.440913.1647801729000.16773.1650669300125%40Atlassian.JIRA.