cruelsmith

That feature was introduced in 2.5.0 (2016 #2040) working and broke somewhere at 2.10.x (2019) ? At least when i see #7398 . Would be at least nice for any...

@slalomsk8er What version did you run that your stupidified timeperiod worked? Is ask because with `2.13.7` even this does not work for me. I created #9781 with all checks it...

@slalomsk8er Thank you. That proves my test `weekday` from #9781.

Duplicate of #452 See https://github.com/voxpupuli/puppet-nodejs/issues/452#issuecomment-1620245201 for a workaround

The `matrix_from_metadata_v2` is part of the puppet_litmus gem. With https://github.com/puppetlabs/puppet_litmus/pull/523/files Debian-12 has been added so this one should now work? Needs a rerun of the workflow to verify.

Oh the version bump for the `puppet_lintmus` gem that adds it is still open puppetlabs/puppet_litmus#524

Hi @Al2Klimov, i saw that you already worked deep in the code of the timeperiod feature of the linked issues and wanted to ask if maybe can have a look...

That issue will also be logged in debug mode: > [2023-06-01 17:26:45 +0200] debug/LegacyTimePeriod: ParseTimeRange: 'day 1' => 1685570400 -> 1685656800, stride: 1 [2023-06-01 17:26:45 +0200] debug/LegacyTimePeriod: ParseTimeRange: 'day 1'...

> In short, you think that the segments are mis-generated even before any merge across time periods (https://github.com/Icinga/icinga2/pull/7855) happens? Yes, that is what my `To Reproduce` tests showed. While TimePeriod...

With the silent drop (without notice in release notes / changelog) of multiple features with puppetlabs/pdk-templates#510 it is more important than ever when maintaining many projects. All pdk projects that...