I'm not happy with the current one. Ideally, I'd like to rewrite it in Python using better diagnostic collection tools. I don't see it happening in 1.3.0, however.

This is no longer relevant now that curl has been almost entirely removed from the interface. Source addresses and such can be set for commit-archive, and authentication variables are set individually for each session.

I'm going to delete loadkey from 1.4 some time after 1.3 comes out.

I assumed the last element of .history[] is the final URL, so I had it display .history[-1]; but it turns out it overwrites .url with the final destination and only keeps the previous redirects in .history[]. Now it just displays .url if .history[] is not empty.

The way it's done right now is like this:

curl is no longer relevant as it was superseded by the new remote module.

Assuming it does not (and I can't replicate this), since the responsible code was rewritten in November to properly use low-level sockets. Let me know if it still persists and I'll try to poke around Paramiko for performance bottlenecks.

Going to backport this to 1.3 as well.

Does this problem persist with the latest rolling version?

The way sockets are handled in the last version should've fixed this once and for all.

Less scary error messages are produced now.

Still works perfectly fine for 1.3 nightly. (1.3-beta-202111240443)

I did a quick test with 1.3.0-epa3 and this config loads in about 6 minutes in my VM (2 GB memory, 1 core at 1,6 GHz) at boot, some WireGuard config errors notwithstanding. After all the performance improvements, I think we can consider this resolved at this point.

Something about commands is meddling with strip-private. I'm looking into it.

Now this is quite strange....

$ echo '2001:1578:2fe:fffd::/64' | strip-private
xxxx:xxxx:2fe:fffd::/64

Backport to 1.3 is complete. See T3821 for further discussion.