Sometimes it fails even earlier:

Select option: 1
Github login: akhavr
Error: Get "https://api.github.com/users/akhavr": read tcp 192.168.1.193:52634->140.82.121.6:443: read: connection reset by peer

Will play more with the bridge creation trying to catch most failure modes.

This bot triages pull requests in order to help the maintainers
identify what needs attention, according to the following lifecycle
rules:

• After 90 days of inactivity, lifecycle/stale is applied
• After 90 days of inactivity since lifecycle/stale was applied,
  lifecycle/rotten is applied

This bot will not automatically close stale pull requests.

To remove the stale status, you can:

• Remove the stale label from this pull request
• Comment on this issue
• Close this issue
• Offer to help out with triage and code review

To avoid automatic lifecycle management of this pull request, add
lifecycle/frozen.

Should we adopt something like backoff? (https://pkg.go.dev/github.com/cenkalti/backoff/v4)

yes :)