text:
IPv6 setting problem

I tried running this using following command but got IPv6 disabled amongst other settings even though I had enable_ipv6 and enable_ipv6_forwarding set to true in the various files (including init.pp)
Any ideas?
puppet apply --verbose -e "include os_hardening" /root/puppet-os-hardening/manifests/init.pp
Info: Loading facts
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Notice: Compiled catalog for bfs-dl360g7-44-xm7.bfs.openwave.com in environment production in 0.58 seconds
Info: Applying configuration version '1453729939'
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ignore_bogus_error_responses]/File[/etc/sysctl.d/net.ipv4.icmp_ignore_bogus_error_responses.conf]/ensure: defined content as '{md5}380beb39ed6bd0769c5e936b28eb6488'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ignore_bogus_error_responses]/File[/etc/sysctl.d/net.ipv4.icmp_ignore_bogus_error_responses.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.icmp_ignore_bogus_error_responses]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ignore_bogus_error_responses]/File[/etc/sysctl.d/net.ipv4.icmp_ignore_bogus_error_responses.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.icmp_ignore_bogus_error_responses]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ignore_bogus_error_responses]/Exec[sysctl-net.ipv4.icmp_ignore_bogus_error_responses]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.accept_redirects]/File[/etc/sysctl.d/net.ipv4.conf.default.accept_redirects.conf]/ensure: defined content as '{md5}16ec2ab639b0abd0d03b64cea5c8290c'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.accept_redirects]/File[/etc/sysctl.d/net.ipv4.conf.default.accept_redirects.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.default.accept_redirects]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.accept_redirects]/File[/etc/sysctl.d/net.ipv4.conf.default.accept_redirects.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.default.accept_redirects]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.accept_redirects]/Exec[sysctl-net.ipv4.conf.default.accept_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[kernel.sysrq]/File[/etc/sysctl.d/kernel.sysrq.conf]/ensure: defined content as '{md5}1a903ed9a2508adec3f27ce94d996a65'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[kernel.sysrq]/File[/etc/sysctl.d/kernel.sysrq.conf]: Scheduling refresh of Exec[sysctl-kernel.sysrq]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[kernel.sysrq]/File[/etc/sysctl.d/kernel.sysrq.conf]: Scheduling refresh of Exec[update-sysctl.conf-kernel.sysrq]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_pinfo]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_ra_pinfo.conf]/ensure: defined content as '{md5}f90c62943f9f5df8b047b180cd86af06'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_pinfo]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_ra_pinfo.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.default.accept_ra_pinfo]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_pinfo]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_ra_pinfo.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.default.accept_ra_pinfo]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_pinfo]/Exec[sysctl-net.ipv6.conf.default.accept_ra_pinfo]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_pinfo]/Exec[update-sysctl.conf-net.ipv6.conf.default.accept_ra_pinfo]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[kernel.sysrq]/Exec[update-sysctl.conf-kernel.sysrq]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.rp_filter]/File[/etc/sysctl.d/net.ipv4.conf.all.rp_filter.conf]/ensure: defined content as '{md5}7f41e4d8ddc8cbba00dab408cb71c857'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.rp_filter]/File[/etc/sysctl.d/net.ipv4.conf.all.rp_filter.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.all.rp_filter]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.rp_filter]/File[/etc/sysctl.d/net.ipv4.conf.all.rp_filter.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.all.rp_filter]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.arp_ignore]/File[/etc/sysctl.d/net.ipv4.conf.all.arp_ignore.conf]/ensure: defined content as '{md5}ecd0cc79078347de778392678ea93c16'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.arp_ignore]/File[/etc/sysctl.d/net.ipv4.conf.all.arp_ignore.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.all.arp_ignore]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.arp_ignore]/File[/etc/sysctl.d/net.ipv4.conf.all.arp_ignore.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.all.arp_ignore]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.arp_ignore]/Exec[sysctl-net.ipv4.conf.all.arp_ignore]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_rfc1337]/File[/etc/sysctl.d/net.ipv4.tcp_rfc1337.conf]/ensure: defined content as '{md5}a853f01d533e7ba66f7ccf1372f81e92'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_rfc1337]/File[/etc/sysctl.d/net.ipv4.tcp_rfc1337.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.tcp_rfc1337]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_rfc1337]/File[/etc/sysctl.d/net.ipv4.tcp_rfc1337.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.tcp_rfc1337]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ratelimit]/File[/etc/sysctl.d/net.ipv4.icmp_ratelimit.conf]/ensure: defined content as '{md5}4185d9fda8041d81d77e19a857055193'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ratelimit]/File[/etc/sysctl.d/net.ipv4.icmp_ratelimit.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.icmp_ratelimit]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ratelimit]/File[/etc/sysctl.d/net.ipv4.icmp_ratelimit.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.icmp_ratelimit]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ratelimit]/Exec[update-sysctl.conf-net.ipv4.icmp_ratelimit]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_source_route]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_source_route.conf]/ensure: defined content as '{md5}fda3ea0fb306b79d5a67be8cead9c627'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_source_route]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_source_route.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.default.accept_source_route]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_source_route]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_source_route.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.default.accept_source_route]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_source_route]/Exec[sysctl-net.ipv6.conf.default.accept_source_route]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.secure_redirects]/File[/etc/sysctl.d/net.ipv4.conf.default.secure_redirects.conf]/ensure: defined content as '{md5}7e4b2efc1507dcb5838f5d12764295df'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.secure_redirects]/File[/etc/sysctl.d/net.ipv4.conf.default.secure_redirects.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.default.secure_redirects]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.secure_redirects]/File[/etc/sysctl.d/net.ipv4.conf.default.secure_redirects.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.default.secure_redirects]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.secure_redirects]/Exec[update-sysctl.conf-net.ipv4.conf.default.secure_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_rtr_pref]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_ra_rtr_pref.conf]/ensure: defined content as '{md5}570ee97412dc5b5d14e03683ed93de5b'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_rtr_pref]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_ra_rtr_pref.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.default.accept_ra_rtr_pref]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_rtr_pref]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_ra_rtr_pref.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.default.accept_ra_rtr_pref]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_rtr_pref]/Exec[update-sysctl.conf-net.ipv6.conf.default.accept_ra_rtr_pref]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_rtr_pref]/Exec[sysctl-net.ipv6.conf.default.accept_ra_rtr_pref]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.ip_forward]/File[/etc/sysctl.d/net.ipv4.ip_forward.conf]/ensure: defined content as '{md5}871a8782d97b3e80a2324ed591f6efbb'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.ip_forward]/File[/etc/sysctl.d/net.ipv4.ip_forward.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.ip_forward]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.ip_forward]/File[/etc/sysctl.d/net.ipv4.ip_forward.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.ip_forward]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.ip_forward]/Exec[update-sysctl.conf-net.ipv4.ip_forward]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.ip_forward]/Exec[sysctl-net.ipv4.ip_forward]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.secure_redirects]/Exec[sysctl-net.ipv4.conf.default.secure_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.disable_ipv6]/File[/etc/sysctl.d/net.ipv6.conf.all.disable_ipv6.conf]/ensure: defined content as '{md5}f761f671ddbae29bccd5e9d92f106e37'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.disable_ipv6]/File[/etc/sysctl.d/net.ipv6.conf.all.disable_ipv6.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.all.disable_ipv6]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.disable_ipv6]/File[/etc/sysctl.d/net.ipv6.conf.all.disable_ipv6.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.all.disable_ipv6]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.disable_ipv6]/Exec[update-sysctl.conf-net.ipv6.conf.all.disable_ipv6]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.disable_ipv6]/Exec[sysctl-net.ipv6.conf.all.disable_ipv6]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.send_redirects]/File[/etc/sysctl.d/net.ipv4.conf.all.send_redirects.conf]/ensure: defined content as '{md5}b13c09b98a8da943e92a750e819830da'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.send_redirects]/File[/etc/sysctl.d/net.ipv4.conf.all.send_redirects.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.all.send_redirects]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.send_redirects]/File[/etc/sysctl.d/net.ipv4.conf.all.send_redirects.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.all.send_redirects]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.send_redirects]/Exec[update-sysctl.conf-net.ipv4.conf.all.send_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.send_redirects]/Exec[sysctl-net.ipv4.conf.all.send_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_defrtr]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_ra_defrtr.conf]/ensure: defined content as '{md5}09e73c1eb03e63898359aeec6c072ff7'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_defrtr]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_ra_defrtr.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.default.accept_ra_defrtr]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_defrtr]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_ra_defrtr.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.default.accept_ra_defrtr]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_defrtr]/Exec[update-sysctl.conf-net.ipv6.conf.default.accept_ra_defrtr]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_ra_defrtr]/Exec[sysctl-net.ipv6.conf.default.accept_ra_defrtr]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.arp_ignore]/Exec[update-sysctl.conf-net.ipv4.conf.all.arp_ignore]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.shared_media]/File[/etc/sysctl.d/net.ipv4.conf.default.shared_media.conf]/ensure: defined content as '{md5}098c029398ed4b26890f4c4925635930'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.shared_media]/File[/etc/sysctl.d/net.ipv4.conf.default.shared_media.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.default.shared_media]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.shared_media]/File[/etc/sysctl.d/net.ipv4.conf.default.shared_media.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.default.shared_media]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.shared_media]/Exec[update-sysctl.conf-net.ipv4.conf.default.shared_media]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.shared_media]/Exec[sysctl-net.ipv4.conf.default.shared_media]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.accept_redirects]/File[/etc/sysctl.d/net.ipv4.conf.all.accept_redirects.conf]/ensure: defined content as '{md5}604caf8e8371cf0e27ca7bd0db4af6bb'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.accept_redirects]/File[/etc/sysctl.d/net.ipv4.conf.all.accept_redirects.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.all.accept_redirects]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.accept_redirects]/File[/etc/sysctl.d/net.ipv4.conf.all.accept_redirects.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.all.accept_redirects]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.accept_redirects]/Exec[update-sysctl.conf-net.ipv4.conf.all.accept_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.accept_source_route]/File[/etc/sysctl.d/net.ipv4.conf.all.accept_source_route.conf]/ensure: defined content as '{md5}70b61e1f916bfc9d42d442a4ded85c98'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.accept_source_route]/File[/etc/sysctl.d/net.ipv4.conf.all.accept_source_route.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.all.accept_source_route]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.accept_source_route]/File[/etc/sysctl.d/net.ipv4.conf.all.accept_source_route.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.all.accept_source_route]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.accept_source_route]/Exec[update-sysctl.conf-net.ipv4.conf.all.accept_source_route]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.accept_source_route]/Exec[sysctl-net.ipv4.conf.all.accept_source_route]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.send_redirects]/File[/etc/sysctl.d/net.ipv4.conf.default.send_redirects.conf]/ensure: defined content as '{md5}e5694a229563dcd97cdd72c6c9866a9f'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.send_redirects]/File[/etc/sysctl.d/net.ipv4.conf.default.send_redirects.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.default.send_redirects]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.send_redirects]/File[/etc/sysctl.d/net.ipv4.conf.default.send_redirects.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.default.send_redirects]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.send_redirects]/Exec[update-sysctl.conf-net.ipv4.conf.default.send_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ignore_bogus_error_responses]/Exec[update-sysctl.conf-net.ipv4.icmp_ignore_bogus_error_responses]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.max_addresses]/File[/etc/sysctl.d/net.ipv6.conf.default.max_addresses.conf]/ensure: defined content as '{md5}f55b8c3ed4233ef76463c6b3bc5e1e48'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.max_addresses]/File[/etc/sysctl.d/net.ipv6.conf.default.max_addresses.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.default.max_addresses]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.max_addresses]/File[/etc/sysctl.d/net.ipv6.conf.default.max_addresses.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.default.max_addresses]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.max_addresses]/Exec[update-sysctl.conf-net.ipv6.conf.default.max_addresses]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.accept_redirects]/Exec[sysctl-net.ipv4.conf.all.accept_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_redirects]/File[/etc/sysctl.d/net.ipv6.conf.all.accept_redirects.conf]/ensure: defined content as '{md5}5c498215d1620e1f18a79f44dbfa1235'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_redirects]/File[/etc/sysctl.d/net.ipv6.conf.all.accept_redirects.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.all.accept_redirects]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_redirects]/File[/etc/sysctl.d/net.ipv6.conf.all.accept_redirects.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.all.accept_redirects]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_redirects]/Exec[update-sysctl.conf-net.ipv6.conf.all.accept_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_redirects]/Exec[sysctl-net.ipv6.conf.all.accept_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.accept_redirects]/Exec[update-sysctl.conf-net.ipv4.conf.default.accept_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_rfc1337]/Exec[update-sysctl.conf-net.ipv4.tcp_rfc1337]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ratelimit]/Exec[sysctl-net.ipv4.icmp_ratelimit]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.send_redirects]/Exec[sysctl-net.ipv4.conf.default.send_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_echo_ignore_broadcasts]/File[/etc/sysctl.d/net.ipv4.icmp_echo_ignore_broadcasts.conf]/ensure: defined content as '{md5}7195e26f16bdc860aac6a373fd9b731e'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_echo_ignore_broadcasts]/File[/etc/sysctl.d/net.ipv4.icmp_echo_ignore_broadcasts.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.icmp_echo_ignore_broadcasts]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_echo_ignore_broadcasts]/File[/etc/sysctl.d/net.ipv4.icmp_echo_ignore_broadcasts.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.icmp_echo_ignore_broadcasts]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_echo_ignore_broadcasts]/Exec[sysctl-net.ipv4.icmp_echo_ignore_broadcasts]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.rp_filter]/Exec[sysctl-net.ipv4.conf.all.rp_filter]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_redirects]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_redirects.conf]/ensure: defined content as '{md5}594504b28e500a511553f1976c50c659'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_redirects]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_redirects.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.default.accept_redirects]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_redirects]/File[/etc/sysctl.d/net.ipv6.conf.default.accept_redirects.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.default.accept_redirects]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_redirects]/Exec[update-sysctl.conf-net.ipv6.conf.default.accept_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[kernel.sysrq]/Exec[sysctl-kernel.sysrq]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.accept_source_route]/File[/etc/sysctl.d/net.ipv4.conf.default.accept_source_route.conf]/ensure: defined content as '{md5}9846b42222457a0814e55bf937dad0a2'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.accept_source_route]/File[/etc/sysctl.d/net.ipv4.conf.default.accept_source_route.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.default.accept_source_route]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.accept_source_route]/File[/etc/sysctl.d/net.ipv4.conf.default.accept_source_route.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.default.accept_source_route]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.accept_source_route]/Exec[update-sysctl.conf-net.ipv4.conf.default.accept_source_route]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.accept_source_route]/Exec[sysctl-net.ipv4.conf.default.accept_source_route]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_redirects]/Exec[sysctl-net.ipv6.conf.default.accept_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.router_solicitations]/File[/etc/sysctl.d/net.ipv6.conf.default.router_solicitations.conf]/ensure: defined content as '{md5}55500cb7011f3a41d03bbb1d0aad9549'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.router_solicitations]/File[/etc/sysctl.d/net.ipv6.conf.default.router_solicitations.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.default.router_solicitations]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.router_solicitations]/File[/etc/sysctl.d/net.ipv6.conf.default.router_solicitations.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.default.router_solicitations]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.router_solicitations]/Exec[update-sysctl.conf-net.ipv6.conf.default.router_solicitations]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_echo_ignore_broadcasts]/Exec[update-sysctl.conf-net.ipv4.icmp_echo_ignore_broadcasts]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.router_solicitations]/Exec[sysctl-net.ipv6.conf.default.router_solicitations]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_rfc1337]/Exec[sysctl-net.ipv4.tcp_rfc1337]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[kernel.randomize_va_space]/File[/etc/sysctl.d/kernel.randomize_va_space.conf]/ensure: defined content as '{md5}8d3abb75095ab04dcceeed67be19d23c'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[kernel.randomize_va_space]/File[/etc/sysctl.d/kernel.randomize_va_space.conf]: Scheduling refresh of Exec[sysctl-kernel.randomize_va_space]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[kernel.randomize_va_space]/File[/etc/sysctl.d/kernel.randomize_va_space.conf]: Scheduling refresh of Exec[update-sysctl.conf-kernel.randomize_va_space]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[kernel.randomize_va_space]/Exec[sysctl-kernel.randomize_va_space]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[kernel.randomize_va_space]/Exec[update-sysctl.conf-kernel.randomize_va_space]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.shared_media]/File[/etc/sysctl.d/net.ipv4.conf.all.shared_media.conf]/ensure: defined content as '{md5}c4027d962c6c465d2a9a7f58585ea44c'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.shared_media]/File[/etc/sysctl.d/net.ipv4.conf.all.shared_media.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.all.shared_media]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.shared_media]/File[/etc/sysctl.d/net.ipv4.conf.all.shared_media.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.all.shared_media]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.shared_media]/Exec[update-sysctl.conf-net.ipv4.conf.all.shared_media]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.shared_media]/Exec[sysctl-net.ipv4.conf.all.shared_media]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.dad_transmits]/File[/etc/sysctl.d/net.ipv6.conf.default.dad_transmits.conf]/ensure: defined content as '{md5}366f20546ba5b31094e1e43c42f04f32'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.dad_transmits]/File[/etc/sysctl.d/net.ipv6.conf.default.dad_transmits.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.default.dad_transmits]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.dad_transmits]/File[/etc/sysctl.d/net.ipv6.conf.default.dad_transmits.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.default.dad_transmits]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.dad_transmits]/Exec[update-sysctl.conf-net.ipv6.conf.default.dad_transmits]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.dad_transmits]/Exec[sysctl-net.ipv6.conf.default.dad_transmits]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.rp_filter]/Exec[update-sysctl.conf-net.ipv4.conf.all.rp_filter]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_ra]/File[/etc/sysctl.d/net.ipv6.conf.all.accept_ra.conf]/ensure: defined content as '{md5}bafa79b072e7a4e659949f42b440a80d'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_ra]/File[/etc/sysctl.d/net.ipv6.conf.all.accept_ra.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.all.accept_ra]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_ra]/File[/etc/sysctl.d/net.ipv6.conf.all.accept_ra.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.all.accept_ra]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_ra]/Exec[sysctl-net.ipv6.conf.all.accept_ra]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_ra]/Exec[update-sysctl.conf-net.ipv6.conf.all.accept_ra]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.max_addresses]/Exec[sysctl-net.ipv6.conf.default.max_addresses]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.arp_announce]/File[/etc/sysctl.d/net.ipv4.conf.all.arp_announce.conf]/ensure: defined content as '{md5}7264d69769b84a28d2f9a529cdc2aaa1'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.arp_announce]/File[/etc/sysctl.d/net.ipv4.conf.all.arp_announce.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.all.arp_announce]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.arp_announce]/File[/etc/sysctl.d/net.ipv4.conf.all.arp_announce.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.all.arp_announce]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.arp_announce]/Exec[update-sysctl.conf-net.ipv4.conf.all.arp_announce]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.forwarding]/File[/etc/sysctl.d/net.ipv6.conf.all.forwarding.conf]/ensure: defined content as '{md5}78a627a2e6c70437e629ce36aedb22b1'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.forwarding]/File[/etc/sysctl.d/net.ipv6.conf.all.forwarding.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.all.forwarding]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.forwarding]/File[/etc/sysctl.d/net.ipv6.conf.all.forwarding.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.all.forwarding]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.forwarding]/Exec[update-sysctl.conf-net.ipv6.conf.all.forwarding]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.forwarding]/Exec[sysctl-net.ipv6.conf.all.forwarding]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ratemask]/File[/etc/sysctl.d/net.ipv4.icmp_ratemask.conf]/ensure: defined content as '{md5}782cfd85594bdfd1ea13bcb56035c3be'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ratemask]/File[/etc/sysctl.d/net.ipv4.icmp_ratemask.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.icmp_ratemask]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ratemask]/File[/etc/sysctl.d/net.ipv4.icmp_ratemask.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.icmp_ratemask]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ratemask]/Exec[sysctl-net.ipv4.icmp_ratemask]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.icmp_ratemask]/Exec[update-sysctl.conf-net.ipv4.icmp_ratemask]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.secure_redirects]/File[/etc/sysctl.d/net.ipv4.conf.all.secure_redirects.conf]/ensure: defined content as '{md5}e950dcb71eebfff44ae67b94811ad393'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.secure_redirects]/File[/etc/sysctl.d/net.ipv4.conf.all.secure_redirects.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.all.secure_redirects]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.secure_redirects]/File[/etc/sysctl.d/net.ipv4.conf.all.secure_redirects.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.all.secure_redirects]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.secure_redirects]/Exec[update-sysctl.conf-net.ipv4.conf.all.secure_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.secure_redirects]/Exec[sysctl-net.ipv4.conf.all.secure_redirects]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[fs.suid_dumpable]/File[/etc/sysctl.d/fs.suid_dumpable.conf]/ensure: defined content as '{md5}f62cd4ea250228661e2252a43d77d52e'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[fs.suid_dumpable]/File[/etc/sysctl.d/fs.suid_dumpable.conf]: Scheduling refresh of Exec[sysctl-fs.suid_dumpable]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[fs.suid_dumpable]/File[/etc/sysctl.d/fs.suid_dumpable.conf]: Scheduling refresh of Exec[update-sysctl.conf-fs.suid_dumpable]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[fs.suid_dumpable]/Exec[sysctl-fs.suid_dumpable]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[fs.suid_dumpable]/Exec[update-sysctl.conf-fs.suid_dumpable]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.all.arp_announce]/Exec[sysctl-net.ipv4.conf.all.arp_announce]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.accept_source_route]/Exec[update-sysctl.conf-net.ipv6.conf.default.accept_source_route]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.autoconf]/File[/etc/sysctl.d/net.ipv6.conf.default.autoconf.conf]/ensure: defined content as '{md5}0db957d6a2151f6a660bd88ed74f48ed'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.autoconf]/File[/etc/sysctl.d/net.ipv6.conf.default.autoconf.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.default.autoconf]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.autoconf]/File[/etc/sysctl.d/net.ipv6.conf.default.autoconf.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.default.autoconf]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.autoconf]/Exec[update-sysctl.conf-net.ipv6.conf.default.autoconf]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.default.autoconf]/Exec[sysctl-net.ipv6.conf.default.autoconf]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_timestamps]/File[/etc/sysctl.d/net.ipv4.tcp_timestamps.conf]/ensure: defined content as '{md5}92c3932a409c8f490161c20b55baef94'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_timestamps]/File[/etc/sysctl.d/net.ipv4.tcp_timestamps.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.tcp_timestamps]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_timestamps]/File[/etc/sysctl.d/net.ipv4.tcp_timestamps.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.tcp_timestamps]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_timestamps]/Exec[update-sysctl.conf-net.ipv4.tcp_timestamps]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_timestamps]/Exec[sysctl-net.ipv4.tcp_timestamps]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.rp_filter]/File[/etc/sysctl.d/net.ipv4.conf.default.rp_filter.conf]/ensure: defined content as '{md5}fa638b987ed743c795d765a70f641731'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.rp_filter]/File[/etc/sysctl.d/net.ipv4.conf.default.rp_filter.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.conf.default.rp_filter]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.rp_filter]/File[/etc/sysctl.d/net.ipv4.conf.default.rp_filter.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.conf.default.rp_filter]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.rp_filter]/Exec[sysctl-net.ipv4.conf.default.rp_filter]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.conf.default.rp_filter]/Exec[update-sysctl.conf-net.ipv4.conf.default.rp_filter]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_syncookies]/File[/etc/sysctl.d/net.ipv4.tcp_syncookies.conf]/ensure: defined content as '{md5}6ad40ed45dd9aef772cabde25d74cfc0'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_syncookies]/File[/etc/sysctl.d/net.ipv4.tcp_syncookies.conf]: Scheduling refresh of Exec[sysctl-net.ipv4.tcp_syncookies]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_syncookies]/File[/etc/sysctl.d/net.ipv4.tcp_syncookies.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv4.tcp_syncookies]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_syncookies]/Exec[sysctl-net.ipv4.tcp_syncookies]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv4.tcp_syncookies]/Exec[update-sysctl.conf-net.ipv4.tcp_syncookies]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_source_route]/File[/etc/sysctl.d/net.ipv6.conf.all.accept_source_route.conf]/ensure: defined content as '{md5}80a4851fb5e81f8ff50f20da4340f239'
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_source_route]/File[/etc/sysctl.d/net.ipv6.conf.all.accept_source_route.conf]: Scheduling refresh of Exec[sysctl-net.ipv6.conf.all.accept_source_route]
Info: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_source_route]/File[/etc/sysctl.d/net.ipv6.conf.all.accept_source_route.conf]: Scheduling refresh of Exec[update-sysctl.conf-net.ipv6.conf.all.accept_source_route]
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_source_route]/Exec[update-sysctl.conf-net.ipv6.conf.all.accept_source_route]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Os_hardening::Sysctl/Sysctl[net.ipv6.conf.all.accept_source_route]/Exec[sysctl-net.ipv6.conf.all.accept_source_route]: Triggered 'refresh' from 1 events
Notice: Finished catalog run in 20.34 seconds

@nmcconom please try to use it like this instead of changing code:
puppet apply -e "class { 'os_hardening': enable_ipv6 => true }"

Hi Artem - I tried the following command based on your example and it seemed to work fine:
puppet apply -e "class { 'os_hardening': enable_ipv6 => true, enable_ipv4_forwarding => true, enable_ipv6_forwarding => true, enable_core_dump => true}"
Thanks for the help on this.

authors: artem-sidorenko nmcconom

repo: hardening-io/puppet-os-hardening


text:
Create ip_obsc.py

Obsc version 🛫

Merge

source: gharchive/pull-request

repo: harkerbyte/nxtgen-ip

license: MIT

license_type: permissive

license_source: github-api


text:
[DOC-3632]: Add warning for expressions that may not resolve

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[x] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[x] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

authors: bot-gitexp-user puthrayaharness

repo: harness/developer-hub


text:
Updated CI related SLIs

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Updated CI SLIs


text:
added a note to the CG and NG docs about Basic Authentication - CDS-48446

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-641

authors: bot-gitexp-user roshnisarangadharan


text:
Detail about Cosign key pair generation

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6643abc53eb3581dc8be2d64--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://664506f4d2e34369c7339917--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://664b3f8fda79e8b2d3b95ef8--harness-developer.netlify.app

authors: bot-gitexp-user tejakummarikuntla


text:
Microverse Desktop Portfolio Version

This is a portfolio desktop version and the mobile version made using HTML  and CSS.
The core concepts of HTML, CSS, and GitHub were implemented. Using HTML, I was able to create a dynamic and responsive webpage that incorporates text, images, and hyperlinks. With CSS, I was able to style and customize the layout and design of the page, creating a unique and visually appealing user experience. In addition, the project has been managed and stored using Github, which provides a powerful and reliable version control system.

As per the feedback, I wrote the description of my PR. The mobile menu and logo are now displayed.Thanks for the feedback


text:
[Fixed] Solved Issue #175 , #177 , #197

Solved Issue #175 , #177 , #197

Mate, here's the location of all the elements and fixed the second last row and the image of barabar hills point

thanku man

authors: dellucifer harshvardhansb

repo: harshvardhansb/TourGuide


text:
2016/05/05/javascript-weak-type

弱类型只是一种信仰 - Harttle Land
http://harttle.land/2016/05/05/javascript-weak-type.html

函数默认值 是 ES 6 标准引入的
By Tech_Query (shiy2008@gmail.com) 2017-11-20T17:04:29Z

Promise 那个例子，JS 的优势和弱类型倒没太大关系，主要是 动态语言 + 基于原型的面向对象
By Tech_Query (shiy2008@gmail.com) 2017-11-20T17:06:35Z

所以 “动态语言” 是指什么？类型么
By Yang Jun (yangjvn@126.com) 2018-02-08T10:06:51Z

其实工程上弱类型有很大问题，比如这篇文章就在想方设法避免问题： http://harttle.land/2018/02...
By Yang Jun (yangjvn@126.com) 2018-02-08T10:08:19Z

source: gharchive/issue


text:
train_cnn.py

When I ran this file, an error arose:
ValueError: output of generator should be a tuple'(x, y, sample_weight)'. Found: None
Hope someone can help me.

Use tensorflow 1.5

@khawar08
Thanks. But my tensorflow version is just 1.5.0. However it doesn't work.

license: mit

license_source: bigquery


text:
delete buttons in Realtime Map Page

Right now buttons program 5 minutes from now. and in UTC.
But I think the purpose is to be  5 minutes from the time that is in the field.
And make "before 5 minutes" and "after 5 minutes"
Above-mentioned about 10 minutes buttons.

I think we can remove this button,
it is supposed to show the busses as of 5 minutes ago (from now).
for example, now it's 17:30 p.m. if I hit this button, it will show the traffic as it was at 17:25 p.m.

OK.
I vote to remove the buttons.

Alright :+1:
Let's also change the default time to five minutes ago

Hey, I can take this issue.
I just want to understand the task:

Remove the "5 min ago" & "10 min ago" buttons
change the default time to five minutes ago - what is the default now?

I tested it now locally, and the default time was 12:00. So - we want to make it 5 minutes ago?

@amabelleS thank you!
I believe the default timestamp is on a different date (1.5.2023).
So yes, you're right. By default, we want the map to show busses from 5 minutes ago

o.k. I'm on it:)

authors: NoamGaash amabelleS aviv1620

repo: hasadna/open-bus-map-search


text:
Set strip_index_format to None

The wgpu documentation says that strip_index_format 'Should be left None for non-strip.', which is the case as we're using wgpu::PrimitiveTopology::TriangleList. This fix isn't urgent by any means, but I do get a vulkan validation error because of it:
VALIDATION [VUID-VkPipelineInputAssemblyStateCreateInfo-topology-00428 (-1077750125)] : Validation Error: [ VUID-VkPipelineInputAssemblyStateCreateInfo-topology-00428 ] Object 0: handle = 0x560f78422700, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xbfc2d693 | vkCreateGraphicsPipelines() pCreateInfo[0]: topology is VK_PRIMITIVE_TOPOLOGY_TRIANGLE_LIST and primitiveRestartEnable is VK_TRUE. It is invalid. The Vulkan spec states: If topology is VK_PRIMITIVE_TOPOLOGY_POINT_LIST, VK_PRIMITIVE_TOPOLOGY_LINE_LIST, VK_PRIMITIVE_TOPOLOGY_TRIANGLE_LIST, VK_PRIMITIVE_TOPOLOGY_LINE_LIST_WITH_ADJACENCY, VK_PRIMITIVE_TOPOLOGY_TRIANGLE_LIST_WITH_ADJACENCY or VK_PRIMITIVE_TOPOLOGY_PATCH_LIST, primitiveRestartEnable must be VK_FALSE (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-VkPipelineInputAssemblyStateCreateInfo-topology-00428)

LGTM

authors: expenses hasenbanck


text:
Enable dependabot automatic updates

Problem
dependabot auto updates are not currently being used
Solution
Enable dependabot automatic updates
See Mirror Node dependabot.yaml for inspiration
Alternatives
No response

Dependabot is functional

repo: hashgraph/hedera-json-rpc-relay


text:
Adds Streak Calculation Algorithm

Tasks Accomplished:

[x] Implemented a Streak class to store and calculate all the streak information of the app with the help of the StreakDataType class
[x] Implemented & Added a StreakDataType TypeAdapter to store object of this class in Hive Database
[x] Added addActivityToStreak and deleteActivityFromStreak methods to update the streak information in case of addition and deletion of Activity in ActivityController & Streak classes
[x] Added following methods in GlobalSettingController for saving, retrieving, and displaying information related to Streak:

initStreakSettings : to initialize Streak settings
getInstalledDate : to get the app installed date
setInstalledDate: to set the app installed date
getAllStreaks: to get all Streaks of [Activity]s
setAllStreaks: to set all Streaks of [Activity]s
getLongestStreak: to get the Longest Streak
getLongestStreakCount: to get the Longest Streak Count
getCurrentStreak: to get the Current Streak
getCurrentStreakCount: to get the Current Streak Count
setCurrentStreak: to set the Current Streak

Fixes #162

@hashirshoaeb Please review it...

@hashirshoaeb Please review it...

@hashirshoaeb..Please review this PR...I've updated the algorithm for the addition and deletion of Activitys


text:
Fix server path for Windows

On Windows the extension ends up stuck while loading, this is a fix for the first error:

I think there are more issues though.

Now extensions finally loads but more errors emerge:

Wow thank you!
I want to resolve the error ahead, but I'm a bit busy for moving right now, so it might take some time before I can set up a Windows environment and verify it.

@MiguelRipoll23

Now extensions finally loads but more errors emerge:

How about running npm install at the root of the extension?

It works fine now using the latest release from the Visual Studio marketplace.
Thanks

repo: hashrock/kivi


text:
Improve sliding window min/max

#95 added sliding window min/max functions with big-O optimal amortized bounds. But a new minimum/maximum can force a pause proportional to the number of elements in the window. If we instead use a more careful sorted list representation, we should be able to cut the pauses to logarithmic time. A relatively simple approach would use a finger tree with a particular monoid described in the Hinze–Paterson paper on 2–3 finger trees, but we can probably tweak it a tad to do better without much difficulty. I don't know if there are more specialized structures that can do even better.

@kccqzy, you may be interested in this, since you came up with the current implementation.

One theoretical concern: with current processors, I estimate it will take on the order of a century to overflow the 64-bit counter. If computers get fast enough, that could get unacceptably short. If we want, we can check for overflow. When we detect it, we can subtract the oldest count from each one in the window (which we'll still assume has under 2^64 elements).

repo: haskell-streaming/streaming


text:
Create/find a script to do an initial ChangeLog

Even if it just slurps and formats all the PR's in the given date range, to be edited afterward for groupinp.

Perhaps use a tweak on https://coderwall.com/p/5cv5lg/generate-your-changelogs-with-git-log
cc @bubba

There are plenty of ready-made scripts like this or that to name a few. Most of them are written in JS or Ruby for some reason, but I don't think it's a problem if you're only going to run it locally.

authors: Anrock alanz

repo: haskell/haskell-ide-engine


text:
Please add Italian language to Master

Like recommended I have moved from develop to master branch, but the Italian language is not merged into master. Please do.

I will do it on Monday..

It will be included in 3.2.1 release. That will be released according our actual plan tomorrow.

Fixed in b975b16dac5f90cec241f3c768e31357b6e658a7

authors: Astagor havfo misi

repo: havfo/multiparty-meeting


text:
Add nuget package for known compatible Monaco editor files.

One of my biggest fears using this (and believe me, I want to), is not having a version of Monaco referenced that has been tested with the control.  I would recommend putting together a nuget package just for the Monaco bits (so it is distributed separately) and making it a version-specific dependency in your control's nuget package.  It also allows you to attribute Monaco correctly in Nuget by having it's own nuspec file.

@sharpninja we tightly couple the Monaco version to the version released in NuGet as we're embedding Monaco into a WebView and instantiating it.  All you need to use the control is pull down the NuGet, you don't have to mess to configure anything Monaco related at all.  It should just feel like any other UWP control, it's just using web-tech under-the-hood.
Since Monaco is distributed via npm, we pull it down through PowerShell to do the build, but we pin the version in that file that we've compiled against; so we'll only update the Monaco version if we've pulled it down and tested it with this wrapper.
That said, Monaco does make breaking changes all the time, so we'll still have breaking changes in the exposed C# versions of those APIs as well, but we'll note them as well.
Hope that helps, please let me know if you have any other questions.

authors: hawkerm sharpninja

repo: hawkerm/monaco-editor-uwp


text:
Refactoring support to control volume of player android

Issue

This pull request is inspired #33 by @sunjae1294.
This pull request will be merged into #33.

Changes

Add setStreamType() functionality for Android
prepare() no longer makes new mediaPlayer everytime it is called.

@sunjae1294 I refactor your code! Can you review this? This pull request will be merged into your pull request #33.

@sunjae1294 Please post a comment in the original repo saying that your code has been updated for some reasons after merging it.

@ghsdh3409 I think the prepare() no longer makes new mediaPlayer everytime it is called. part of the summary of this PR should be omitted! I forgot to erase it in my PR.

repo: hayanmind/react-native-sound


text:
[UI core library] Select isn't SSR compatible

It seems like there's an issue with Select on SSR:

This is caused by this method (document is not defined during server side render):
const getMenuContainer = (menuPortalTarget: 'body' | 'self' | HTMLElement | null): HTMLElement | null | undefined => {
  if (menuPortalTarget == 'body') {
    return document.body
  }
  if (menuPortalTarget == 'self') {
    return undefined
  }
  return menuPortalTarget
}

Currently this is a blocker for the new Cloud sign up.

@jozefhruska you can passing a custom menuPortalTarget as a workaround. I'll try to work on the fix tomorrow.

authors: aigoncharov jozefhruska

repo: hazelcast/frontend-shared


text:
Ringbuffer async API usage example

Implemented Ringbuffer async API usage example.

Windows test PASSed.

Linux test PASSed.

Windows test PASSed.

Linux test PASSed.

Linux test PASSed.

Windows test PASSed.

Linux test PASSed.

Linux test PASSed.

Windows test PASSed.

authors: devOpsHazelcast ihsandemir

repo: hazelcast/hazelcast-cpp-client


text:
Please add this new tracker.

Order on ebay with tracker:
https://www.orangeconnex.com/tracking?language=en&trackingnumber=EE10012419158450001040003E0N
Thanks

Hi @pedrobotelho, we'll try to add this tracker during the week.
Just a matter of curiosity did you have any issue like this https://github.com/hdnpt/geartrack-website/issues/44 since yesterday?

Hi @pedrobotelho, we'll try to add this tracker during the week.
Just a matter of curiosity did you have any issue like this https://github.com/hdnpt/geartrack-website/issues/44 since yesterday?

No Carlos, everything is working normally at my side!
I've 6 items 2 that are not working because they are from the above tracker and the other 4 are working as usually!
I did not notice any issue at all.
Thanks

No Carlos, everything is working normally at my side!
I've 6 items 2 that are not working because they are from the above tracker and the other 4 are working as usually!
I did not notice any issue at all.
Thanks

Cool, thanks for the feedback!

Cool, thanks for the feedback!

Hi, I'm experiencing the same issue as #44 since yesterday. Tried to delete all TrackIDs and start all over but the issue remains.

Hi, I'm experiencing the same issue as #44 since yesterday. Tried to delete all TrackIDs and start all over but the issue remains.

@jabss can you move your comment to the issue #44 and check if you can prove more data from you browser console / failed requests? (I can help you debug it if needed).

@jabss can you move your comment to the issue #44 and check if you can prove more data from you browser console / failed requests? (I can help you debug it if needed).

Just added this carrier :).

Just added this carrier :).

Hi Carlos!
Its working, it has the country on the stops! Great!
It looks great Thanks!
Just one question, maybe this is not the right place but its a simple one, on the trackers when it says Próximo ID: UJ827448XXX
the information will be display also right? we don't need to add a "new" item, right?
Thanks again

Hi Carlos!
Its working, it has the country on the stops! Great!
It looks great Thanks!
Just one question, maybe this is not the right place but its a simple one, on the trackers when it says Próximo ID: UJ827448XXX
the information will be display also right? we don't need to add a "new" item, right?
Thanks again

Hi Pedro,
Good to know it works, yeah its the next ID and it should be inserted manually at the moment. We hope to improve this process in the next version. I'll try to add a tooltip with some help when that field exists.

Hi Pedro,
Good to know it works, yeah its the next ID and it should be inserted manually at the moment. We hope to improve this process in the next version. I'll try to add a tooltip with some help when that field exists.

Ok thanks!
The ticket is closed and Working as expected!
Great job!
And if you need help you can count with me! Just ask!
Thanks again!

Ok thanks!
The ticket is closed and Working as expected!
Great job!
And if you need help you can count with me! Just ask!
Thanks again!

authors: carlosflorencio jabss pedrobotelho

repo: hdnpt/geartrack-website


text:
feat: LSDV-4583-1: Introduce valueList support

Hi @nicholasrq!
This PR was created in response to a PRs in upstream repo:

https://github.com/heartexlabs/label-studio-frontend/pull/1173

/git merge develop

authors: nicholasrq robot-ci-heartex

repo: heartexlabs/label-studio


text:
Create role philips_hue_configure

The role should:

[ ] Add bulbs by serial number
[ ] Create rooms and zones
[ ] Create Scenes
[ ] Update Scenes

Adding bulbs by serial number
Refs:

https://www.reddit.com/r/Hue/comments/sklsk3/add_light_with_serial_number_via_philips_hue_api/
https://morehue.com/add-light-with-serial-number-via-philips-hue-api/

https://github.com/ansible/ansible-examples/tree/master/phillips_hue


text:
Add a comment of how to clear the display to integration example

When I use integration example, it took some time to figure out how to clear display without own scene.
So I think it's good to share the code by adding this comment.
Feel free to correct me if my code is wrong or my english comment is grammertically bad.

The comment feels a bit out of place to me.
I think we can simply change the code to clear the screen right there, instead of hiding the side-effect inside Scene.

I just gave it a shot but I am not convinced by the result.
The example is meant to showcase how values from iced can be injected in a Scene. Moving the clearing logic defeats this purpose.
However, the comment adds noise to the integration code, which is the focus of the example.
In short, I am not sure there is a problem worth fixing here.

authors: hatoo hecrj

repo: hecrj/iced


text:
Tkinter error when trying to use Layoutviewer

Why when i do :
if not args.disablepreview:       gdspy.LayoutViewer(library=None, cells=[cell])
python return me a :
Traceback (most recent call last):   File ".\InductorGen.py", line 726, in <module>     gdspy.LayoutViewer(library=None, cells=[cell])   File "C:\Users\Maël\Anaconda3\lib\site-packages\gdspy\viewer.py", line 182, in __init__     self.grid(sticky='nsew')   File "C:\Users\Maël\Anaconda3\lib\tkinter\__init__.py", line 2226, in grid_configure     + self._options(cnf, kw)) _tkinter.TclError: cannot use geometry manager grid inside . which already has slaves managed by pack

@maelhos Are you trying to use LayoutViewer inside another Tk application? Can you show more of the code you're using?

Here it is InductorGen just do :
python .\InductorGen.py -l 200 -t 4 -lt 50 -p 5 -r 0.8 -v 4 -m 1 -d 45 -o tet -s 8
if you want to try ... and i think this is because of matplotlib ...

Ok it works perfectely fine now without matplotlib thank you so much...
But i'm sorry to say that i also need matplotlib, not now but for future graph ...
So only if you can and if you want ... can we implement other tk window compatibilitie ...

TBH I'm not sure what that would require... I'm not used to programming GUI apps. Maybe we can work together on trying to find a solution to your use case.

Ok ... Cool, that goes for me.I'm already trying to solve the problem

I've asked oubout the tcl error and understood it because of a cool helper on stackoverflow... Maybe it could help us ...

No changes after a year, so I'm closing this issue.

authors: heitzmann maelhos

repo: heitzmann/gdspy


text:
Toggle menu on mobile

It seems as though the toggle menu isn't working on the mobile view. The JavaScript isn't executing on the html files

Hello @helfi92
I hope you are doing well.
If this issue still active i would like to work on that and if possible you can assign me, I will be grateful for this.
Best regards,
Amisha

@amiii123malviya Thanks! All yours.


text:
Screen Blank when blur_edges set to True

Hi,
I seem to be having a problem when i have blur_edges set to True nothing shows just a black screen.
Any help would be great

Hi @PiSignage I think that might be due to a breaking change in the python image library (Pillow). Try upgrading picframe to the latest dev branch, something like (depending on what you did to originally set up your system pre or post Pi4 etc etc)
cd ~
source venv_picframe/bin/activate
pip install git+https://github.com/helgeerbe/picframe@dev --upgrade

I will try to pull the changes from the dev branch into main soon.
Paddy

I pulled the changes to main branch.  If you upgraded using the dev branch you might need to add a line to the viewer section of your configuration.yaml i.e.
  use_glx: False                          # default=False. Set to True on linux with xserver running. NB use_sdl2 might need to be False for this to work.
  use_sdl2: False                         # default=True. pysdl2 can use display without xserver, it should be installed as a dependency of pi3d

Thank you for getting back to me, I can confirm all is working now with your suggestions

authors: PiSignage paddywwoof

repo: helgeerbe/picframe


text:
Feature catalog improvement

We should add the following to feature catalog:

flavorExclusive - this feature only works in the flavor it is defined for (such as MP) - this should trigger a warning when trying to run it in a different flavor
mode - programmatic, kernel, CDI - which mode this feature supports, to make sure it runs in the correct environment
context - client, server - to make sure server side features are not added to client side programs

Consider changing the catalog to use files (such as META-INF/helidon/features.json) to collocate the feature description with the feature code, and load it at runtime. This would require moving this to a separate module as well (common-features) as it would depend on JSON library

This is already done, closing issue.

repo: helidon-io/helidon