Skip to content

Remove legacy network HTTP APIs#390

Draft
silug wants to merge 4 commits intoOpenVoxProject:mainfrom
silug:remove-legacy-http-apis
Draft

Remove legacy network HTTP APIs#390
silug wants to merge 4 commits intoOpenVoxProject:mainfrom
silug:remove-legacy-http-apis

Conversation

@silug
Copy link
Copy Markdown
Contributor

@silug silug commented Apr 9, 2026

Short description

The deprecated Puppet::Network::HTTP::Connection class and associated legacy HTTP pool methods have been removed.

Closes #341

Checklist

I have:

  • read the CONTRIBUTING.md document
  • read and accepted the Developer Certificate of Origin document and added a Signed-off-by annotation to each of my commits
  • tested this code
  • included documentation (including possible behaviour changes)
  • documented the code
  • added or modified regression test(s)
  • added or modified unit test(s)

The deprecated Puppet::Network::HTTP::Connection class and associated
legacy HTTP pool methods have been removed.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Steven Pritchard <steven.pritchard@gmail.com>
@silug silug force-pushed the remove-legacy-http-apis branch from 8b7c52f to 8f76945 Compare April 9, 2026 20:19
silug and others added 3 commits April 13, 2026 09:12
`dir_containing` creates the input `.rb` files just before `genface.types` runs and creates the output `.pp` files. On Windows with Ruby 3.2, sub-second or 2-second filesystem timestamp granularity can make test2.rb's mtime appear >= test2.pp's mtime, causing `up_to_date?` to return false incorrectly.

The fix backdates both input `.rb` files by 10 seconds before the first `genface.types` run, so the generated `.pp` files will always have unambiguously newer mtimes regardless of filesystem timestamp granularity. The `sleep(1)` before `touch`ing test1.rb is still needed to ensure test1.rb's new mtime is clearly newer than test1.pp's mtime.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Steven Pritchard <steven.pritchard@gmail.com>
Replace File.utime-based workaround with a sleep(2) before the first
genface.types call. File.utime with an explicit Time argument has a
DST offset bug on Windows Ruby 3.2 that can shift the stored mtime by
±1 hour, making the input files appear to be in the future and causing
spurious regeneration. Sleeping 2 seconds instead ensures output files
have unambiguously newer mtimes than inputs on any filesystem,
including FAT with its 2-second timestamp granularity.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Steven Pritchard <steven.pritchard@gmail.com>
Signed-off-by: Steven Pritchard <steven.pritchard@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Deprecation] Legacy Puppet::Network HTTP APIs

1 participant