[Pipeline Bug]: Pipeline can't handle PackageVersion-s with both quotation marks and spaces in them.

[DandelionSprout]

If a package's PackageVersion has a space in it, e.g. if the PackageVersion is "4.0 SP3", then the pipelines fail fairly quickly and throw an "Internal-Error-Dynamic-Scan" error.

Compare:

• New package: Microsoft.MSXML.4 version 4.0 SP3 #378933; space in PackageVersion ("4.0 SP3"), wrapped in quotation marks, threw Internal-Error-Dynamic-Scan on each run.
• New package: Microsoft.MSXML.4 version 4.0-SP3 #378943; the space is replaced with a dash (4.0-SP3), pipeline runs to completion.

[Trenly]

I'm not sure one package is enough to make the claim that this is an error with the pipelines. There are several counterxamples, where spaces validated just fine -

• New version: DirkJansen.MailCheck2 version 2.146 (Build 594) #348635
• Update: IZArc.IZArcCommandLineAddon version 1.1 (Build 140) #339563
• New package: mcmilk.7zip-zstd-ndm version 25.01-v1.5.7-R4 NDM #329408
• New package: Qualibyte.Pixelformer version 0.9.6.3 RC3 #209894
• New package: Syntropica_Studio.GSML version ALPHA 1.0.1 #358047
• New version: win32ss.Supermium version 144.0.7559.247 R2 (144-r2) #355365

[DandelionSprout]

Looking through those 6 counterexamples, apparently none of those used quotation marks around the version number, whereas my situation did. Maybe that's a factor, though I'm unsure when I'd be to test that.

[Trenly]

I'm not sure how that would make a difference, since in the YAML spec both would be treated as strings, and the CLI even parses the values in and treats quoted and unquoted values the same. I suppose it could be a factor, I'm just struggling to see how it would be.

Definitely something the Engineering team can look into through