Patrick Hallisey

To be clear, I understand CUE4Parse ships with the native assembly, it's just not in the correct folder in the nuget package. Native assemblies should be in `/runtimes/{rid}/native/` not `/lib/`

> The test is failing [here](https://dev.azure.com/azure-sdk/public/_build/results?buildId=4240308&view=logs&j=5c952eb6-394a-5f6b-81c4-fd6e00460747&t=324a3550-b8a5-548f-4819-7b5944e418be&l=79), seems we need to add [vitest.config.ts](https://github.com/microsoft/typespec/blob/main/packages/http-client-csharp/emitter/vitest.config.ts) @live1206 Should we add the test config once we have tests?

> Just realized your point. We should add `--passWithNoTests` to `npm run test`, we have met this [before](https://github.com/Azure/autorest.csharp/pull/5032#issue-2500153913) This should only be for when we know there are no tests...

I think it's pragmatic to wait a reasonable amount of time for process exit. I don't know that it's reasonable to bind our "do something with an external process" call...

It looks like our resource cleanup functions support some AI resource soft deletes: https://github.com/Microsoft/mcp/blob/main/eng/common/scripts/Helpers/Resource-Helpers.ps1#L43-L44 We may need to add additional discovery and delete logic if they don't fall under the...

I think we have some existing powershell scripts that do token minting and KV signing for doing GitHub app installation auth. Maybe that's also sha-384 and we can just borrow...

I save the name of the file I'm parsing to file, then collect the name if the process dies while parsing. It appears to happen only with foliage related assets....

It looks like the issue is with nanite resource parsing: https://github.com/FabianFG/CUE4Parse/blob/master/CUE4Parse/UE4/Assets/Exports/Nanite/NaniteResources.cs#L357 ```cs var nanite = new FByteArchive("PackedCluster", Ar.ReadArray(), Ar.Versions); ``` In `SM_OceanLight01A.uasset` the length for the array is read as...

@chidozieononiwu, can you check the server.json content to make sure it's correct for npx packaging?

Can you update `servers/Template.Mcp.Server` as well? I'd like to be able to test this as part of Template's release pipeline