NuGet packages allow non-ASCII characters, and currently the NuGet ingestor is not escaping non-ASCII characters when fetching the packages, so we're seeing this error and not ingesting those packages:
URI must be ascii only "https://nuget.org/packages/...."
this PR escapes the name in the proper places (note that the NuGet source actually lists the escaped version as the canonical name in the HTML, e.g. here), including while unzipping the package's .nuspec file and checking each filename.
NuGet packages allow non-ASCII characters, and currently the NuGet ingestor is not escaping non-ASCII characters when fetching the packages, so we're seeing this error and not ingesting those packages:
this PR escapes the name in the proper places (note that the NuGet source actually lists the escaped version as the canonical name in the HTML, e.g. here), including while unzipping the package's .nuspec file and checking each filename.