proxy-investigation.md

Understanding test-proxy stack overflow errors

Existing failures:

Check .NET Version availability

On the same terminal that you would invoke test-proxy on, please run:

dotnet --list-sdks

What versions do you have on your machine?

Set debug logging, re-run your attempt to push

If you know where your recordings are, and you don't currently have a change, please manually add a newline to the end of a recording file. This will put it into the state where you can actually attempt to push, as the proxy will only do so when changes are pending.

Then, in the same terminal that you will run test-proxy push in, please set the following environment variable:

# powershell
$env:LOGGING__LOGLEVEL__DEFAULT="Debug"

# bash
export LOGGING__LOGLEVEL__DEFAULT="Debug"

Then attempt to push your change.

By enabling debug logging, we should see a raw ToString() of the CommandException from our shell out to git. I have a suspicion that we aren't handling an issue here somehow.

Try a standalone version of the test-proxy

• Download an appropriate version from the release here.
• Unzip, locate Azure.Sdk.Tools.TestProxy.exe within the unzipped folder
• Utilize that exe instead of calling the installed .NET tool test-proxy.
  • path/to/Azure.Sdk.Tools.TestProxy.exe push -a path/to/assets.json