[ruby] Update bootsnap 1.14.0 → 1.18.4 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ bootsnap (1.14.0 → 1.18.4) · Repo · Changelog

Release Notes

1.18.4 (from changelog)

• Allow using bootsnap without bundler. See #488.
• Fix startup failure if the cache directory points to a broken symlink.

1.18.3 (from changelog)

• Fix the cache corruption issue in the revalidation feature. See #474. The cache revalidation feature remains opt-in for now, until it is more battle tested.

1.18.2 (from changelog)

• Disable stale cache entries revalidation by default as it seems to cause cache corruption issues. See #471 and #474. Will be re-enabled in a future version once the root cause is identified.
• Fix a potential compilation issue on some systems. See #470.

1.18.1 (from changelog)

• Handle EPERM errors when opening files with O_NOATIME.

1.18.0 (from changelog)

• Bootsnap.instrumentation now receive :hit events.
• Add Bootsnap.log_stats! to print hit rate statistics on process exit. Can also be enabled with BOOTSNAP_STATS=1.
• Revalidate stale cache entries by digesting the source content. This should significantly improve performance in environments where mtime isn't preserved (e.g. CI systems doing a git clone, etc). See #468.
• Open source files and cache entries with O_NOATIME when available to reduce disk accesses. See #469.
• bootsnap precompile --gemfile now look for .rb files in the whole gem and not just the lib/ directory. See #466.

1.17.1 (from changelog)

• Fix a compatibility issue with the prism library that ships with Ruby 3.3. See #463.
• Improved the Kernel#require decorator to not cause a method redefinition warning. See #461.

1.17.0 (from changelog)

• Ensure $LOAD_PATH.dup is Ractor shareable to fix an conflict with did_you_mean.
• Allow to ignore directories using absolute paths.
• Support YAML and JSON CompileCache on TruffleRuby.
• Support LoadPathCache on TruffleRuby.

1.16.0 (from changelog)

• Use RbConfig::CONFIG["rubylibdir"] instead of RbConfig::CONFIG["libdir"] to check for stdlib files. See #431.
• Fix the cached version of YAML.load_file being slightly more permissive than the default Psych one. See #434. Date and Time values are now properly rejected, as well as aliases. If this causes a regression in your application, it is recommended to load trusted YAML files with YAML.unsafe_load_file.

1.15.0 (from changelog)

• Add a readonly mode, for environments in which the updated cache wouldn't be persisted. See #428 and #423.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ msgpack (indirect, 1.6.0 → 1.7.2) · Repo · Changelog

Release Notes

1.7.2 (from changelog)

* Fix a potential GC bug when packing data using recursive extensions and buffers containing over 512KkiB of data (See #341).
* Fix a regression where feeding an empty string to an Unpacker would be considered like the end of the buffer.

1.7.1 (from changelog)

* Fix JRuby 9.4 compatibility.
* Fix compilation on older compilers (gcc 4.x).
* Fix an infinite recursion issue when registering a Symbol type with a `nil` packer.

1.7.0 (from changelog)

* Fix a possible double-free issue when GC triggers inside `_msgpack_rmem_alloc2`.
* `Unpacker#feed` now always directly read in provided strings instead of copying content in its buffer.
* `Unpacker#feed` is now an alias of `Unpacker#feed_reference`.
* Implement `Factory::Pool#unpacker` and `Factory::Pool#packer` to allow for more precise serialization.
* Require Ruby 2.5+.

1.6.1 (from changelog)

* Undefine `#clone` and `#dup` on `MessagePack::Buffer`, `MessagePack::Packer` and `MessagePack::Unpacker`.
  These methods were never intended, and using them could cause leaks or crashes or worse.
* Fix a possible GC crash when GC trigger inside `MessagePack::Buffer.new` (#314).

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)