Failed to create pull request: AggregateError

[cancan101]

Describe the bug
A clear and concise description of what the bug is.

Categorization

• This is not a permissions issue (Seek help at 403 error when Dependabot tries to create a pull request #1245)

Repository
URL: https://dev.azure.com/laticrete/Public%20Repos/

To Reproduce
Steps to reproduce the behavior:
Looks to be sporadic and due to a timeout.

Expected behavior
A clear and concise description of what you expected to happen.
Longer timeout and / or retry behavior

Logs and screenshots
https://dev.azure.com/laticrete/Public%20Repos/_build/results?buildId=10729&view=results

 - Adding dependency metadata to pull request properties...
##[error]Failed to create pull request: AggregateError
AggregateError [ETIMEDOUT]: 
    at internalConnectMultiple (node:net:1118:18)
    at internalConnectMultiple (node:net:1186:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1712:5)
    at listOnTimeout (node:internal/timers:583:11)
    at process.processTimers (node:internal/timers:519:7) {
  code: 'ETIMEDOUT',
  [errors]: [
    Error: connect ETIMEDOUT 13.107.42.20:443
        at createConnectionError (node:net:1648:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1707:38)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '13.107.42.20',
      port: 443
    },
    Error: connect ENETUNREACH 2620:1ec:21::20:443 - Local (:::0)
        at internalConnectMultiple (node:net:1182:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1712:5)
        at listOnTimeout (node:internal/timers:583:11)
        at process.processTimers (node:internal/timers:519:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2620:1ec:21::20',
      port: 443
    }
  ]
}

Extension (please complete the following information):

• Host: [e.g. Azure DevOps, Azure DevOps Server]
• Version [e.g. 1.2.54]

Server (please complete the following information):

• Region [e.g. westeurope]
• Version [e.g. 1.2.54]

Additional context
Add any other context about the problem here.

[rhyskoedijk]

@cancan101 thanks for the report. ENETUNREACH sounds like a low-level network issue, which is surprising to see given the previous APIs succeeded.

This could probably be fixed by adding some basic retry logic for the API calls; I will look into this when I have some free time.

[mburumaxwell]

@cancan101 how often does this happen? Is it always the same? Does retrying it fix it?