question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Darc incorrectly constructing download url for internal manifest symbols package

See original GitHub issue
  • This issue is blocking
  • This issue is causing unreasonable pain

https://dev.azure.com/dnceng/internal/_build/results?buildId=1282580&view=logs&j=40e1e683-ea82-5be9-b25e-899b65e1c0cb&t=94a692ec-20f2-55dd-1884-cf0cad1763a4&l=7141

This is an internal build, so the symbol package was uploaded to a nuget feed. The format of the package name appears to be confusing darc’s gather-drop, because it’s incorrectly constructing the package download URL:

It attempts https://pkgs.dev.azure.com/dnceng/internal/_apis/packaging/feeds/dotnet6-internal-symbols/nuget/packages/Microsoft.NET.Workload.Mono.ToolChain.Manifest-6.0.100.Msi.x64.6.0.0-preview.7.21377.20/versions/6.0.100/content. This appears to mean that it thinks the version number is 6.0.100, rather than 6.0.0-preview.7.21377.20

My hunch is that the - in the middle of the package name is confusing things. It’s unclear whether the error is on the arcade-services side or the version identification side. BAR appears to understand the version number correctly, according to the darc get-asset output, but it’s unclear why it would choose 6.0.100 later.

PS C:\r\arcade> darc get-asset --name "assets/symbols/Microsoft.NET.Workload.Mono.ToolChain.Manifest-6.0.100.6.0.0-preview.7.21377.20.symbols.nupkg"
Looking up assets with name 'assets/symbols/Microsoft.NET.Workload.Mono.ToolChain.Manifest-6.0.100.6.0.0-preview.7.21377.20.symbols.nupkg' in the last 30 days
assets/symbols/Microsoft.NET.Workload.Mono.ToolChain.Manifest-6.0.100.6.0.0-preview.7.21377.20.symbols.nupkg @ 6.0.0-preview.7.21377.20
Repository:    https://dev.azure.com/dnceng/internal/_git/dotnet-runtime
Branch:        refs/heads/internal/release/6.0-preview7
Commit:        01019e12c1292fc51496c2c3b52fb5141d0f0602
Build Number:  20210727.20
Date Produced: 7/27/2021 9:03 PM
Build Link:    https://dev.azure.com/dnceng/internal/_build/results?buildId=1262709
BAR Build Id:  99704
Released:      False
Channels:
- .NET 6 Preview 7 Internal
Locations:
- https://dev.azure.com/dnceng/internal/_apis/build/builds/1262709/artifacts (Container)
- https://pkgs.dev.azure.com/dnceng/internal/_packaging/dotnet6-internal-symbols/nuget/v3/index.json (Container)

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:18 (18 by maintainers)

github_iconTop GitHub Comments

1reaction
mmitchecommented, Aug 19, 2021

The sdk band version has to be in the package name, since there will eventually be multiple of them. I think we either need to change the version identifier (with a new test of course, since this stuff can be fragile) or change the way the package name is constructed so that it still contains 6.0.100, but perhaps with different delimiters. That may require reaction on the VS or installer side.

/cc @joeloff

1reaction
michellemcdanielcommented, Aug 19, 2021

Ok, I think I have a change that might fix the version parser. I will put up a PR and we can discuss.

Read more comments on GitHub >

github_iconTop Results From Across the Web

A failure occurred while executing com.android.build. ...
I am getting this error while I am building APK. Cause 1: org.gradle.workers.internal.DefaultWorkerExecutor$WorkExecutionException: A failure ...
Read more >
NuGet pack and restore as MSBuild targets
With the PackageReference format, NuGet 4.0+ can store all manifest metadata directly within a project file rather than using a separate .nuspec ...
Read more >
Xcode 15 Beta 7 Release Notes
Fixed: Devices running watchOS 10 beta 5 may receive an error that “The device is not available because there was an error downloading...
Read more >
The Internal Structure of Python Eggs - Setuptools
Thus, support from a package management tool is required. ... These may be direct download URLs, or the URLs of web pages containing...
Read more >
npm packages in the Package Registry
Learn how to build an npm or yarn package. Watch a video demo of how to publish npm packages to the GitLab Package...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found