ruby.git/lib/bundler/compact_index_client/updater.rb, branch v4.0.2

[rubygems/rubygems] Retry gracefully on blank partial response in compact index

2025-02-28T03:34:57+00:00

https://github.com/rubygems/rubygems/commit/fafb9ae090

[rubygems/rubygems] Remove MD5 ETag generation from compact index

2024-05-23T22:57:26+00:00

This was an offramp for generated etags to allow existing caches
to be served until people could upgrade. It has been about 6 months
since the transitional version was released, so we can remove this
transitional code now.

https://github.com/rubygems/rubygems/commit/4ec8cfe611

[rubygems/rubygems] Quote Etag in `If-None-Match` header of compact index request

2024-01-05T02:06:58+00:00

https://github.com/rubygems/rubygems/commit/d26bcd7551

[rubygems/rubygems] Use vendored net-http in Bundler

2023-12-13T03:16:55+00:00

https://github.com/rubygems/rubygems/commit/0d758e8926

Opaque Etags for compact index requests

2023-11-27T06:04:40+00:00

This changes the CompactIndexClient to store etags received from the
compact index in separate files rather than relying on the MD5 checksum
of the file as the etag.

Smoothes the upgrade from md5 etags to opaque by generating them when no
etag file exists. This should reduce the initial impact of changing the
caching behavior by reducing cache misses when the MD5 etag is the same.

Eventually, the MD5 behavior should be retired and the etag should be
considered completely opaque with no assumption that MD5 would match.

[rubygems/rubygems] Reduce allocations when parsing compact index

2023-10-08T04:17:15+00:00

This still allocates a ton (a string for each line, plus a bunch of
splits into arrays), but it helps a bit when Bundler has to go through
dependency resolution.

```
==> memprof.after.txt <==
Total allocated: 194.14 MB (2317172 objects)
Total retained:  60.81 MB (593164 objects)

==> memprof.before.txt <==
Total allocated: 211.97 MB (2404890 objects)
Total retained:  62.85 MB (640342 objects)
```

https://github.com/rubygems/rubygems/commit/c68b41b0e5

Merge RubyGems/Bundler master

2022-12-12T01:49:43+00:00

  from https://github.com/rubygems/rubygems/commit/bfb0ae69776069155d2092702bfbb5a12617d85a

[rubygems/rubygems] Fix misleading error if compact index cannot be copied

2022-07-14T06:06:09+00:00

Previously if `~/.bundle/cache/compact_index/rubygems.org.*/version`
were owned by root with read-only access, `bundle install` would fail
with a misleading error message. For example:

```
There was an error while trying to write to `/tmp/bundler-compact-index-20220711-1823-npllre/versions`. It is
likely that you need to grant write permissions for that path.
```

This happened because the EACCESS error was caught by
`SharedHelpers.filesystem_access`, which makes it look like the target
directory is at fault instead of the source.

We can't simply drop this guard because that causes the opposite
problem: the permission error appears to come from the source instead of
the target, since `CompactIndexClient::Cache#lines` also wraps read
access errors.

Instead, bring a minimal implementation of `FileUtils.cp` and nest calls
to `SharedHelpers.filesystem_access` properly.

https://github.com/rubygems/rubygems/commit/320822c070

Co-authored-by: Stan Hu

[rubygems/rubygems] Let original EACCES error be raised

2021-12-03T20:18:11+00:00

This block of code already wraps file operations with
`SharedHelpers.filesystem_access`, which rescues and re-raises more
friendly errors. Also, I'm not fully sure creating a temporary directory
can end up raising an `Errno::EACCES` error from reading `tmpdir`
sources. Finally, this rescue block apparently leads to some false
positives when firewall is blocking the ruby executable on Windows, or
at least that's what we've got reported.

In any case, I think it's best to let the original error be raised.

https://github.com/rubygems/rubygems/commit/f7dbe54404

Sync bundler & rubygems

2021-05-11T02:29:41+00:00