Nuget update timeout caused by too many requests to https://dc.services.visualstudio.com:443/v2/track

[TomW-Skyline]

Is there an existing issue for this?

• I have searched the existing issues

Package ecosystem

Nuget

Package manager version

No response

Language version

No response

Manifest location and content before the Dependabot update

No response

dependabot.yml content

No response

Updated dependency

No response

What you expected to see, versus what you actually saw

Dependabot updates fail on our solution with "Dependabot timed out during its update". In the logging I see thousands of POST requests to "https://dc.services.visualstudio.com:443/v2/track". These request take a lot of time. What are they used for, and how can this be solved?

proxy | 2024/03/11 02:01:37 [623] POST https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:37 [623] 200 https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:37 [625] POST https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:37 [625] 200 https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:37 [627] POST https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:37 [627] 200 https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:37 [629] POST https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:37 [629] 200 https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:39 Posting metrics to remote API endpoint
proxy | 2024/03/11 02:01:39 Successfully posted metrics data via api client
proxy | 2024/03/11 02:01:41 [632] POST https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:41 [633] POST https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:41 [633] 200 https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:41 [632] 200 https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:43 [635] POST https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:43 [635] 200 https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:43 [637] POST https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:43 [637] 200 https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:43 [639] POST https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:43 [639] 200 https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:44 [641] POST https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:44 [641] 200 https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:48 [643] POST https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:48 [643] 200 https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:49 [645] POST https://dc.services.visualstudio.com:443/v2/track
proxy | 2024/03/11 02:01:49 [645] 200 https://dc.services.visualstudio.com:443/v2/track

Native package manager behavior

No response

Images of the diff or a link to the PR, issue, or logs

No response

Smallest manifest that reproduces the issue

No response

[JamieMagee]

@TomW-Skyline are you able to share a job id or which repository this is occurring on?

[TomW-Skyline]

Hi @JamieMagee, it's a private repository so unfortunately I cannot share the logging.

[JamieMagee]

@TomW-Skyline I understand that you can't post the full logs here, but if you're able to share just the job ID from the logs I can look into it from our side. The job ID appears in the logs as job_xxxxxxxxx. Without more information I can't debug further.

[JamieMagee]

Actually, this appears in a lot of job logs. Digging into it, it appears to be coming from Nuget. We use NuGet.Client, and posts telemetry using Microsoft.VisualStudio.Telemetry.

I can't immediately see a way to disable that.

[TomW-Skyline]

@TomW-Skyline I understand that you can't post the full logs here, but if you're able to share just the job ID from the logs I can look into it from our side. The job ID appears in the logs as job_xxxxxxxxx. Without more information I can't debug further.

@JamieMagee job_id=798930643

[TomW-Skyline]

Version update 803306246
Errored with the message "Dependabot timed out during its update" and 1 other error

[JamieMagee]

Thanks for that. I dug into it, and reached out to someone on the NuGet team, and it doesn't appear that they are sending the telemetry. I'll need to investigate further.

[TomW-Skyline]

Maybe this could help? https://learn.microsoft.com/en-us/dotnet/core/tools/telemetry#how-to-opt-out

[benmccallum]

I think this might be crippling our ability to get updates in our rather large mono repo.

Our setup is:

• NuGet
  • Centralised package versioning (Directory.Packages.props)
  • ~200 .csproj project files
  • ~10 solution files (are these crawled? because I do want to go to 1 sln with x slnf files)
• Yarn
• GitHub Actions

Logs:

• Version update 814783535
• Version update 811869810 (this one managed to create 2 PRs)

[brettfo]

The extra telemetry calls have been removed but there are still likely some timeout issues. Consolidating the timeout investigation to #9375.