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

[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.

[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

[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)