Jira (PUP-8439) Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit

[Thomas Hallgren (JIRA)]

Thomas Hallgren created an issue

Puppet / PUP-8439 Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit Issue Type: Bug Assignee: Unassigned Created: 2018/02/08 12:57 AM Environment: The data types Float, Integer, Timespan, and Timestamp in the Puppet type system can be specified with a lower and upper limit using the syntax T[min, max]. When using just one argument, T[x] the  Float and Integer will interpret this as T[x, <no limit>] whereas Timespan and Timestamp interprets it as T[x,x]. The latter interpretation is incorrect. Timespan and Timestamp must be changed to use the same semantics as Float and Integer. Priority: Normal Reporter: Thomas Hallgren Puppet Version: Puppet Server Version: OS Name/Version: Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful. Add Comment

This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)

[Thomas Hallgren (JIRA)]

Thomas Hallgren updated an issue

Puppet / PUP-8439 Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit

Change By: Thomas Hallgren Method Found: Manual Test Needs Assessment

Add Comment

[Thomas Hallgren (JIRA)]

Thomas Hallgren updated an issue

Puppet / PUP-8439 Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit

Change By: Thomas Hallgren Method Found: Needs Assessment Manual Test

Add Comment

[Thomas Hallgren (JIRA)]

Thomas Hallgren assigned an issue to Thomas Hallgren

Puppet / PUP-8439 Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit

Change By: Thomas Hallgren Assignee: Thomas Hallgren Environment: The data types {{Float}}, {{Integer}}, {{Timespan}}, and {{Timestamp}} in the Puppet type system can be specified with a lower and upper limit using the syntax {{T[min, max]}}. When using just one argument, {{T[x]}} the  {{Float}} and {{Integer}} will interpret this as {{T[x, <no limit>]}} whereas {{Timespan}} and {{Timestamp}} interprets it as {{T[x,x]}}. The latter interpretation is incorrect. {{Timespan}} and {{Timestamp}} must be changed to use the same semantics as {{Float}} and {{Integer}}. Story Points: 1 Team: Platform Core Sprint: Bolt Kanban

Method Found: Needs Assessment Manual Test

Add Comment

[Thomas Hallgren (JIRA)]

Thomas Hallgren assigned an issue to Henrik Lindberg

Puppet / PUP-8439 Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit

Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg

Add Comment

[Henrik Lindberg (JIRA)]

Henrik Lindberg assigned an issue to Unassigned

Puppet / PUP-8439 Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit

Change By: Henrik Lindberg Assignee: Henrik Lindberg

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper commented on PUP-8439

Re: Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit Merged to master in https://github.com/puppetlabs/puppet/commit/53ecfaf1bc7cb7576fed14db0567441c4df385cb

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-8439

Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit

Change By: Josh Cooper Fix Version/s: PUP 5.4.z

Add Comment

[Kenn Hussey (JIRA)]

Kenn Hussey commented on PUP-8439

Re: Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit Thomas Hallgren please add release notes for this issue, if needed. Thanks!

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Henrik Lindberg (JIRA)]

Henrik Lindberg updated an issue

Puppet / PUP-8439

Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit

Change By: Henrik Lindberg Release Notes Summary: The data types Timespan and Timestamp incorrectly set the upper bounds to the same as lower bounds when created with a single parameter - that is T[x] was taken as T[x,x] instead of T[x, <no-limit>]. This is now corrected. Release Notes: Bug Fix

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-8439 Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit

Change By: Josh Cooper Sub-team: Language

Add Comment

[John Duarte (JIRA)]

John Duarte updated an issue

Puppet / PUP-8439 Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit

Change By: John Duarte QA Risk Assessment: Needs Assessment No Action

Add Comment