Jeff Handley

The [eng/pipelines/runtime.yml](https://github.com/dotnet/runtime/blob/71177d95d142a1341af9d7b5e8b4548889a42c70/eng/pipelines/runtime.yml#L1347-L1368) pipeline uses the [eng/pipelines/installer/jobs/build-job.yml](https://github.com/dotnet/runtime/blob/71177d95d142a1341af9d7b5e8b4548889a42c70/eng/pipelines/installer/jobs/build-job.yml) template, which uses the [eng/pipelines/common/download-artifact-step.yml](https://github.com/dotnet/runtime/blob/71177d95d142a1341af9d7b5e8b4548889a42c70/eng/pipelines/common/download-artifact-step.yml) step. This results in running the `ExtractFiles@1` task with the following inputs: * `archiveFilePatterns`: `D:\a\_work\1\s\__download__\CoreCLR_Libraries_BuildArtifacts_windows_x86_Release\**\CoreCLR_Libraries_BuildArtifacts_windows_x86_Release.zip` * `destinationFolder`: `D:\a\_work\1\s\artifacts\bin` *...

@Jozkee Are there any other tests in this realm that are still active and causing noise, or do you think they're all disabled now? It looks like the hit count...

No recent reports and much of the internal implementation has been changed since this was logged. Closing.

The description has been edited to reflect that this issue affects .NET 6, .NET 8, and .NET 9. The issue is addressed in the upcoming .NET 6.0.34, .NET 8.0.10, and...

Tagging @artl93 for review (and merge) into release/9.0. This reacts to macOS Sequoia changing behavior; our existing unit tests were failing on the platform so no new tests were needed....

See: [Announcing System.CommandLine 2.0.0-beta5 and our path to a stable release #2576 ](https://github.com/dotnet/command-line-api/issues/2576)

This is either a bug in VS or something we need to tweak in our API docs.

I published the [NuGet Gallery | sqlite-vec 0.1.7-alpha.2.1](https://www.nuget.org/packages/sqlite-vec/#readme-body-tab) package based on this project, producing the build from the [0.1.7-alpha.2.nuget (jeffhandley/sqlite-vec)](https://github.com/jeffhandley/sqlite-vec/tree/release/0.1.7-alpha.2.nuget) branch of my fork. That branch on my fork uses...

> 23 | type: number That is a bogus lint error from the actionlinter. `number` is a valid type for workflow dispatch inputs: https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#onworkflow_dispatchinputsinput_idtype So far, I'm striking out figuring...

Bumping superlinter to v7 addressed those lint issues. But now there are others to address. Will continue ~~Wednesday~~ _Thursday._