Pranav K

@stephentoub both of these failures occurred on ARM64. Does that ring a bell in any form, particularly around launching processes? I was planning to set up a ARM VM and...

This is similar to https://github.com/dotnet/aspnetcore/issues/37143, but with Server rendering, not WASM. Could you use https://github.com/dotnet/aspnetcore/issues/37143#issuecomment-931726256 as a workaround to unblock yourself?

_Finally_ got around to this, but I'm running in to a fun issue with running our benchmarks with AOT enabled: ``` blazor.webassembly.js:1 RuntimeError: null function or function signature mismatch at...

> Yeah that's probably it, cc @pranavkm who lead me astray Serves you right for trusting me 😄

Our triage decision was to look at replacing this with https://github.com/dotnet/aspnetcore/issues/17528 if that becomes a thing. At this point, that's not scheduled work. Given that this package is stable and...

Clearing milestone for re-triage. This was brought up during https://github.com/dotnet/aspnetcore/issues/13174

139 usually means access violation. Is this error consistent? Do you get this running other `dotnet` commands?

Sorry, completed missed this. I can send a PR