[main] Update dependencies from microsoft/usvc-apiserver

[dotnet-maestro]

This pull request updates the following dependencies

From https://github.com/microsoft/usvc-apiserver

• Subscription: 852f69a6-643d-499a-6cb6-08dbca4ebb98
• Build: 0.1.46
• Date Produced: January 8, 2024 7:44:28 PM UTC
• Commit: 10caa62514311b78e4d8a85a25559d31fc5f17f0
• Branch: refs/heads/production

• Updates:
  • Microsoft.DeveloperControlPlane.darwin-amd64: from 0.1.45 to 0.1.46
  • Microsoft.DeveloperControlPlane.darwin-arm64: from 0.1.45 to 0.1.46
  • Microsoft.DeveloperControlPlane.linux-amd64: from 0.1.45 to 0.1.46
  • Microsoft.DeveloperControlPlane.linux-arm64: from 0.1.45 to 0.1.46
  • Microsoft.DeveloperControlPlane.windows-386: from 0.1.45 to 0.1.46
  • Microsoft.DeveloperControlPlane.windows-amd64: from 0.1.45 to 0.1.46
  • Microsoft.DeveloperControlPlane.windows-arm64: from 0.1.45 to 0.1.46

Microsoft Reviewers: Open in CodeFlow

[davidfowl]

Does this have the proxy changes?

[dnegstad]

The proxy changes merged this morning; this is a related fix for an error installing the workload on Mac/Linux with those changes.

[dnegstad]

Ah, wrong PR; yes, this is the proxy change.

[davidfowl]

cc @balachir the latest builds have the proxy changes. @dnegstad Are you going to send the PR that undoes that complex http client logic in p2?

[davidfowl]

@karolz-ms @dnegstad I thought the errors on startup would go away with the custom proxy:

[karolz-ms]

I thought this one is related to Azure connectivity and is unrelated to the proxy? @eerhardt ?

[davidfowl]

There's no azure in this sample, its all local proxies (its talking to rabbitmq)

[eerhardt]

I've submitted #1628 to re-add logging for Redis. This was the change blocked on the proxy issue. With that change I am not seeing errors on startup with the Redis connections.

Looking now why we are seeing it with RabbitMQ. My guess is that RabbitMQ takes that much longer to startup, and our proxy is closing the connection.

[davidfowl]

I would guess that too, @karolz-ms is there some fixed timeout that the proxy connection has?

[karolz-ms]

If there is no backed to serve the request, the proxy will not drop the connection. But if there is a backend, the timeout to connect is 5 seconds. From a cursory glance at RabbitMQ container logs it looks like it takes the container longer than that to start serving incoming traffic.

[karolz-ms]

@eerhardt if you indeed see that the proxy is closing the connection, LMK. I can change its behavior so that it keeps trying to connect till it succeeds (or till the client gives up waiting for the response).

EDIT: double checked the code and the proxy is supposed to do that already. So LMK what you find. My bet is the RabbitMQ client is giving up after not receiving a response.