Jira (FACT-968) Add/verify AIX timezone support
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-968 Add/verify AIX timezone support Change By: Kylo Ginsberg Sprint: Client2015-05-27 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-891) dynamic library support cannot determine first_load on AIX
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-891 dynamic library support cannot determine first_load on AIX Change By: Kylo Ginsberg Sprint: Client2015-05-27 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-971) Add AIX memory_resolver.cc
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-971 Add AIX memory_resolver.cc Change By: Kylo Ginsberg Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-969) Add AIX networking_resolver.cc
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-969 Add AIX networking_resolver.cc Change By: Kylo Ginsberg Sprint: Client2015-05-27 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-972) Compare facter 3 AIX output with facter 2 AIX output on AIX 6.1
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-972 Compare facter 3 AIX output with facter 2 AIX output on AIX 6.1 Change By: Kylo Ginsberg Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-974) Compare facter 3 AIX output with facter 2 AIX output on AIX 5.3
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-974 Compare facter 3 AIX output with facter 2 AIX output on AIX 5.3 Change By: Kylo Ginsberg Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-973) Compare facter 3 AIX output with facter 2 AIX output on AIX 7.1
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-973 Compare facter 3 AIX output with facter 2 AIX output on AIX 7.1 Change By: Kylo Ginsberg Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-892) load_average resolver is not really posix
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-892 load_average resolver is not really posix Change By: Kylo Ginsberg Sprint: Client2015-05-27 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-967) Add AIX operating_system_resolver.cc
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-967 Add AIX operating_system_resolver.cc Change By: Kylo Ginsberg Sprint: Client2015-05-27 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3774) puppet fails to manipulate user's group membership if group name has space in it
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3774 puppet fails to manipulate user's group membership if group name has space in it Change By: Kylo Ginsberg Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3774) puppet fails to manipulate user's group membership if group name has space in it
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3774 puppet fails to manipulate user's group membership if group name has space in it Change By: Kylo Ginsberg Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Henrik Lindberg commented on PUP-4463 Re: split with just Regexp (unparameterized type) splits on whitespace This is targeting 4.1.0 since the split function in 3.x does not use the Regexp hash at all - it was a new feature added in 4.0.0. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Henrik Lindberg commented on PUP-4513 Re: Language spec does not document behavior of access operator on resource references Will review and make sure it is reflected in the specification. Getting attributes from resources depends on the order of evaluation - it is not possible to get values set via Resource defaults, nor to get values of meta parameters (since these are set after user code has stopped evaluating; i.e. blanks are filled in by the compiler at the end using collectors with overrides and attributes set at the resource type level (Resource Default Expressions). The example in evil made manifests show exactly that. It may very well be that the spec is vague in this area because we did not fully understand what was actually possible in various situations. And we discussed for a long time if we should try to formalize behavior that is driven by the compiler as opposed the language - you will find the spec vague in several areas that deal with resources, collectors, overrides, defaults and meta parameters (or it may say that the behavior is undefined). I will review the parts of the spec that relate to this and make it clearer. Not certain what we want the specification to say; simply that it is evaluation order dependent (you have to know how the evaluator and compiler does it), or if it should specify how the compiler does this now (which is perhaps not how we really want it to work, and to be honest, we really don't know all the corner cases), or state that it is undefined? We may want the documentation to say something different like you can only read attributes that are explicitly set. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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
Jira (PUP-4482) Add support for PE platforms/repos/paths
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4482 Add support for PE platforms/repos/paths Change By: Kylo Ginsberg Sprint: Client2015-05-27 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-802) cannot use text-based external facts to represent empty fact-values.
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Facter / FACT-802 cannot use text-based external facts to represent empty fact-values. Change By: Kylo Ginsberg Assignee: EricSorenson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1470) PR (1374): r(maint) make facts response streaming - wkalt
Title: Message Title gepetto-bot commented on PDB-1470 Re: PR (1374): r(maint) make facts response streaming - wkalt pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1139/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2638) Missing dependent directory from Puppet Agent install causes issues with resource graphing
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2638 Missing dependent directory from Puppet Agent install causes issues with resource graphing Change By: Kylo Ginsberg Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-910) Solaris is missing the LDom facts
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-910 Solaris is missing the LDom facts Change By: Kylo Ginsberg Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-918) Virtualization facts are incorrect in SPARC Solaris LDoms
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-918 Virtualization facts are incorrect in SPARC Solaris LDoms Change By: Kylo Ginsberg Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-909) Processor facts are incorrect in SPARC Solaris
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-909 Processor facts are incorrect in SPARC Solaris Change By: Kylo Ginsberg Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-911) manufacturer and productname facts are missing in SPARC Solaris
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-911 manufacturer and productname facts are missing in SPARC Solaris Change By: Kylo Ginsberg Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-950) Switch to a tagged version of Leatherman
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-950 Switch to a tagged version of Leatherman Change By: Kylo Ginsberg Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-912) FQDN reported as just hostname in SPARC
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-912 FQDN reported as just hostname in SPARC Change By: Kylo Ginsberg Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-915) Serialnumber fact doesn't resolve in SPARC Solaris
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-915 Serialnumber fact doesn't resolve in SPARC Solaris Change By: Kylo Ginsberg Sprint: Client2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Henrik Lindberg commented on PUP-4374 Re: Splatting attributes into an amended attribute block isn't supported Eric Thompson here is a hint: --parser future Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3341) Puppet apply breaks when an ENC returns an environment
Title: Message Title
Kurt Wall updated an issue
Puppet / PUP-3341
Puppet apply breaks when an ENC returns an environment
Change By:
Kurt Wall
GiventhefollowingENCscript(/tmp/enc){code}#!/bin/shecho'classes:[]'echo'environment:production'{code}andtwomanifests1.amanifesttoapply(/tmp/manifest.pp){code}notify{'itworks':}{code}2.apseudosite-manifest(/tmp/site.pp){code}notify{'FAIL':}{code}Invoking{{puppetapply}}inthefollowingfashionshouldprintitworks,butdoesnot.{noformat}$bundleexecpuppetapply/tmp/manifest.pp--node_terminusexec--external_nodes/tmp/enc--manifest/tmp/site.pp...Notice:FAIL{noformat}--QARiskAnalysisRiskLevel: Medium High(abrokenapplycanbreakproduction) Probability:High(itseemshighlylikelyanENCwillreturnanenvrionment)Impact:Medium({{puppetapply}}shouldwork)TestLevel:Acceptance(crossescomponentboundaries)
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1468) Maven keeps caching the old puppetdb during during ezbake builds
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1468 Maven keeps caching the old puppetdb during during ezbake builds Issue Type: Bug Affects Versions: PDB 3.0.0 Assignee: Unassigned Created: 2015/05/01 6:52 AM Priority: Normal Reporter: Kenneth Barber Right now we have a problem whereby the ezbake build step in our pipeline is caching the puppetdb jar for 24 hours. This means we don't get a new working jar that matches acceptance tests and such, until 24 hours has passed and the new jar with the new code is downloaded. This is giving us false negatives, point in case: https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys/392/ We need to figure out a way to either remove this cache, use our own per job maven repo per run, or perhaps specifically target a particular revision of the jar instead. Add Comment
Jira (PUP-3931) Upgrading Puppet package within Puppet agent run on EL7 results in bad package state
Title: Message Title Orion Poplawski commented on PUP-3931 Re: Upgrading Puppet package within Puppet agent run on EL7 results in bad package state Filed PUP-4512 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Orion Poplawski commented on PUP-4512 Re: systemctl restart puppet fails to restart puppet Actually, with Fedora 22, puppet 4.0.0, the restart completes fine, but the old child process sticks around: systemctl status puppet ● puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2015-05-01 11:09:17 MDT; 2min 3s ago Main PID: 844 (start-puppet-ag) CGroup: /system.slice/puppet.service ├─844 /bin/sh /usr/bin/start-puppet-agent agent --no-daemonize └─849 /usr/bin/ruby-mri /usr/bin/puppet agent --no-daemonize systemctl restart puppet systemctl status puppet ● puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2015-05-01 11:11:54 MDT; 16s ago Main PID: 1622 (start-puppet-ag) CGroup: /system.slice/puppet.service ├─ 849 /usr/bin/ruby-mri /usr/bin/puppet agent --no-daemonize ├─1622 /bin/sh /usr/bin/start-puppet-agent agent --no-daemonize └─1623 /usr/bin/ruby-mri /usr/bin/puppet agent --no-daemonize so now there are two puppet agents running. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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,
Jira (FACT-965) facter doesn't run under jruby
Title: Message Title
Eric Thompson updated an issue
Facter / FACT-965
facter doesn't run under jruby
Change By:
Eric Thompson
I'veinstalledpuppet-agentandpuppetserverfromPuppetSC1onRHEL6.HoweverIcan'tenablecfacter:{code}[root@host~]#puppetconfig--sectionmasterprintcfactertrue{code}{code}[root@host~]#/etc/init.d/puppetserverstartStartingpuppetserver:[OK][root@host~]#[FAILED]{code}{code}==/var/log/puppetlabs/puppetserver/puppetserver-daemon.log==ArgumentError:cfacterversion0.2.0orlaterisnotinstalled.{code}Disablingcfacterallowsmetorunpuppetserver. note:turnontheCIintegrationjobafterthisismerged. h3.QArisk:highprobability:highseverity:hightestlevel:acceptance(existing,butneedstorunagainstserver)
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1469) puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package
Title: Message Title John Duarte commented on PDB-1469 Re: puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package Info from Matthaus Owens [9:49 AM] Matthaus Owens: @JohnDuarte got added inhttps://github.com/puppetlabs/puppetdb/commit/660522fe5998056d563815de32bb835098c45cb8 Link [image: https://github.com/favicon.ico] Commit 660522f to puppetlabs/puppetdb by Erik Daln (#23422) Use JSON in terminus instead of PSON [9:50 AM] Matthaus Owens: i'm not sure we should pull it out in 2.3.x though, but it will definitely be gone in pdb 3.0 [9:52 AM] Matthaus Owens: @JohnDuarte extra info. puppet 3.x already pulls in rubygem-json or whatever, so it should be safe to remove. if they are on puppet 3.x they have json from puppet's dependency chain. if they are on 4.x json is in the AIO ruby Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-1448 'replace facts' failing due to foreign key constraint issue Change By: Rob Browning Assignee: RobBrowning Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1469) puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package
Title: Message Title John Duarte created an issue PuppetDB / PDB-1469 puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package Issue Type: Bug Assignee: Unassigned Created: 2015/05/01 9:51 AM Priority: Normal Reporter: John Duarte Trying to install puppetdb on a puppetserver and PC1 system. Attempting to install rubygem-json results in a package not found, but yet the puppetdb-terminus package fails due to the dependency. $ yum install -y rubygems ruby-sqlite3 rubygem-activerecord rubygem-json Loaded plugins: product-id, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. Setting up
Jira (PUP-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Orion Poplawski created an issue Puppet / PUP-4512 systemctl restart puppet fails to restart puppet Issue Type: Bug Affects Versions: PUP 4.0.0, PUP 3.7.5 Assignee: Unassigned Created: 2015/05/01 10:07 AM Environment: Fedora Linux Labels: systemd Priority: Critical Reporter: Orion Poplawski Adding KillMode=process to puppet.service to fix PUP-3931 appears to have broken systemctl restart puppet for me. systemctl status puppet ● puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled) Active: active (running) since Fri 2015-05-01 11:02:35 MDT; 11s ago Main PID: 18662 (start-puppet-ag) CGroup: /system.slice/puppet.service ├─18662 /bin/sh /usr/bin/start-puppet-agent agent
Jira (PUP-4512) systemctl restart puppet fails to restart puppet
Title: Message Title
Orion Poplawski updated an issue
Puppet / PUP-4512
systemctl restart puppet fails to restart puppet
Change By:
Orion Poplawski
AddingKillMode=processtopuppet.servicetofixPUP-3931appearstohavebrokensystemctlrestartpuppetforme. {noformat} #systemctlstatuspuppet●puppet.service-PuppetagentLoaded:loaded(/usr/lib/systemd/system/puppet.service;enabled)Active:active(running)sinceFri2015-05-0111:02:35MDT;11sagoMainPID:18662(start-puppet-ag)CGroup:/system.slice/puppet.service├─18662/bin/sh/usr/bin/start-puppet-agentagent--no-daemonize└─18665/usr/bin/ruby-mri/usr/bin/puppetagent--no-daemonize#systemctlrestartpuppet#systemctlstatuspuppet●puppet.service-PuppetagentLoaded:loaded(/usr/lib/systemd/system/puppet.service;enabled)Active:failed(Result:exit-code)sinceFri2015-05-0111:03:03MDT;4sagoProcess:19066ExecStart=/usr/bin/start-puppet-agentagent${PUPPET_EXTRA_OPTS}--no-daemonize(code=exited,status=1/FAILURE)MainPID:19066(code=exited,status=1/FAILURE)CGroup:/system.slice/puppet.service└─18665/usr/bin/ruby-mri/usr/bin/puppetagent--no-daemonize {noformat} Theoldchildpuppetprocessisstillaround.Straceshows: {noformat} 19199restart_syscall(...resuminginterruptedcall...unfinished...19245restart_syscall(...resuminginterruptedcall...unfinished...19198wait4(-1,unfinished...19199...restart_syscallresumed)=-1ETIMEDOUT(Connectiontimedout)19199futex(0xb556d0,FUTEX_WAKE_PRIVATE,1)=019199futex(0xb55654,FUTEX_WAIT_BITSET_PRIVATE,15,{359644,166273339},unfinished...19198...wait4resumed0x7ffc8ab93080,0,NULL)=?ERESTARTSYS(ToberestartedifSA_RESTARTisset)19198---SIGTERM{si_signo=SIGTERM,si_code=SI_USER,si_pid=1,si_uid=0}---19198+++killedbySIGTERM+++19199...futexresumed)=-1ETIMEDOUT(Connectiontimedout)19199futex(0xb556d0,FUTEX_WAKE_PRIVATE,1)=019199futex(0xb55654,FUTEX_WAIT_BITSET_PRIVATE,17,{359649,166794009},detached... {noformat} I'mseeingthiswithFedora21and3.7.5andFedora22w/4.0.0.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Wyatt Alt commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Simon Oxwell Wow, nice going! Thanks for tracking it down so specifically. We have the issue reproduced and are testing a fix currently. Duncan McNaught Thanks for that data. If your scenario matches the one Simon is describing I don't think we need anything else. We'll update this thread once we release a bugfix – hopefully sometime next week. Thanks again for the help, guys! Wyatt Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-956) Update puppet-agent#master to build facter#master, remove cfacter
Title: Message Title
Eric Thompson updated an issue
Facter / FACT-956
Update puppet-agent#master to build facter#master, remove cfacter
Change By:
Eric Thompson
UpdateforbothWindowsandLinux.Thatmeansfixingpuppet_for_the_winandpuppet-agent.Removethecfactercomponent,andupdatethefactercomponenttobuildfacter#mastercorrectly(essentiallythecfactercomponent).Alsoenabletestingnativefacterbyadding{{maketest}}tothebuildtarget. note:turnontheCIintegrationjobwhenthisismerged.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4374 Splatting attributes into an amended attribute block isn't supported Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4212) Create a Splay Start Time Setting
Title: Message Title Nick Walker updated an issue Puppet / PUP-4212 Create a Splay Start Time Setting Change By: Nick Walker Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Eric Thompson assigned an issue to Henrik Lindberg Puppet / PUP-4374 Splatting attributes into an amended attribute block isn't supported Change By: Eric Thompson Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title
Eric Thompson commented on PUP-4374
Re: Splatting attributes into an amended attribute block isn't supported
h. this doesn't seem to work in 3.x on ubuntu14 at 3.x SHA: 17b75e2
[root@mupkgq3reracnf3 ~]# puppet apply splat_attrs.pp
Error: Could not parse for environment production: Syntax error at '*'; expected '}' at /root/splat_attrs.pp:3 on node mupkgq3reracnf3.delivery.puppetlabs.net
Error: Could not parse for environment production: Syntax error at '*'; expected '}' at /root/splat_attrs.pp:3 on node mupkgq3reracnf3.delivery.puppetlabs.net
[root@mupkgq3reracnf3 puppet]# puppet apply -e '$myattrs = {message = from a reference attribute block} Notify[first] { *= $myattrs }'
Error: Could not parse for environment production: Syntax error at '*'; expected '}' at line 1 on node mupkgq3reracnf3.delivery.puppetlabs.net
Error: Could not parse for environment production: Syntax error at '*'; expected '}' at line 1 on node mupkgq3reracnf3.delivery.puppetlabs.net
[root@mupkgq3reracnf3 puppet]# puppet apply -e '$myattrs = {message = from a reference attribute block} notify {extra: *= $myattrs }'
Jira (PUP-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Eric Thompson commented on PUP-4463 Re: split with just Regexp (unparameterized type) splits on whitespace validated on ubuntu14 at 3.x SHA: 17b75e2 [root@mupkgq3reracnf3 puppet]# puppet apply -e 'notice split(a;b;c;d,;)' --parser future Notice: Scope(Class[main]): [a, b, c, d] Notice: Compiled catalog for mupkgq3reracnf3.delivery.puppetlabs.net in environment production in 0.43 seconds Notice: Finished catalog run in 0.01 seconds [root@mupkgq3reracnf3 puppet]# puppet apply -e 'notice split(a;b;c;d,)' --parser future Notice: Scope(Class[main]): [a, ;, b, ;, c, ;, d] Notice: Compiled catalog for mupkgq3reracnf3.delivery.puppetlabs.net in environment production in 0.41 seconds Notice: Finished catalog run in 0.01 seconds [root@mupkgq3reracnf3 puppet]# puppet apply -e 'notice split(a;b;c;d,nil)' --parser future
Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilati
Title: Message Title Thomas Linkin commented on PDB-949 Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilation. I encountered this again while trying to do some catalog diffs (https://github.com/acidprime/puppet-catalog-diff). The solution was to disable trusted facts on the master, but there has to be a better way, right? I assume it has something to do with the fact that catalog being compiled does not match the cn of the cert requesting the catalog. Some sort of misalignment in security is causing a trusted variable to get set and interfere with the trusted facts var. This is probably close to what is happening with the time sync issue as well. I have done exactly nothing along the lines of actually tracking this back (the disable trusted data solution was a guess, a guess that worked) and am not even 100% sure this is a PDB issue, but this ticket is tracking an issue that includes this particular error message so whatever, good enough More research on the relevance and source of my issue is needed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Thomas Hallgren commented on PUP-4463 Re: split with just Regexp (unparameterized type) splits on whitespace Eric Thompson I'll have to refer to Henrik Lindberg's earlier comment on why this is targeted to 4.1.0 only. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Eric Thompson commented on PUP-4462 Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled calling this done enough Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Eric Thompson commented on PUP-4462 Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled validated on ubuntu14 at 3.x SHA: 17b75e2 [root@mupkgq3reracnf3 puppet]# puppet apply interp_heredoc.pp --parser future Notice: Scope(Class[main]): Variable standing apart: hi there Variable enjambed: heyhi there Variable with single backslash enjambed: \hi there Variable with double backslash enjambed: \\hi there Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4461) manifest changes are ignored when using hiera_include
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4461 manifest changes are ignored when using hiera_include Change By: Eric Thompson Assignee: QA EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1465) PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker
Title: Message Title gepetto-bot commented on PDB-1465 Re: PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1138/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilati
Title: Message Title Charlie Sharpsteen commented on PDB-949 Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilation. Thomas Linkin: The issue is that for puppet master --compile, facts retrieved from PuppetDB contain trusted as a fact. These are sent into the compiler which attempts to create top-scope variables for every fact. This fails, because the top-scope trusted variable cannot be altered during compilation. A normal node checkin avoids this problem because trusted is not mixed in with the facts — it arrives as a separate dataset that is added to the Node object. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4501) TypeCalculator instance_of? does not consider String type values.
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4501
TypeCalculator instance_of? does not consider String type values.
Change By:
Eric Thompson
The{{TypeCalculator.instance_of?}}methodfor{{PStringType}}onlychecksiftheincomingobjectisa{{String}}andifit'ssizeiscompliantwiththe{{size_type}}.Itdoesnotcheckifthetypehasvaluesand,ifso,ifthegivenstringisoneofthem.Thischeckmustbeadded. h3.QArisk:mediumprobability:medium(instance_of?onstringvalues)severity:medium(couldproduceincorrectresult)testlevel:unit
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4501) TypeCalculator instance_of? does not consider String type values.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4501 TypeCalculator instance_of? does not consider String type values. Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4499) The size_type is dropped when inferring common type for String types
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4499
The size_type is dropped when inferring common type for String types
Change By:
Eric Thompson
The{{TypeCalculator}}will loose lose the{{String.size_type}}whencomputingthecommontypeoftwo{{String}}typesthatbothhavea{{size_type}}.Thecorrectbehavioristocomputethecommontypeofthetwo.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4483) Add NotUndef type to the set of Puppet types
Title: Message Title Eric Thompson commented on PUP-4483 Re: Add NotUndef type to the set of Puppet types at validation: add test link in existing testcase Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4458) Refactor validation of 4.x parameter signatures
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4458 Refactor validation of 4.x parameter signatures Change By: Eric Thompson Thecodethatperformsvalidationofparameterswhencallingfunctions,lambdas,orinstantiatingresourceorclassdefinitionsresidesindifferentplacestodayandproducesdifferenterrormessages.Thiscodeshouldberefactoredsothatithandlesalltypesofparametervalidation.Thecodemustbeabletohandlebothpureindexedbasedparameterpassing(functionsandlambdas)andparameterspassedbyname(resourceandclassinstantiations). h3.QA risk:low(refactor)probability:mediumseverity:lowtestinglayer:unit/acceptance(as-is) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2315) function call error message about mis-matched arguments is hard to understand
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-2315
function call error message about mis-matched arguments is hard to understand
Change By:
Eric Thompson
ThenewfunctionAPIchecksthetypesofgivenargumentsandgivesanerror.Thiserrorishardtounderstandinseveralsituations:*whenalambdaisgivenwherenoneisacceptedsinceitonlyreportsthegivenCallabletypeasifitwasaregularparameter.Itshouldcallitoutexplicitly(sinceaCallableisanObject,itlooksliketheerrorisnotlegit).Callingthe{{assert_type}}functionwithalambdashowsthebaderrormessage.*Whenalambdaisexpected,butdoesnotmatch*Errorspewsoutalldetailsaboutthetypes(anarraywiththousandsofentriesisdisplayed)WeshouldimplementanExplainingTypeCalculatorthat:*explainswhyamatchfailed*isgiventhenamesoftheinputobjects*producesamessagewithareferencerootedatthegivennamethatshowswheretheerrorwasfound(e.g.{{$x\[key\]\[3\]-expectedX,gotY}})*reducesthedetailedtypeinformationindependenttypes(e.g.Tuple,Array,Hash,Enum)suchthatrepeatedsequencesarecompacted(asequenceof100Integersmaybedisplayedas{{Integer\{100\}}}Anerrormessagenow,maylooklikethis:{code}ErrorwhileevaluatingaMethodcall,function'each'calledwithmis-matchedargumentsexpectedoneof:each(Hash[Any,Any]hash,Callable[2,2]block)-argcount{2}each(Hash[Any,Any]hash,Callable[1,1]block)-argcount{2}each(Anyenumerable,Callable[2,2]block)-argcount{2}each(Anyenumerable,Callable[1,1]block)-argcount{2}actual:each(Tuple[Integer,Integer,Integer,Integer,Integer,Integer,Integer],Callable[Any,Any,Any])-argcount{2}atline1:29onnodefoonode{code}Ittakesawhiletofigureoutthattheerroristhatthegivenblocktotheeachfunctionhadthreeparameterswhere1or2wereexpected.Ifeachexpectedresultshowsthereasonforrejectionareshownitwoulddisplaysomethinglike:{code}ErrorwhileevaluatingaMethodcall,function'each'calledwithmis-matchedargumentsexpectedoneof:each(Hash[Any,Any]hash,Callable[2,2]block)-argcount{2}rejected:$block[parameter_count]is3where2wasexpectedeach(Hash[Any,Any]hash,Callable[1,1]block)-argcount{2}rejected:$block[parameter_count]is3where1wasexpectedeach(Anyenumerable,Callable[2,2]block)-argcount{2}rejected:$block[parameter_count]is3where2wasexpectedeach(Anyenumerable,Callable[1,1]block)-argcount{2}rejected:$block[parameter_count]is3where1wasexpectedactual:each(Tuple[Integer,Integer,Integer,Integer,Integer,Integer,Integer],Callable[Any,Any,Any])-argcount{2}atline1:29onnodefoonode{code}Or,itmaybeclearerifitdoesthis:{code}ErrorwhileevaluatingaMethodcall,function'each'calledwithmis-matchedargumentsexpectedoneof:1.each(Hash[Any,Any]hash,Callable[2,2]block)-argcount{2}2.each(Hash[Any,Any]hash,Callable[1,1]block)-argcount{2}3.each(Anyenumerable,Callable[2,2]block)-argcount{2}4.each(Anyenumerable,Callable[1,1]block)-argcount{2}actual:each(Tuple[Integer,Integer,Integer,Integer,Integer,Integer,Integer],Callable[Any,Any,Any])-argcount{2}atline1:29onnodefoonoderejectedbecause:1.$block[parameter_count]is3where2wasexpected2.$block[parameter_count]is3where1wasexpected3.$block[parameter_count]is3where2wasexpected4.$block[parameter_count]is3where1wasexpected{code}Andifweareabletodetectapattern(allcausedbycountbeing3),wecouldpointthatoutandattheendshow:{code}rejectedbecause:$block[parameter_count]is3...andpossiblythedetails1-n{code}Naturally,ifthereisonlyonesignature,thenumberingshouldbeskipped. h3.QA
Jira (FACT-965) facter doesn't run under jruby
Title: Message Title Kylo Ginsberg commented on FACT-965 Re: facter doesn't run under jruby suppose I'm just thinking of CI purity. It's unlikely we'd accidentally make changes to Facter 3 and Puppet 4 that break compatibility with Facter 2, but we'll have no CI coverage that would detect something like that. Ah yes, that's true. But one of the whole motivations for AIO was to reduce the kind of cross-version CI matrices implied by independently releasing different components. So to me that's basically upside. Anyway, worth discussing somewhere but I think it's OT in this ticket? Perhaps raise the issue on client@ or sth like that, otherwise the convo will be lost in the sands of Jira Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4511) Types Array[?], Hash[?,?], and Optional[?] are not assignable to themselfes
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4511
Types Array[?], Hash[?,?], and Optional[?] are not assignable to themselfes
Change By:
Eric Thompson
The{{TypeCalculator.assignable?}}methoddoesnotconsiderthetypes{{Array[?]}},{{Hash[?,?]}},and{{Optional[?]}}tobeassignabletothemselves. h3.QArisk:mediumprobability:mediumseverity:medium(workaroundsinsyntax/language)testlevel:unit
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4511) Types Array[?], Hash[?,?], and Optional[?] are not assignable to themselfes
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4511 Types Array[?], Hash[?,?], and Optional[?] are not assignable to themselfes Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4500) Common type of two strings where only one have values is too restricted
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4500
Common type of two strings where only one have values is too restricted
Change By:
Eric Thompson
The{{TypeCalculator.common_type(t1,t2)}}method,whengiventwoStringswhereonlyoneoftheStrings have has valueswillyieldacommonStringtypethatisrestrictedtothosevalues.Thisiswrong.Ifoneofthetypesisunrestricted,thenthecommontypemustalsobeunrestricted.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4500) Common type of two strings where only one has values is too restricted
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4500 Common type of two strings where only one has values is too restricted Change By: Eric Thompson Summary: Commontypeoftwostringswhereonlyone have has valuesistoorestricted Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4499) The size_type is dropped when inferring common type for String types
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4499
The size_type is dropped when inferring common type for String types
Change By:
Eric Thompson
The{{TypeCalculator}}willlosethe{{String.size_type}}whencomputingthecommontypeoftwo{{String}}typesthatbothhavea{{size_type}}.Thecorrectbehavioristocomputethecommontypeofthetwo. h3.QArisk:mediumprobability:lowseverity:mediumtestlevel:unit
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4500) Common type of two strings where only one has values is too restricted
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4500 Common type of two strings where only one has values is too restricted Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4499) The size_type is dropped when inferring common type for String types
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4499 The size_type is dropped when inferring common type for String types Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4513) Language spec does not document behavior of access operator on resource references
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-4513 Language spec does not document behavior of access operator on resource references Issue Type: Task Assignee: Unassigned Components: Language Created: 2015/05/01 11:06 AM Labels: specification Priority: Normal Reporter: Nicholas Fagerlund The section on the access operator alludes to its use on resource references, but there isn't a peer subsection on resource references to go along with the array/string/hash sections. This file in evil made manifest shows most of the tricky bits that the spec doesn't cover. There may also be subtleties I don't know about yet. Add Comment
Jira (PUP-4500) Common type of two strings where only one has values is too restricted
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4500
Common type of two strings where only one has values is too restricted
Change By:
Eric Thompson
The{{TypeCalculator.common_type(t1,t2)}}method,whengiventwoStringswhereonlyoneoftheStringshasvalueswillyieldacommonStringtypethatisrestrictedtothosevalues.Thisiswrong.Ifoneofthetypesisunrestricted,thenthecommontypemustalsobeunrestricted. h3.QArisk:mediumprobability:lowseverity:medium(orlow,it'sjustabitrestricting)testlevel:unit
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4483) Add NotUndef type to the set of Puppet types
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4483
Add NotUndef type to the set of Puppet types
Change By:
Eric Thompson
ThePuppettypesystemhascurrentlynowayofdefiningatypewiththemeaninganyvalueexceptundefinedandhencenowayofdifferentiatingbetweenamissingvalueandagivenvalueofanytype(theexisting{{Any}}typeaccepts{{undef}}values).Theproblembecomesapparentwhendeclaringahashwherecertainentriesmustbepresentbutthevalueisunrestricted.Addinga{{NotUndef}}wouldresolvetheissuebutthesolutionisnotidealsincethevaluethenbecomesrestricted(itcannotbe{{undef}}).It'sstillnotpossibletodifferentiatebetweenamissingkeyandakeywiththevalueundef.Thisdifferentiationcanbesignificantwhenvariantsareusingdifferentsetsofkeys.Toreallysolvetheproblem,wewouldneedawaytodeclarea{{Struct}}keytoberequiredoroptionalinadditiontoaddingthe{{NotUndef}}type.Onewayofdoingthiswouldbetocheckifthevalueisoftype{{Optional}},andifitis,considerthekeytobeoptional.{{Optional[Any]}}wouldthenbedifferentfrom{{Any}}inthattheformeraffectsthekey. h3.QArisk:mediumprobability:lowseverity:mediumtestlevel:unit
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4483) Add NotUndef type to the set of Puppet types
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4483 Add NotUndef type to the set of Puppet types Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Simon Oxwell commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Hi Wyatt - sorry I haven't been able to get this over the last few days, had other operational priorities. I've now got a new server playing up, and it's not being blocked by a structured fact: puppetdb=# DELETE FROM fact_values fv puppetdb-#WHERE fv.id in (2347921,5398,5421,1525955,2374767,2301540,2373170,5416,2301540,5407,2374770,2374768,2374770,2374767,2374769,5398,2374771) puppetdb-# AND NOT EXISTS (SELECT 1 FROM facts f puppetdb(#WHERE f.fact_value_id in (2347921,5398,5421,1525955,2374767,2301540,2373170,5416,2301540,5407,2374770,2374768,2374770,2374767,2374769,5398,2374771) puppetdb(# AND f.fact_value_id = fv.id puppetdb(# AND (f.factset_id, f.fact_path_id) NOT in ((93,148),(93,79),(93,4731),(93,4723),(93,131),(93,68),(93,48),(93,4720),(93,27),(93,4836),(93,127),(93,86),(93,40),(93,103),(93,142),(93,92),(93,105))); ERROR: update or delete on table fact_values violates foreign key constraint fact_value_id_fk on table facts DETAIL: Key (id)=(5407) is still referenced from table facts.
Jira (PDB-1467) puppetdb module has ordering problem with read_database.ini
Title: Message Title Chris Spence created an issue PuppetDB / PDB-1467 puppetdb module has ordering problem with read_database.ini Issue Type: Bug Assignee: Unassigned Created: 2015/05/01 12:51 AM Priority: Normal Reporter: Chris Spence On EL6, Puppet 3.7.4 I get this error: Error: Could not set 'file' on ensure: No such file or directory - /etc/puppetdb/conf.d/read_database.ini at 43:/platform/puppet/environment/production/modules/puppetdb/manifests/server/read_database_ini.pp when building a fresh machine Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-3884) Investigate AIO puppet agent upgrade
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3884 Investigate AIO puppet agent upgrade Test Rail triage and risk analysis not necessary. Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1309) Finish happy path Clojure end-to-end tests
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1309 Finish happy path Clojure end-to-end tests Test Rail triage and risk analysis not necessary. Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1347) PR (171): add FreeBSD support - mmoll
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1347 PR (171): add FreeBSD support - mmoll Test Rail triage and risk analysis not necessary. Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1470) PR (1374): r(maint) make facts response streaming - wkalt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1470 PR (1374): r(maint) make facts response streaming - wkalt Issue Type: Task Assignee: Unassigned Created: 2015/05/01 2:28 PM Labels: github Priority: Normal Reporter: gepetto-bot r(maint) make facts response streaming Author: Wyatt Alt Company: Github ID: wkalt Pull Request 1374 Discussion Pull Request 1374 File Diff Pull Request Description Previously we were mistakenly realizing the value of our facts response by validating it as a collection. This changes the validation so that it is applied on a per-element basis and doesn't disrupt the laziness of the response.
Jira (PUP-4347) Add test(s) for the File resource ignore attribute
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4347 Add test(s) for the File resource ignore attribute Change By: Kurt Wall Assignee: QA KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1958) Puppet Ticketing System Should Support Puppet Markup
Title: Message Title Kurt Wall updated an issue Puppet / PUP-1958 Puppet Ticketing System Should Support Puppet Markup Test Rail triage and risk analysis not necessary. Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1451) Placeholder for PE 3.8 testing help
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1451 Placeholder for PE 3.8 testing help Test Rail triage and risk analysis not necessary. Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1437) PR (1355): (maint) Explain acceptance testing off the VPN - rbrw
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1437 PR (1355): (maint) Explain acceptance testing off the VPN - rbrw Test Rail triage and risk analysis not necessary. Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1449) PR (1362): (maint) Remove lucid from build targets - melissa
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1449 PR (1362): (maint) Remove lucid from build targets - melissa Test Rail triage and risk analysis not necessary. Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1386) PR (1337): (maint) Support iterative acceptance test development - mullr
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1386 PR (1337): (maint) Support iterative acceptance test development - mullr Test Rail triage and risk analysis not necessary. Change By: Kurt Wall QA Contact: KurtWall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4511) Type Array is not assignable to itself
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-4511 Type Array is not assignable to itself Issue Type: Bug Assignee: Thomas Hallgren Created: 2015/05/01 5:33 AM Fix Versions: PUP 3.8.1, PUP 4.1.0 Priority: Normal Reporter: Thomas Hallgren The TypeCalculator.assignable? method does not consider the type Array to be assignable to itself. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4511) Types Array[?] and Hash[?,?] are not assignable to themselfes
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-4511
Types Array[?] and Hash[?,?] are not assignable to themselfes
Change By:
Thomas Hallgren
The{{TypeCalculator.assignable?}}methoddoesnotconsiderthetype{{Array [?] }}tobeassignabletoitself. Samethingfor{{Hash[?,?]}}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4511) Types Array[?] and Hash[?,?] are not assignable to themselfes
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-4511 Types Array[?] and Hash[?,?] are not assignable to themselfes Change By: Thomas Hallgren Summary: Type Types Array is [?]andHash[?,?]are notassignableto itself themselfes Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4511) Types Array[?], Hash[?,?], and Optional[?] are not assignable to themselfes
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-4511
Types Array[?], Hash[?,?], and Optional[?] are not assignable to themselfes
Change By:
Thomas Hallgren
The{{TypeCalculator.assignable?}}methoddoesnotconsiderthe type types {{Array[?]}} tobeassignabletoitself.Samethingfor , {{Hash[?,?]}} ,and{{Optional[?]}}tobeassignabletothemselves.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4511) Types Array[?], Hash[?,?], and Optional[?] are not assignable to themselfes
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-4511 Types Array[?], Hash[?,?], and Optional[?] are not assignable to themselfes Change By: Thomas Hallgren Summary: TypesArray[?] and , Hash[?,?] ,andOptional[?] arenotassignabletothemselfes Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1460) PR (1369): (maint) Upgrade clj-time ring-core and compojure deps - ajroetker
Title: Message Title gepetto-bot commented on PDB-1460 Re: PR (1369): (maint) Upgrade clj-time ring-core and compojure deps - ajroetker rbrw commented: LGTM Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1460) PR (1369): (maint) Upgrade clj-time ring-core and compojure deps - ajroetker
Title: Message Title gepetto-bot commented on PDB-1460 Re: PR (1369): (maint) Upgrade clj-time ring-core and compojure deps - ajroetker Pull request (maint) Upgrade clj-time ring-core and compojure deps has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4483) Add NotUndef type to the set of Puppet types
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-4483 Add NotUndef type to the set of Puppet types Change By: Thomas Hallgren Fix Version/s: PUP4.1.0 Fix Version/s: PUP3.8.1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
