Fair. We run proxies, so “proxy or site?” is the question we care about, and I didn’t trust the error messages to answer it.

The point is what you do after. If the proxy hung you rotate it out. If the site hung you slow down on that site. requests blames the site by name either way, so you can end up throttling a site that’s fine and keeping a dead proxy. That’s why.

git log -S'some_string' -p is the one that pays for itself. it finds the commits where that string was added or removed, so you can track down when a function disappeared without reading through history. -G is the same idea with a regex, matching any changed line.

and git log --follow -p path/to/file keeps going across renames, which plain git log file won’t do.