Samuel Giddins

That's a good idea!

Yes, I will circle back here

I'm a bit unclear on what the issue is w/r/t `eval_gemfile`, and why that doesn't work for your needs? This also feels close to what https://github.com/segiddins/bundler-compose/tree/main is trying to solve...

From profiling with rbspy: ``` Time since start: 17s. Press Ctrl+C to stop. Summary of profiling data so far: % self % total name 20.64 69.22 - /Users/segiddins/Development/github.com/rubygems/rubygems/lib/rubygems/name_tuple.rb:95 15.48 35.65...

This happens as well if you force rubygems to error on requests to the compact index api, I get a 17s successful install when I do that. Seems to be...

https://github.com/rubygems/rubygems/pull/5182/commits/f63d08647a80f0024a1633414284a279ceb44564 is probably a good place to look for writing a failing spec for this

For another workaround, running with `BUNDLE_VERSION=system` will skip the trampolining as well, iirc

Can we add a test for the issue this is fixing?

Should we add a test covering this? is it potentially an encoding issue?

See https://github.com/rubygems/rfcs/pull/51