https://github.com/pantsbuild/pants/pull/8568 adds options to specify retry behavior and connection pool size when fetching from the v1 http artifact cache! i tried to avoid adding any special logic and focused on just mapping pants option values to constructor args for

requests

and

urllib3

classes. i'd really like to merge this sooner rather than later so i will probably merge before Sunday if nobody has time to review. this is a first attempt at solving this problem, it's scoped to a single subsystem so we can deprecate this approach en masse if it turns out to be wrong at first -- which is why i'm leaning towards trying to merge it earlier, so i can get feedback from users on whether it's working. this would be a massive win for many pants users at twitter who try to develop on a train or plane, and i suspect it will be similarly useful for other organizations using pants.

I’m looking at it now, but note that we should never merge without review:

i’d really like to merge this sooner rather than later so i will probably merge before Sunday if nobody has time to review.

what is the alternative?

what is the alternative?

Pinging reviewers to ask them to review, which often means things like DMing over Slack if they’re free to review during the week. But fundamentally we never should merge without review. It’s too dangerous of a precedent, even for simple PRs

ok, correction: not merging without review!

Yes, thanks for clarifying: let's not merge without review, except maybe to unbreak master in exceptional circumstances. But generally speaking, since we're not powering life-support machines, it can wait, whatever "it" is...