Coby Allred

One of the potential issues I've found while investigating this is the use of github URLs in pnpm-lock.yaml files instead of component versions, ex: ``` "github.com/xmldom/xmldom/c568938641cc1f121cef5b4df80fcfda1e489b6e" "github.com/faisalil/react-native-mock/[email protected]" "github.com/joonhocho/react-native-android-action-sheet/f7436395ffb41e23a7770de18601d703913b5a95" ```

The blocker our team had internally for this was resolved last week. @JamieMagee will hopefully be taking a look at this change later this week.

Did some preliminary investigation and work on the `cobya/StrongName` branch. This work is blocked pending strong name assembly releases of the Docker.DotNet (see [Can you provide a strong name for...

@marklio If you are using Visual Studio the C# tests (what's failing) should be automatically populated in the test explorer. Otherwise you can use `dotnet test .\ComponentDetection.sln`

@JamieMagee you probably have the most context to review this

I haven't heard any customer reports of this being an issue and we have already resolved the exception. Closing this unless something comes up.

Relevant function: `ResolveDependencySpecifications` in `PythonResolverBase`

@hravellamicrosoft we do not have a current ETA for this. The fixes in #962 will be rolled out in the next release of our internal tooling but this repo's discussions...

Ideally most of these issues will be resolved after the changes from #1091 are merged.

This will be handled in conjuction with #108