lib/client.rb - use Tempfile.create instead of Tempfile.new for request bodies #3296
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently,
Tempfile.new
is used inClient
when a request contains content (a body) that is either very large or indeterminate (chunked).Tempfile.new
creates a finalizer that removes theTempfile
, so its removal is dependent on GC.Recently, Windows head builds started logging the following in CI, a log is here. Note that Ruby head (3.3) has had many changes re GC, and one might call it more agressive...
I doubt many people are using Puma on Windows, but Windows CI may show things that indicate issues. On Windows, one cannot delete a file if it is open, unlike '*nix' platforms.
Also, in general, I think we'd prefer that Puma does its own cleanup, and not depend on GC to do so, at least with system resources like IO (files, pipes, sockets, etc).
So, use
Tempfile.create
and remove the file when Puma is finished with it.Your checklist for this pull request
[ci skip]
to the title of the PR.#issue
" to the PR description or my commit messages.