[BUG] ManagedIdentityCredential takes a long time to fail when used in ChainedTokenCredential

Library name and version
Azure.Identity 1.12
Describe the bug
The ManagedIdentityCredential will probe IMDS and fail quickly but this only works when it's created via DefaultAzureCredential. If a ManagedIdentityCredential is manually created and and used within a ChainedTokenCredential the ManagedIdentityCredential will keep retrying and take ~25 seconds to fail.
Expected behavior
Ability to leverage the probing functionality of ManagedIdentityCredential without needing to rely on DefaultAzureCredential.
Actual behavior
(See repro steps below for the full error output)
Reproduction Steps

Took 00:00:01.0039585 to get token from DefaultAzureCredential. Expires on 8/22/2024 7:56:24 PM +00:00.
Took 00:00:24.5510537 to get token from ChainedTokenCredential. Expires on 8/22/2024 7:56:24 PM +00:00.

Sample:
        	using AzureEventSourceListener listener = AzureEventSourceListener.CreateConsoleLogger();

	var chainedCredential = new ChainedTokenCredential(
		new ManagedIdentityCredential(options: new TokenCredentialOptions
		{
			Diagnostics = { IsLoggingEnabled = true, L }
		}),
		new AzureCliCredential());

	var defaultAzureCredential = new DefaultAzureCredential(new DefaultAzureCredentialOptions
	{
		Diagnostics = { IsLoggingEnabled = true },
		ExcludeAzureCliCredential = false,
		ExcludeManagedIdentityCredential = false,
		// Disable other mechanisms so we're comparing the same thing
		ExcludeAzurePowerShellCredential = true,
		ExcludeEnvironmentCredential = true,
		ExcludeInteractiveBrowserCredential = true,
		ExcludeAzureDeveloperCliCredential = true,
		ExcludeSharedTokenCacheCredential = true,
		ExcludeVisualStudioCodeCredential = true,
		ExcludeVisualStudioCredential = true,
		ExcludeWorkloadIdentityCredential = true
	});

	var stopwatch = Stopwatch.StartNew();
	var token = await defaultAzureCredential.GetTokenAsync(new TokenRequestContext(new[] { "https://storage.azure.com/.default" }));
	Console.WriteLine($"Took {stopwatch.Elapsed} to get token from DefaultAzureCredential. Expires on {token.ExpiresOn}.");

	stopwatch.Restart();
	token = await chainedCredential.GetTokenAsync(new TokenRequestContext(new[] { "https://storage.azure.com/.default" }));
	Console.WriteLine($"Took {stopwatch.Elapsed} to get token from ChainedTokenCredential. Expires on {token.ExpiresOn}.");

Full output with telemetry:
[Informational] Azure-Identity: DefaultAzureCredential.GetToken invoked. Scopes: [ https://storage.azure.com/.default ] ParentRequestId:
[Informational] Azure-Identity: ManagedIdentityCredential.GetToken invoked. Scopes: [ https://storage.azure.com/.default ] ParentRequestId:
[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:05Z - 25cadb5b-5d18-4c87-8149-d5083bf4a560] MSAL MSAL.NetCore with assembly version '<IP_ADDRESS>'. CorrelationId(25cadb5b-5d18-4c87-8149-d5083bf4a560)
[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:05Z - 25cadb5b-5d18-4c87-8149-d5083bf4a560] === AcquireTokenForClientParameters ===
SendX5C: False
ForceRefresh: False

[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:05Z - 25cadb5b-5d18-4c87-8149-d5083bf4a560]
=== Request Data ===
Authority Provided? - True
Scopes - https://storage.azure.com/.default
Extra Query Params Keys (space separated) -
ApiId - AcquireTokenForClient
IsConfidentialClient - True
SendX5C - False
LoginHint ? False
IsBrokerConfigured - False
HomeAccountId - False
CorrelationId - 25cadb5b-5d18-4c87-8149-d5083bf4a560
UserAssertion set: False
LongRunningOboCacheKey set: False
Region configured:

[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:05Z - 25cadb5b-5d18-4c87-8149-d5083bf4a560] === Token Acquisition (ClientCredentialRequest) started:
     Scopes: https://storage.azure.com/.default
    Authority Host: login.microsoftonline.com
[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:05Z - 25cadb5b-5d18-4c87-8149-d5083bf4a560] [Region discovery] Not using a regional authority.
[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:05Z - 25cadb5b-5d18-4c87-8149-d5083bf4a560] [Instance Discovery] Skipping Instance discovery because it is disabled.
[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:05Z - 25cadb5b-5d18-4c87-8149-d5083bf4a560] [ClientCredentialRequest] Acquiring a token from the token provider.
[Informational] Azure-Core: Request [276e9385-9a56-433a-802e-b070999175b3] GET http://<IP_ADDRESS>/metadata/identity/oauth2/token?api-version=2018-02-01&resource=REDACTED
x-ms-client-request-id:276e9385-9a56-433a-802e-b070999175b3
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Identity/1.12.0 (.NET 6.0.33; Microsoft Windows 10.0.26100)
client assembly: Azure.Identity
[Informational] Azure-Core: Request [276e9385-9a56-433a-802e-b070999175b3] exception Azure.RequestFailedException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Http.HttpRequestException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Sockets.SocketException (10051): A socket operation was attempted to an unreachable network.
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request)
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   --- End of inner exception stack trace ---
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   at Azure.Core.Pipeline.HttpPipelineTransportPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
   at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
[Error] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:05Z - 25cadb5b-5d18-4c87-8149-d5083bf4a560] Exception type: Azure.Identity.CredentialUnavailableException
---> Inner Exception Details
Exception type: Azure.RequestFailedException
---> Inner Exception Details
Exception type: System.Net.Http.HttpRequestException
---> Inner Exception Details
Exception type: System.Net.Sockets.SocketException
To see full exception details, enable PII Logging. See https://aka.ms/msal-net-logging
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)

=== End of inner exception stack trace ===
To see full exception details, enable PII Logging. See https://aka.ms/msal-net-logging
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request)
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)

=== End of inner exception stack trace ===
To see full exception details, enable PII Logging. See https://aka.ms/msal-net-logging
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   at Azure.Core.Pipeline.HttpPipelineTransportPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
   at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.RedirectPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Identity.ManagedIdentitySource.AuthenticateAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
   at Azure.Identity.ImdsManagedIdentitySource.AuthenticateAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)

=== End of inner exception stack trace ===
To see full exception details, enable PII Logging. See https://aka.ms/msal-net-logging
   at Azure.Identity.ImdsManagedIdentitySource.AuthenticateAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
   at Azure.Identity.ManagedIdentityClient.AuthenticateCoreAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
   at Azure.Identity.ManagedIdentityClient.AppTokenProviderImpl(AppTokenProviderParameters parameters)
   at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.SendTokenRequestToAppTokenProviderAsync(ILoggerAdapter logger, CancellationToken cancellationToken)
   at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.GetAccessTokenAsync(CancellationToken cancellationToken, ILoggerAdapter logger)
   at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.ExecuteAsync(CancellationToken cancellationToken)
   at Microsoft.Identity.Client.Internal.Requests.RequestBase.<>c__DisplayClass11_1.<<RunAsync>b__1>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Identity.Client.Utils.StopwatchService.MeasureCodeBlockAsync(Func`1 codeBlock)
   at Microsoft.Identity.Client.Internal.Requests.RequestBase.RunAsync(CancellationToken cancellationToken)

[Informational] Azure-Identity: ManagedIdentityCredential.GetToken was unable to retrieve an access token. Scopes: [ https://storage.azure.com/.default ] ParentRequestId:  Exception: Azure.Identity.CredentialUnavailableException (0x80131500): ManagedIdentityCredential authentication unavailable. No response received from the managed identity endpoint.
 ---> Azure.RequestFailedException (0x80131500): A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Http.HttpRequestException (0x80004005): A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Sockets.SocketException (0x80004005): A socket operation was attempted to an unreachable network.
[Informational] Azure-Identity: AzureCliCredential.GetToken invoked. Scopes: [ https://storage.azure.com/.default ] ParentRequestId:
[Informational] Azure-Identity: AzureCliCredential.GetToken succeeded. Scopes: [ https://storage.azure.com/.default ] ParentRequestId:  ExpiresOn: 2024-08-22T19:56:24.0000000+00:00
[Informational] Azure-Identity: DefaultAzureCredential credential selected: Azure.Identity.AzureCliCredential
[Informational] Azure-Identity: DefaultAzureCredential.GetToken succeeded. Scopes: [ https://storage.azure.com/.default ] ParentRequestId:  ExpiresOn: 2024-08-22T19:56:24.0000000+00:00
Took 00:00:01.0039585 to get token from DefaultAzureCredential. Expires on 8/22/2024 7:56:24 PM +00:00.
[Informational] Azure-Identity: ManagedIdentityCredential.GetToken invoked. Scopes: [ https://storage.azure.com/.default ] ParentRequestId:
[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:06Z - 9c0a0a0f-f8a2-4188-a7b2-7e3a54ce10de] MSAL MSAL.NetCore with assembly version '<IP_ADDRESS>'. CorrelationId(9c0a0a0f-f8a2-4188-a7b2-7e3a54ce10de)
[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:06Z - 9c0a0a0f-f8a2-4188-a7b2-7e3a54ce10de] === AcquireTokenForClientParameters ===
SendX5C: False
ForceRefresh: False

[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:06Z - 9c0a0a0f-f8a2-4188-a7b2-7e3a54ce10de]
=== Request Data ===
Authority Provided? - True
Scopes - https://storage.azure.com/.default
Extra Query Params Keys (space separated) -
ApiId - AcquireTokenForClient
IsConfidentialClient - True
SendX5C - False
LoginHint ? False
IsBrokerConfigured - False
HomeAccountId - False
CorrelationId - 9c0a0a0f-f8a2-4188-a7b2-7e3a54ce10de
UserAssertion set: False
LongRunningOboCacheKey set: False
Region configured:

[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:06Z - 9c0a0a0f-f8a2-4188-a7b2-7e3a54ce10de] === Token Acquisition (ClientCredentialRequest) started:
     Scopes: https://storage.azure.com/.default
    Authority Host: login.microsoftonline.com
[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:06Z - 9c0a0a0f-f8a2-4188-a7b2-7e3a54ce10de] [Region discovery] Not using a regional authority.
[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:06Z - 9c0a0a0f-f8a2-4188-a7b2-7e3a54ce10de] [Instance Discovery] Skipping Instance discovery because it is disabled.
[Informational] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:06Z - 9c0a0a0f-f8a2-4188-a7b2-7e3a54ce10de] [ClientCredentialRequest] Acquiring a token from the token provider.
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] GET http://<IP_ADDRESS>/metadata/identity/oauth2/token?api-version=2018-02-01&resource=REDACTED
Metadata:REDACTED
x-ms-client-request-id:92e32410-d326-42e5-b976-2a3cfcb29ff8
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Identity/1.12.0 (.NET 6.0.33; Microsoft Windows 10.0.26100)
client assembly: Azure.Identity
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] exception Azure.RequestFailedException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Http.HttpRequestException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Sockets.SocketException (10051): A socket operation was attempted to an unreachable network.
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request)
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   --- End of inner exception stack trace ---
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   at Azure.Core.Pipeline.HttpPipelineTransportPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
   at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] attempt number 1 took 00.0s
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] GET http://<IP_ADDRESS>/metadata/identity/oauth2/token?api-version=2018-02-01&resource=REDACTED
Metadata:REDACTED
x-ms-client-request-id:92e32410-d326-42e5-b976-2a3cfcb29ff8
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Identity/1.12.0 (.NET 6.0.33; Microsoft Windows 10.0.26100)
client assembly: Azure.Identity
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] exception Azure.RequestFailedException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Http.HttpRequestException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Sockets.SocketException (10051): A socket operation was attempted to an unreachable network.
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request)
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   --- End of inner exception stack trace ---
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   at Azure.Core.Pipeline.HttpPipelineTransportPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
   at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] attempt number 2 took 00.0s
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] GET http://<IP_ADDRESS>/metadata/identity/oauth2/token?api-version=2018-02-01&resource=REDACTED
Metadata:REDACTED
x-ms-client-request-id:92e32410-d326-42e5-b976-2a3cfcb29ff8
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Identity/1.12.0 (.NET 6.0.33; Microsoft Windows 10.0.26100)
client assembly: Azure.Identity
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] exception Azure.RequestFailedException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Http.HttpRequestException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Sockets.SocketException (10051): A socket operation was attempted to an unreachable network.
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request)
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   --- End of inner exception stack trace ---
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   at Azure.Core.Pipeline.HttpPipelineTransportPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
   at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] attempt number 3 took 00.0s
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] GET http://<IP_ADDRESS>/metadata/identity/oauth2/token?api-version=2018-02-01&resource=REDACTED
Metadata:REDACTED
x-ms-client-request-id:92e32410-d326-42e5-b976-2a3cfcb29ff8
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Identity/1.12.0 (.NET 6.0.33; Microsoft Windows 10.0.26100)
client assembly: Azure.Identity
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] exception Azure.RequestFailedException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Http.HttpRequestException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Sockets.SocketException (10051): A socket operation was attempted to an unreachable network.
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request)
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   --- End of inner exception stack trace ---
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   at Azure.Core.Pipeline.HttpPipelineTransportPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
   at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] attempt number 4 took 00.0s
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] GET http://<IP_ADDRESS>/metadata/identity/oauth2/token?api-version=2018-02-01&resource=REDACTED
Metadata:REDACTED
x-ms-client-request-id:92e32410-d326-42e5-b976-2a3cfcb29ff8
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Identity/1.12.0 (.NET 6.0.33; Microsoft Windows 10.0.26100)
client assembly: Azure.Identity
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] exception Azure.RequestFailedException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Http.HttpRequestException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Sockets.SocketException (10051): A socket operation was attempted to an unreachable network.
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request)
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   --- End of inner exception stack trace ---
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   at Azure.Core.Pipeline.HttpPipelineTransportPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
   at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] attempt number 5 took 00.0s
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] GET http://<IP_ADDRESS>/metadata/identity/oauth2/token?api-version=2018-02-01&resource=REDACTED
Metadata:REDACTED
x-ms-client-request-id:92e32410-d326-42e5-b976-2a3cfcb29ff8
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Identity/1.12.0 (.NET 6.0.33; Microsoft Windows 10.0.26100)
client assembly: Azure.Identity
[Informational] Azure-Core: Request [92e32410-d326-42e5-b976-2a3cfcb29ff8] exception Azure.RequestFailedException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Http.HttpRequestException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Sockets.SocketException (10051): A socket operation was attempted to an unreachable network.
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request)
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   --- End of inner exception stack trace ---
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   at Azure.Core.Pipeline.HttpPipelineTransportPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
   at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
[Error] Azure-Identity: False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.33 Microsoft Windows 10.0.26100 [2024-08-22 18:43:29Z - 9c0a0a0f-f8a2-4188-a7b2-7e3a54ce10de] Exception type: Azure.Identity.CredentialUnavailableException
---> Inner Exception Details
Exception type: System.AggregateException
---> Inner Exception Details
Exception type: Azure.RequestFailedException
---> Inner Exception Details
Exception type: System.Net.Http.HttpRequestException
---> Inner Exception Details
Exception type: System.Net.Sockets.SocketException
To see full exception details, enable PII Logging. See https://aka.ms/msal-net-logging
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)

=== End of inner exception stack trace ===
To see full exception details, enable PII Logging. See https://aka.ms/msal-net-logging
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(HttpRequestMessage request)
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)

=== End of inner exception stack trace ===
To see full exception details, enable PII Logging. See https://aka.ms/msal-net-logging
   at Azure.Core.Pipeline.HttpClientTransport.ProcessSyncOrAsync(HttpMessage message, Boolean async)
   at Azure.Core.Pipeline.HttpPipelineTransportPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline)
   at Azure.Core.Pipeline.ResponseBodyPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.LoggingPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.RedirectPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)

=== End of inner exception stack trace ===
To see full exception details, enable PII Logging. See https://aka.ms/msal-net-logging
   at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Identity.ManagedIdentitySource.AuthenticateAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
   at Azure.Identity.ImdsManagedIdentitySource.AuthenticateAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)

=== End of inner exception stack trace ===
To see full exception details, enable PII Logging. See https://aka.ms/msal-net-logging
   at Azure.Identity.ImdsManagedIdentitySource.AuthenticateAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
   at Azure.Identity.ManagedIdentityClient.AuthenticateCoreAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
   at Azure.Identity.ManagedIdentityClient.AppTokenProviderImpl(AppTokenProviderParameters parameters)
   at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.SendTokenRequestToAppTokenProviderAsync(ILoggerAdapter logger, CancellationToken cancellationToken)
   at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.GetAccessTokenAsync(CancellationToken cancellationToken, ILoggerAdapter logger)
   at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.ExecuteAsync(CancellationToken cancellationToken)
   at Microsoft.Identity.Client.Internal.Requests.RequestBase.<>c__DisplayClass11_1.<<RunAsync>b__1>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Identity.Client.Utils.StopwatchService.MeasureCodeBlockAsync(Func`1 codeBlock)
   at Microsoft.Identity.Client.Internal.Requests.RequestBase.RunAsync(CancellationToken cancellationToken)

[Informational] Azure-Identity: ManagedIdentityCredential.GetToken was unable to retrieve an access token. Scopes: [ https://storage.azure.com/.default ] ParentRequestId:  Exception: Azure.Identity.CredentialUnavailableException (0x80131500): ManagedIdentityCredential authentication unavailable. Multiple attempts failed to obtain a token from the managed identity endpoint.
 ---> System.AggregateException (0x80131500): Retry failed after 6 tries. Retry settings can be adjusted in ClientOptions.Retry or by configuring a custom retry policy in ClientOptions.RetryPolicy.
[Informational] Azure-Identity: AzureCliCredential.GetToken invoked. Scopes: [ https://storage.azure.com/.default ] ParentRequestId:
[Informational] Azure-Identity: AzureCliCredential.GetToken succeeded. Scopes: [ https://storage.azure.com/.default ] ParentRequestId:  ExpiresOn: 2024-08-22T19:56:24.0000000+00:00
Took 00:00:24.5510537 to get token from ChainedTokenCredential. Expires on 8/22/2024 7:56:24 PM +00:00.

Environment
No response

Hi @giulianob - This is the expected default behavior.
If you want to customize the retry behavior, this can be done by customizing the RetryOptions on the options passed to the ManagedIdentityCredential

@christothes I haven't been able to find a way to accomplish the same thing as what DefaultAzureCredentials does without some hacking around. I believe I would have to essentially re-implement what is available internally but not exposed:

Implement a custom pipeline that keeps track of the first request to ManagedIdentity and removes the Metadata header to do the probing request
Make the network timeout conditional on whether it's the first request
Implement a custom retry policy which then keeps track of whether it's a probing request and does not retry

I understand this is currently the expected behavior but this is a design bug IMO if using managed identity within the ChainedTokenCredential takes ~25s every time.

If you want the probe behavior, you could replace ManagedIdentityCredential with DefaultAzureCredential in your chain and construct it with DefaultAzureCredentialOptions setting all the Exclude*Credential properties set to true except for ExcludeManagedIdentityCredential.

I understand this is currently the expected behavior but this is a design bug IMO if using managed identity within the ChainedTokenCredential takes ~25s every time.

ManagedIdentityCredential is designed to be resilient when attempting to connect to the IMDS endpoint and will retry exponentially. As mentioned in my previous reply, the retry behavior can be customized. However, since it is not constructed by the ChainedTokenCredential it is not aware that it is part of a chain and will not be configured with the probing behavior.

@christothes: we understand the behavior is as designed. Our comment is that the behavior as designed caused an unexpected issue for us. As @giulianob pointed out, any customer that hits the unexpected issue would need to recreate the retry behavior themselves. If the retry behavior in DefaultAzureCredential were easier to use it would have made this issue easier to solve.


Add plugin: Tabler picker

Submit a new Plugin to Marketplace
Plugin Github repo URL: https://github.com/yoyurec/logseq-tabler-picker
✨ Tabler icon picker plugin for Logseq

Github releases checklist

[x] a legal package.json file.
[x] a valid CI workflow build action for Github releases. (Optional for theme plugin only).
[x] a release which includes a release zip pkg from a successful build.
[x] a clear README file, ideally with an image or gif showcase. (For more friendly to users, it is recommended to have English version description).
[x] a license in the LICENSE file.

@xyhp915 🙏

Helper plugin https://github.com/logseq/logseq/pull/8758


fix: Fixed TCP and UDP Port Drift on Application Segment Resources

Provide a general summary of your changes in the title above. You should
remove this overview, any sections and any section descriptions you
don't need below before submitting. There isn't a strict requirement to
use this template if you can structure your description and still cover
these points.
Description
Describe your changes in detail through motivation and context. Why is
this change required? What problem does it solve? If it fixes an open
issue, link to the issue using GitHub's closing issues keywords1.
Has your change been tested?
Explain how the change has been tested and what you ran to confirm your
change affects other parts of the code. Automated tests are generally
expected and changes without tests should explain why they aren't
required.
Screenshots (if appropriate):
Types of changes
What sort of change does your code introduce/modify?

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] This change is using publicly documented and stable APIs.

Codecov Report
Attention: Patch coverage is 75.67568% with 18 lines in your changes missing coverage. Please review.

Project coverage is 74.65%. Comparing base (076b0c6) to head (06d8f50).

Files with missing lines
Patch %
Lines

zpa/resource_zpa_application_segment.go
72.72%
9 Missing and 6 partials :warning:

zpa/utils.go
80.00%
2 Missing and 1 partial :warning:

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #481      +/-   ##
==========================================
+ Coverage   74.07%   74.65%   +0.57%
==========================================
  Files          92       92
  Lines       16857    16858       +1
==========================================
+ Hits        12487    12585      +98
+ Misses       3548     3433     -115
- Partials      822      840      +18

Files with missing lines
Coverage Δ

zpa/resource_zpa_application_segment_inspection.go
62.16% <100.00%> (-3.09%)
:arrow_down:

zpa/resource_zpa_application_segment_pra.go
55.69% <100.00%> (-2.47%)
:arrow_down:

zpa/utils.go
72.87% <80.00%> (+3.09%)
:arrow_up:

zpa/resource_zpa_application_segment.go
56.46% <72.72%> (+29.46%)
:arrow_up:

... and 2 files with indirect coverage changes


didcomm demo: issuer.example.com: user consent while connecting wallet

During the process of connecting the issuer adapter with the user's wallet, the user is asked for their consent:
Click to expand

This screen should either be hidden altogether from the user or refactored to make it look like the user is approving Terms+Conditions. Or some other creative solution.
The problem with this screen right now are:

The user is introduced to an unknown (by them) "third party application" named "auth-code-client" that wishes to "access resources on their behalf". The user does not know this 3rd party application's identity
The user is already interacting with the party that holds the user's data (the issuer - issuer.example.com). They shouldn't have to delegate authority unto anyone else to fetch the data
The user might get the impression that they are already sharing the data when in fact that steps comes later

During yesterday's call there seemed to be confusion and/or disagreement around whether this is a problem or not.
First, we need to be clear and aligned on the model we are demonstrating here.
When we say "an issuer issues a credential to the user" in this demo, we are:

referring to an interaction between two parties: the user and the issuer
implying the issuer is the producer of the data

Since in this model there are no third parties involved, there is no one else for the user to delegate authority unto.
After the user has logged in, the issuer offers the capability to "download their credential" via an onscreen button. The user clicks on that button and the issuer fetches the data and transfers it over to the user's agent.
This is akin to downloading a digital copy of your credit card statement from your bank. After you log in, you just click the download button and viola.

@llorllale Currently the issuer (CMS) contains multiple sets of data for the user and the user is giving consent to the issuer to release (create credential for) certain set of data (represented by scope). This was original requirement from @troyronda. We may not need it any more, however @troyronda has to confirm it.

@sandrask

Currently the issuer (CMS) contains multiple sets of data for the user and the user is giving consent to the issuer to release (create credential for) certain set of data

I see three parties mentioned here: the user, an issuer of a credential, and a third party collecting and producing the user's data.
Introducing the third party just seems like a demonstration of the OAuth2 auth code flow... which is not very useful in this leg of the demo's flow.


use Heroku database in development

I'm trying to initiate a project with Heroku database in development mode.
I updated config/database.js:
  development: {
    username: 'XXXX',
    password: 'XXXXX',
    database: 'XXXXX',
    host: 'XXXXX.compute-1.amazonaws.com',
    dialect: 'postgres'
  },

Loaded configuration file "config/database.js".
Using environment "development".
ERROR: connect ECONNREFUSED
What I'm doing wrong?

You need start application with command "npm rum dev" for load "database.developement"

Any message in the Heroku logs?

heroku requires encryption for connections to database
sslMode=require

Heroku needs SSL for outside connections. So you can read more in this article https://devcenter.heroku.com/articles/heroku-postgresql#connecting-in-node-js


Old Extensions shown in marketplace search

I've installed https://github.com/cdr/code-server/releases/download/v3.8.0/code-server_3.8.0_amd64.deb (v1.51.1)
When I search in code-server v3.8.0 for "intelephense" in Extensions Marketplace, "PHP Intelephense 1.5.4" is shown.
When I search in vs-code v1.52.1 for "intelephense" in Extensions Marketplace, "PHP Intelephense 1.6.1" is shown.
When I open https://marketplace.visualstudio.com/items?itemName=bmewburn.vscode-intelephense-client "PHP Intelephense 1.6.1" is shown.
I'd expect latest extension versions shown in Marketplace.
My remote installation (docker):
https://github.com/thomasbley/example_tasks_php/blob/master/docker/vscode/Dockerfile

Web Browser: Firefox 86.0a1
Local OS: Mint Linux 20
Remote OS: debian:buster-slim
Remote Architecture: amd64
code-server --version: 3.8.0

The issue is fixed with 3.9.0, thanks!


上币请求

{
"symbol": "EOC",
"address": "0x7ab2174c7151cb84f91bb818e07a72a5420a37e",
"overview": {
"Project description":"Energy video box EOCThe foundation was established in Singapore in 2018. The EOC is based on the basic encrypted currency of the Etifang ERC20 network. It has a total circulation of 26 million pieces and is an extremely rare currency. It can circulate throughout the Etifang block chain network. EOC is based on the decentralized film and television application developed by ERC20. It is promoted, mined, and purchased by the users of the decentralized application(energy box), and is used in the application to generate value through recharging VIP, in-mall item trading, and mining. And as the number of transactions decreases, the market value can continue to increase."
"Team background": "Founded in Singapore in 2018, the Energy Box EOC Foundation has an average of more than 10 years of Internet product development experience. It is a technical team in the field of early research blocks in foreign countries. The EOC is committed to building a value discovery platform for connecting trading platforms, block chain companies, and investors. Committed to building the world's leading block chain film application"
},

You modified all the data. Please submit again.


Add Rudderstack analytics to registry

Docs

Hey, thanks for requesting this integration. I've recently made a discussion for submitting these, would you mind copying it over to this :pray:
https://github.com/nuxt/scripts/discussions/177
Thanks!


Fixing folder/file case sensitive renaming issue

Example:
Could not rename folder "Objects" to "objects" or vice versa.
Could not rename "Player.tscn" to "player.tscn" or vice versa

One possible solution is to rely on preprocessor directives for this condition

Yes, could you do this @Straskal?
I don't think this will be a big performance hit, but I prefer to avoid adding Windows-specific checks to all other platforms.

You got it!

Great :) Be sure to use git commit --amend to edit the commit, and force push to update the PR (see PR workflow).

Merged manually as e790ca084 with the requested changes.


Unified system for visualizer-resolved component defaults

At the moment, the monolithic EntityProperties is made up of several EditableAutoValues that are populated as part of  on_frame_start.
As we move away from EditableAutoValues as part of https://github.com/rerun-io/rerun/issues/4442, we need a new way to compute default-component-values.
There are two main complications:

We would like to be able to compute these values with knowledge of the space view state. For example, some default values are reactive to bounding box, or the existence of other components.
We want to reliably know what the default value would be, even if it's unused, in the SelectionPanel.

This got all addressed in 0.17 using the fallback system!


Cryptomatte AOVs causes Python launched render to fail

Adding a Cryptomatte AOV (object or material) to the frame AOV container in Python will cause the render to fail at some point.  It seems to be caused by the mere presence of the AOV, as the crashes still occur even when the AOV container is not accessed in any way.
This is through Blender (both 2.79b with Python 3.5 and 2.8 with Python 3.7).  No error messages are generated, instead the render (and Blender itself) just stops suddenly and shuts down.  When this happens is also inconsistent.  Sometimes a full render is finished and it crashes when I try to run another one.  In other cases it will fail at startup.  Other times it fails in the middle of the render.
Regular color and single channel AOVs work properly.
Exporting scene files and rendering through appleseed.studio works fine as well.  It appears to be something with the Python bindings.

In addition: Whatever is happening isn't being caught by the VSCode debugger either.  Usually it's pretty good at catching exceptions in the Blender plugin so I can only assume this is happening somewhere deeper inside appleseed.

Turns out the Cryptomatte accumulator has a bug where it fills empty channels with black.  It's been fixed.


[backport] Change Link.add_hook to return self

Backport of #5736

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit cc0fb951c93575918e85ae20cf11865d79a50add, target branch v5) succeeded!


forcedSelectedIndex doesn't work

I set a forcedSelectedIndex value but it doesn't reset a toggle.
Only manual change of a toggle value works for me. How can I reset a toggle value in code?

Hello @YakimchykNadzeya,
I can't seem to reproduce the issue. I have deployed the storybook that lets you play around with props API: https://gr34se.github.io/react-switch-selector/
please see the given example with forcedSelectedIndex set to arbitrary value:
https://gr34se.github.io/react-switch-selector/?path=/story/switchselector--three-options&args=forcedSelectedIndex:2


Prep for V2

Hi folks! I'm beginning the process of squaring Inertia Django up to get ready for the Inertia V2 improvements that we're going to need, but it's now been several years since I've worked on a Django project professionally. If there's anyone in the community who is using Inertia Django actively and would be interested in collaborating with me on the V2 upgrade, please comment here or reach out!

I want to leave a comment to reflect my sense of excitement about a v2! I'm not an appropriate fit as I have just started using inertia and also found it a struggle to set it up, resorting to django-breeze to smooth over the process. Hoping this will be addressed in v2!

Hi. I am relatively new to Inertia (I only have one small project using it), but I do have lots of experience with Django. If there's anything I can do to help, I'd be happy to.

@eddyojb88 thank you that's great feedback! I also maintain Inertia Rails and we've felt that same onboarding pain over there. We got luckily in Rails and a top notch company helped build an installer, but that doesn't mean we can't improve the Django situation! Was there anything in particular that tripped you up or was it just too confusing in general?
@sopelj Thanks for the reply! Lots of experience with Django is exactly what would be most helpful. If you could potentially help me test out alpha/beta releases and sanity check Django standards, that would be amazing. I'm not a native python developer, so some of my Django code may not be as expected 😄

I use Django professionally and the Inertia integration in a few hobby projects, I'd be willing to help out!

@BrandonShar
Some thoughts:

"At its core, Inertia is essentially a client-side routing library"

"Inertia has no client-side routing, nor does it require an API. Simply build controllers and page views like you've always done! Inertia works great with any backend framework, but it's fine-tuned for Laravel."

I find the interaction between the Django server, Inertia, Vite and React confusing. I have struggled for hours to understand what is processing and serving what, which didn't help when debugging when I went to setup. I am having to try it out during my evenings so probably a bit tired and dumb but in terms of helping the unitiated, perhaps a diagram would help here

I think an opinionated hello-world quick setup is super valuable to on-ramp a new user and let them break it to learn quickly (something like a Django-Breeze)

A diagram like this helps

@sopelj Thanks for the reply! Lots of experience with Django is exactly what would be most helpful. If you could potentially help me test out alpha/beta releases and sanity check Django standards, that would be amazing. I'm not a native python developer, so some of my Django code may not be as expected 😄

Definitely, I'd love to. Just let me know if you have some branches to check or if you want me to check the repo in general. If it's in general, I could open some issues or maybe start some discussions for suggestions (which I'd be happy to help implement if desired).

I agree that django-breeze does help one get started. It might be nice, although, I don't like how it includes views you can't override. It would be nice if it had class based views that one could easily extend and add themselves. Especially for form views. It would be awesome to have something built-in that one could simply extend. Something like was mentioned in #30
It is also not super intuitive to integrate Django's URL patterns with Inertia. It would be good if we had an example with that too. Especially for localized URLs. I have not yet found a good way of implementing that. Something like django-js-reverse, but I don't think that handles localization.

Hi, I've just started using Inertia and Django, but I have a lot of experience on Python. I'd be happy if I could help you something!

Hi all, I opened a pull request #55 to implement the history encryption feature of inertia v2. Feedback is welcome!

Hey all, I've also just started using inertia, and wanted to use the deferred prop feature in 2.0, I opened a PR #56 to implement this.
Feedback most welcome, especially as this is my first contribution to this project (as well as any other project for quite a few years)!  I'm also happy to help on other areas! I have a reasonable amount of experience with Django and python.

@svengt and @mrfolksy thanks for the PRs!! Both are a huge help to getting us to V2!


make genesis delay configurable

addresses #1547 by making genesis delay configurable with new param MIN_GENESIS_DELAY. This replaces the static SECONDS_PER_DAY

CC: @paulhauner

LGTM, thank you!


feat(cloud): Add volume import partial checks

Prerequisite checklist

[ ] Read the contribution guidelines regarding submitting new changes to the project;
[ ] Tested your changes against relevant architectures and platforms;
[ ] Ran make fmt on your commit series before opening this PR;
[ ] Updated relevant documentation.

Description of changes

Merging this PR is dependent on merging the counterpart from @smoga on volume importing.
It is also dependent on removing feat(cloud): Introduce debug code after testing of course.
It is also dependent on adding support for prompts in processes.

Can you move kraftkit.sh/internal/cpio into kraftkit.sh/cpio. Since we plan on maintaining this package there is no need to prevent its use externally.


Re-Designing Minimum Rating section

What problem is this feature trying to solve?
it enhances the aesthetic appearances to the users

Assign this issue under GSSOC


Deployment and monitoring setup

As a BR mantainer, I want a smooth experience (status, ci/cd)

[x] setup github actions
[ ] define infra/tools
[ ] setup local stack
[ ] deploy the app
[ ] add deployment withing the github actions
[ ] setup some monitoring/logging tool

Old and ambiguous


Unexpected behavior in default configuration

Hi,
I was experiencing a tricky issue in one of my projects, where sometimes we were receiving messages that apparently came from a certain user, when they not. After digging into it, we found that it has to do with intercom-rails' default configuration:
# == Current user method/variable
# The method/variable that contains the logged in user in your controllers.
# If it is `current_user` or `@user`, then you can ignore this
#
# config.user.current = Proc.new { current_user }

Well, we shouldn't have ignored that. We have some pages where, for unlogged users, we set the variable @user (a public view for /users/1, for example). In that case, any unlogged user will result in Intercom believing that there is a logged user (@user, the user being viewed), and messages will be sent appearing to come from him of her. That appears to me to be quite a common case scenario.
I think that is extremely unexpected. I suggest that you either you remove the default and force that option to be set, or remove @user from the default. Or, at the very least, set up a clearer message and warning.
Thanks!

Same here. Users are receiving wrong messages in users/:id. I think '@user' is not a good choice as default user for Intercom.

Hi dgilperez,
Yes, I can see how this can be confusing. We have since updated the troubleshooting section on the Readme page in relation to the default configuration. It is also near the top of the Readme page now. Not sure it was there previously when you encountered this issue. We feel that making sure it is visible on the Readme page is the best way to alert people to this default setting.
Thanks for the feedback. We are also trialing a developer forum where you can discuss issues like this with other developers. You can find this here. It might be a good way to discuss these issues with other people using the Intercom Rails Plugin. Otherwise feel free to open another issue if you are still having issues with this.
Thanks
Cathal


Support DateTimeOffset

Related #29

MessagePack can only have UTC in the timestamp. There is no specification for storing as local time. On the other hand, MessagePack for C# serializes DateTimeOffset, which is stored as local time.
example
2022-09-17T18:27:56.520+09:00 means local time + offset.
The MessagePack specification only accepts UTC for timestamp. Therefore, we expect it to be saved in the following format.
expect : ["2022-09-17T09:27:56.52Z", 540]
actual  : ["2022-09-17T18:27:56.52Z", 540]


[Enhancement] add spilling capability for multi_cast_local_exchange operator

Why I'm doing:
When CTEs in a query are reused, the same data is sent to multiple downstream through the MultiCastLocalExchange operator. In the current implementation, all unconsumed data is cached in memory, depending on the gap between the fastest and slowest consumers, resulting in uncontrollable memory usage.
In this scenario, we cannot control memory by restricting the producer's writes, as there may be dependencies between downstream CTEs, such as when the hash join build side and probe side appear simultaneously, the probe side needs to wait for the build side to complete. If restrictions are imposed on the write side, it will cause queries to be stuck forever due to mutual waiting.
What I'm doing:
In this PR, I introduced a new implementation of MultiCastLocalExchanger called SpillableMultiCastLocalExchanger that can control the memory usage of operators by spilling data to disk.
SpillableMultiCastLocalExchanger is implemented based on MemLimitedChunkQueue.
MemLimitedChunkQueue is an MPMC queue that accepts multiple producers writing data from different threads and supports multiple consumers consuming the same data, similar to a message queue like Kafka. It controls memory usage by spilling data to disk, while also considering the efficiency of spilling io. as we know, too many small io can seriously affect performance.
MemLimitedChunkQueue organizes data internally in the form of a block linked list. The nodes in a linked list are called Block, which contain multiple Cells, each Cell contains a Chunk.
Every time chunk is pushed, a Cell is created and added to the Block at the end of the linked list. When the size of the Block exceeds a certain limit, a new Block is generated and added to the end of the linked list.
Block is the smallest unit handling by spill io task. when writing, if the data in memory exceeds a certain size, a flush io task will be submitted to flush the oldest block to the disk.
when consumers consume data and find that the block they want to read is not in memory, they will submit a load io task to load the corresponding block back into memory.
Through this approach, we can ensure that both producers and consumers can function properly while controlling memory usage.
Test
I constructed a query based on the tpch 100g dataset for testing.
set pipeline_dop=8;
select l_shipdate,count(distinct l_orderkey),count(distinct l_linenumber),count(distinct l_partkey),count(distinct l_suppkey),count(distinct l_quantity),count(distinct l_extendedprice),count(distinct l_discount),count(distinct l_tax),count(distinct l_returnflag),count(distinct l_linestatus) from lineitem group by l_shipdate;

baseline doesn't change other session variables.
for testing, only enable force spill on multi_cast_local_exchange operator.
set enable_spill=true;
set spill_mode='force';
set spillable_operator_mask=32;

here is some metrics from query profile
MULTI_CAST_LOCAL_EXCHANG_SINK
baseline
          UniqueMetrics:
             - ExchangerPeakBufferRowSize: 551.312M (551311886)
             - ExchangerPeakMemoryUsage: 31.848 GB

with spillable_multi_cast_local_exchange
          UniqueMetrics:
             - ExchangerPeakBufferRowSize: 3.473M (3473408)
             - ExchangerPeakMemoryUsage: 205.394 MB
             - FlushIOBytes: 16.275 GB
             - FlushIOCount: 4.079K (4079)
             - FlushIOTime: 18s58ms
             - ReadIOBytes: 16.036 GB
             - ReadIOCount: 3.982K (3982)
             - ReadIOTime: 10s871ms

QueryPeakMemoryUsage and QueryTime
baseline: 78.354 GB, 48s952ms
with spillable_multi_cast_local_exchange:67.408 GB, 1m27s
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

@mergify backport branch-3.3


(doc) (DOCUMENT-541) Make resource type examples pass puppet-lint checks

Currently the code examples at:
https://docs.puppet.com/puppet/latest/reference/type.html
are not all passing a puppet-lint run.
This PR fixes that.

CLA signed by all contributors.

Thanks @roman-mueller! This seems like a good idea :)
Ping @nfagerlund and @hlindberg for visibility.

👍

Since this is a docs-string only PR, I'll go ahead and merge. Since it's going into master, it ought to appear in Puppet 4.5's docs. Thanks!

Ah, wait — I almost forgot about the commit message. @roman-mueller, this repo's maintainers want commit messages to omit the DOCUMENT ticket number. Could you please amend the commit so its message is formatted as (docs) Make resource type examples pass puppet-lint checks? Once you do that, I'll merge.

@nfagerlund done

@nfagerlund for reference, it's not that the (DOCUMENT-xxx) bit needs to be omitted; it's that it needs to start with (doc) (or (docs)). So either of these is fine:

(doc) Make resource type examples pass puppet-lint checks
(doc) (DOCUMENT-541) Make resource type examples pass puppet-lint checks

Don't change anything now, just mentioning for future reference. :)


v5: API commands

The PR re-implement api commands, because of https://github.com/v2fly/v2ray-core/pull/369#issuecomment-725289191:

Removing deprecated proto dependency
Easier to use
Add inbounds, outbounds commands

v2ray api provides tools to manipulate V2Ray via its API.

Usage:

        v2ray api <command> [arguments]

The commands are:

        restartlogger Restart the logger
        stats         Get statistics
        statsquery    Query statistics
        statssys      Get system statistics
        adi           Add inbounds
        ado           Add outbounds
        rmi           Remove inbounds
        rmo           Remove outbounds

Use "v2ray help api <command>" for more information about a command.

Extra
This PR BTW comes with some improvements to commands logic:

Do not build all commands texts, build only the current one
Command column is scalable according to the command length

change of command caused some tests to fail, I can solve these problems today night

I have not idea why tests are failed, and I'm not capable to solve it. Here comes you👍

https://github.com/v2fly/v2ray-core/blob/7acf5152583edabb66a1eca94d8b4d4448d675aa/testing/scenarios/common_regular.go#L23-L31
v2ray run -config=stdin: -format=pb

Do you have an suggest?

@kslr Yes, here is the key:
func RunV2RayProtobuf(config []byte) *exec.Cmd {
	genTestBinaryPath()
	proc := exec.Command(testBinaryPath, "run", "-config=stdin:", "-format=pb")
	proc.Stdin = bytes.NewBuffer(config)
	proc.Stderr = os.Stderr
	proc.Stdout = os.Stdout

	return proc
}

But I don't know why func TestHTTP2(t *testing.T) stuck

I suspect it has something to do with "golint",

Please rebase upon v5, I think test should be okay then.

Please rebase upon v5, I think test should be okay then.

@Loyalsoldier Thanks! But seems that tests are fail randomly, as to my two force pushes, Ubuntu fails the first running but pass the second.

@Loyalsoldier Thanks! But seems that tests are fail randomly, as to my two force pushes, Ubuntu fails the first running but pass the second.

Yeah, that's a problem.

we just need to ensure that the PR test is normal...

Thanks for your work.


Create a list of shorthand, case insensitive metrics and dimensions

It might be a bad idea because then you'd have to replace column names in the result as well and it might be confusing during debugging and data processing. Closed for now


Mark kops-aws as nonblocking job

Build has been broken for 8+ hours now. Let's mark it
as non-blocking to get 1.5 queue unblocked temporarily.
https://k8s-testgrid.appspot.com/google-aws#kops-aws

This change is

/cc @k8s-oncall

I'm all for this.
If @gmarek can confirm this is ok, I'll redeploy the submit-queue with this change.

I was considering this move, but I'm rather against it. Two reasons: 1) it looks like a valid breakage, and we don't want to disable tests when something breaks, 2) we have a number of other problems with submit queue (i.e. per-PR tests have problems with running), so it's not enough to unblock merges.

@gmarek : i am not asking to disable the test, but just mark it as non-blocking. Looks like it was marked blocking after the code freeze? (https://github.com/kubernetes/contrib/pull/2045)

@gmarek I don't think it is a valid breakage.

That's one option. Other one is that we create 3 instead of 4 Nodes.

@dims - it was (mostly) passing until yesterday. I don't know what changed, but I really don't think that unblocking the merge queue is the answer. We can do it when someone responsible for kops test setup wakes up and gives us green light. I don't want to cause more regression that we have now.

ack @gmarek sounds like a good plan

I think that removing this from blocking won't help for merges. We have a super serious issue, that after retest, half of the tests stuck in phases like:

"Waiting for status to be reported"
"Error in queue"
"Error queueing build."
That means, that pretty much nothing is green after retest and won't be merged anyway.

If we don't fix this, we will never merge anything without "retest-not-required"...

Do we know who is responsible for this test suite?
cc @krzyzacy

I think that @zmerlynn is.

it looks like a valid breakage,

Without logs, it is really hard to determine the validity of a break.  It seem reasonable for blocking jobs to be required to produce logs for their components as noted here: https://github.com/kubernetes/kubernetes/issues/37553 .  If the job doesn't produce apiserver, controller, and kubelet logs on failures, making it a blocking job just means that it blocks and no one can figure out why.

@deads2k - I'm one who'd rather err on the safe side. As for your proposal I completely agree. @kubernetes/test-infra-maintainers

/lgtm

Thanks @zmerlynn let's merge this now and see how to get the submit queue back on its feet and decide when to switch this back

Redeploying the queue now.

@zmerlynn this job has a presubmit (per-PR run), right? Is the presubmit broken, too?

@lavalamp: It should be clear now regardless (c.f. https://github.com/kubernetes/test-infra/issues/1212). I'm working on fixing the logging situation before I make it blocking again.


Fix option names in changelog

(Not sure if the changelog should be updated post-release)

Thanks!


re-opening #261

since it does not work here...

I have reopened #261 and will close this one instead.


Mention embedded etcd as option in main install doc

Happy with the PR. Need @mdeneva to review the style. Also, MD linter failed, so it needs correction. I saw some warnings but doesn't seem to say why it failed.

Thanks, @vfiftyfive, good spot on the linter errors - it was some trailing spaces, I've run markdownlint2-fix to resolve!

+1 from me on this PR.

On a slightly related note - We should definitely discuss about how to present this page in the future as it seems like there is unnecessary duplication for installing Ondat on different versions of Kubernetes (ie 💡 "Ondat supports the five most recent Kubernetes releases, at minimum" should be sufficient and the list of supported versions should fall under a table in > https://docs.ondat.io/docs/prerequisites/)


Tiebreak options do not suffice with nth

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[x] zsh
[ ] fish

Problem / Steps to reproduce
I have a nice fzf script to search through and install Arch Linux packages.
In it, I use --nth so I can see the repo but only search the actual package string.
However, I am unable to define any tiebreak algorithm that puts the best matches first.
Suppose the following scenario:
echo "aur\tdockerize\naur\tsystemd-docker\ncommunity\tdocker\t5.5" | fzf --nth 2

Searching for docker will yield one of the aur packages,
regardless of the tiebreak options.
In my day-to-day usage I encounter basically this,
except that there's lots more irrelevant results.
Workarounds

search for ^docker$
reorder the input so community packages appear first (pretty brittle)

Neither of these is reliable and convenient.
I think the solution would be a --tiebreak=matchlength option, which only takes the length of the match rather than the whole line into account.
And, again, sorting perfect matches first (https://github.com/junegunn/fzf/issues/2285)

I encountered exactly the same issue!
I assumed that --tiebreak=length would already take into account the substring we select with the --nth selector.
Wouldn't this be a possibility as well, to have the length tiebreak work on the --nth substring automatically, as I do not think there wouldn't really be a use-case where you want the total line length, instead of the matching line length.

Actually, there could be a tiebreak called matchlength or similar to handle that case. Just encountered a similar issue again, as I use --tiebreak=index now to sort non-AUR packages always first.
But in this example, the perfect match "context" if very far behind, making me wonder why the algorithm resorted to a tiebreak here at all - you don't need a tiebreak to see that the first match is a lot worse, even with a very generic algorithm. Do we maybe have a regression here?

You might want to try the new --tiebreak=chunk in 0.32.0.


Ability to change the default option for files.autoSave to something else other than afterDelay

Hi there.
When switching between auto-save modes from the file menu, say setting the files.autoSave option to onFocusChange, if you disable the auto-save from the flle menu, then enable it back, the setting files.autoSave defaults to afterDelay. This behaviour happens in both user and workspacesettings.
It would be awesome to have a setting like files.autoSaveDefault where one can specify the auto-save behaviour when switching. Alternatively, if VSCode would 'remember' the previous setting, also that would be an even better option.
Thanks.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Add reply-to tag for distribution lists

Originally created by Dalnix AB on 2013-05-15T11:51:45Z
Distribution lists in modoboa is awesome! Hurray!
Only thing i miss is when i send an email to a list, people answer to me in person instead of to the list.
I would like to have (maybe optional) modoboa add a reply-to header when sent to distrubution lists so that when people hit reply it goes back to the list.

A mailing list server usually sets the "Sender" address of outgoing emails to address of the sending mailing list.

Ebrahim Mohammadi<EMAIL_ADDRESS>

A mailing list server usually sets the "Sender" address of outgoing emails to address of the sending mailing list.

This should be optional as there usually are fierce battles whether it right
[tm] or not to set Reply-to:-headers.
p@rick
--
[*] sys4 AG
https://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

What's the best way to add a header to an outgoing message? Use smtpd_sender_restrictions with a check_sender_access (PREPEND)?
@patrickbenkoetter ?

Careful here: mailing list as per RFC must have the obvious list-post, list-id, list-subscribe,lists unsubscribe and the precedence header, or else the emails will be treated as spam by various spam filters.
Also there are some caveats to take care of, as f.i. dkim signing and dmarc policies ( which if the headers are modified, will break the mailing list)

I think @piwats is right, Modoboa is not a mailing list manager like Mailman. Would it be complicated to build a "simple" plugin for that ? (I mean create a simple ML manager)

You have to handle a lot of stuff for a Mailinglist Tool, I would drop this feature and perhaps implement something like mailman integration ( perhaps take a look how proprietary solutions work here... )


Change windows wmic diskdrive to wmic logicaldisk

I have changed the windows call 'wmic diskdrive' to use 'logicaldisk' as it is more useful returning DeviceID 'C:' instead of '\\.\PHYSICALDRIVE0'. Also removed build directory as it is auto-generated.
Right now if you want to read a file from a USB using nodejs you will need to pass the logical volume name for windows:
var fs = require('fs');
var filename = "D:\\file.json";
fs.readFile(filename, function(err, data) {
    if (err) throw err;
    console.log(data);
  });

If drive list returns in windows:
[ { device: 'C:', description: 'Windows 8.1', size: '661 GB' },
  { device: 'D:', description: 'USB1', size: '15 GB' } ]

instead of:
{
 device: '\\\\.\\PHYSICALDRIVE0',
 description: 'WDC WD10JPVX-75JC3T0',
 size: '661 GB'
},

We will be able to identify and read/write files from mounted devices.

The two are actually different use cases, this is an example from my machine:
>wmic diskdrive get DeviceID, Caption, Size
Caption                       DeviceID            Size
SAMSUNG SSD PM810 2.5" 7      \\.\PHYSICALDRIVE0<PHONE_NUMBER>00
JMCR SD/MMC SCSI Disk Device  \\.\PHYSICALDRIVE1<PHONE_NUMBER>0

and
>wmic logicaldisk get DeviceID, Size, VolumeName
DeviceID  Size          VolumeName
C:<PHONE_NUMBER>12  OS
D:

diskdrive lists all my disks, including my unmounted sd card, meaning it is possible to address and write to it directly at the disk level (eg for burning images).
logicaldisk however does not show it (due to it being unmounted and hence not having a disk letter), it does however show my (empty) optical drive, which would allow accessing mounted drives on a filesystem level (eg in order to read a file)
What I would say is that these should be different methods, as both have their uses, rather than one being strictly better than the other

I agree, better split up to keep both functionalities.

The benefit of drivelist is that the exact same interface is implemented for all major operating systems. Adding a new function specifically for Windows will break this benefit, and from a user standpoint, I have to manually check if I'm running Windows before calling this particular function.
@acabelloj I suggest that you create another module that lists logical drives (since the use case is different), or you create a module that takes drivelist output as an input, and translates physical drive ids to logical names.

Thanks @jviotti, I think I'm opting for forking the module as translating the physical drive ids is going to be harder.

@acabelloj Sounds great, let us know how it goes. Good luck! :+1:


Testing angular application using protractor and Jasmine

Added an index file that contains the tutorial text in markdown format. Also attached is an image linked to the hero image used in the tutorial text.

@Eze4Manuel could you create a new PR that has the required form. I will be closing this one. Thanks


Ability to vacuum database

Description
Ability to vacuum database
Type of change

New feature (non-breaking change which adds functionality)
Documentation update

Testing steps
Can be tested locally.
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report

Merging #146 (07acc0e) into master (d426a1f) will decrease coverage by 0.60%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #146      +/-   ##
==========================================
- Coverage   18.45%   17.84%   -0.61%
==========================================
  Files           3        3
  Lines         439      454      +15
==========================================
  Hits           81       81
- Misses        347      362      +15
  Partials       11       11

Impacted Files
Coverage Δ

cleaner.go
0.00% <0.00%> (ø)

storage.go
19.38% <0.00%> (-0.71%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d426a1f...07acc0e. Read the comment docs.


⚠ Bofrost.de has degraded performance

In 6534686, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1184 ms

Resolved: Bofrost.de performance has improved in 0368004.


Prompts to upgrade from 2.50.0 to 2.51.0, then fails to upgrade (MacOS)

Describe the bug
Running az upgrade on a 2.50.0 install of azure-cli on MacOS results in following:

az upgrade
This command is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus

Your current Azure CLI version is 2.50.0. Latest version available is 2.51.0.
Please check the release notes first: https://docs.microsoft.com/cli/azure/release-notes-azure-cli
Do you want to continue? (Y/n):
Updated 1 tap (homebrew/cask-fonts).
Warning: azure-cli 2.50.0_1 already installed
CLI upgrade failed or aborted.
In an effort to resolve this, I've completely uninstalled the azure-cli, deleted the ~/.azure directory, and reinstalled az using homebrew as prescribed here: https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-macos
Same results.
NOTE: This is a significant problem because because it affects scripting. As an example: I have creation/configuration scripts I use, and I have several upcoming sessions at a partner conference showcasing Azure Spring Apps etc. Those scripts fail at key points due to the prompt inserting itself into the results (e.g. --query queries assigning values to env vars). This would seem to indicate that customer's production scripts could also be affected, at least in certain circumstances.
Related command
az upgrade
Errors
Warning: azure-cli 2.50.0_1 already installed
CLI upgrade failed or aborted.
Issue script & Debug output
az upgrade
Expected behavior
It should upgrade to the current version as indicated in the prompt it provides when running az commands:
Your current Azure CLI version is 2.50.0. Latest version available is 2.51.0.
Environment Summary

az --version                                                             2 ↵

azure-cli                         2.50.0 *
core                              2.50.0 *
telemetry                          1.0.8 *
Dependencies:
msal                              1.22.0
azure-mgmt-resource             23.1.0b2
Python location '/usr/local/Cellar/azure-cli/2.50.0_1/libexec/bin/python'
Extensions directory '/Users/markheckler/.azure/cliextensions'
Python (Darwin) 3.10.12 (main, Jun 20 2023, 17:00:24) [Clang 14.0.3 (clang-14<IP_ADDRESS>.1)]
Legal docs and information: aka.ms/AzureCliLegal
You have 3 update(s) available. Consider updating your CLI installation with 'az upgrade'
Additional context
No response

Thank you for opening this issue, we will look into it.

Thank you @yonzhan, please let me know how I can help, happy to do so.

@mkheck - having the same issue on my Mac.

2.51 is not available on homebrew, see https://github.com/Azure/azure-cli/issues/27047
Please disable autoupgrade az config set auto-upgrade.enable=no
Duplicate of https://github.com/Azure/azure-cli/issues/27091

Hi @bebound, that stops the "forced" upgrade but this message still applies with every command executed:
You have 3 update(s) available. Consider updating your CLI installation with 'az upgrade'
Still, progress. 👍

I disabled all updates for now. az config set auto-upgrade.all=no

I was able to successfully upgrade it on my Mac using pip –
pip3 install azure-cli==2.51.0
% az --version
azure-cli                         2.51.0

core                              2.51.0
telemetry                          1.1.0

Dependencies:
msal                            1.24.0b1
azure-mgmt-resource             23.1.0b2

Python location<EMAIL_ADDRESS>Extensions directory '/Users/hiteshashar/.azure/cliextensions'

Python (Darwin) 3.11.5 (main, Aug 24 2023, 15:09:45) [Clang 14.0.3 (clang-14<IP_ADDRESS>.1)]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

Close as 2.52.0 is available in Homebrew.


Complex queries

One thing I missed the most was to filter a collection based on more than one field and also the ability to limit the fields returned. This pull request takes care of that!
Here is how the collection page looks like now (before entering a query):

Here is a screenshot with a query and the fields entered (along w/ the corresponding result):

If you have any suggestions do post them here. I am still looking in to whether I am missing anything else!

As a side note, the "Simple" tab has the form which was available before, I didn't modify any of that!


upgrade gopkg.in/yaml.v2 -> v3

Updates yaml.v2 -> yaml.v3.
See https://github.com/go-yaml/yaml/issues/602 for details on the UnmarshalStrict change.

@golanglemonade Thanks!!!!!!


cleanup some unnecessary #if os

Motivation:
Certain #if os uses in SwiftNIO are unnecessary, they should be
removed.
Modifications:
Removed unnecessary #if os in SwiftNIO.
Result:
Nicer codebase.

@swift-nio-bot test this please

@swift-nio-bot test this please


Doc improvements request.

In the first note where it talks about using a versionless Key Vault secret for the APGw to always call newer cert's version, please clarify how long APGw takes to recognize/use the updated version?
In the section for "KeyVaultHasRestrictedAccess" why is it that you ask to add APGw Vnet and subnet + having trusted services option marked as yes? You should not need to whitelist the Vnet and subnet, Trusted services should be enough, please test.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e50c4505-22be-a16b-0812-ca9f371c58cf
Version Independent ID: 31f2d260-f1d0-c76b-d3d4-f00b0aedeb42
Content: Common key vault errors in Application Gateway - Azure Application Gateway
Content Source: articles/application-gateway/application-gateway-key-vault-common-errors.md
Service: application-gateway
GitHub Login: @jaesoni
Microsoft Alias: jaysoni

@FabianGonzalez-MSFT Thanks for the feedback! We are currently investigating and will update you shortly.

@fabiangonzalez-msft @BryanTrach-MSFT the refresh intraval is 4 hours to pull from keyvault.  We havemore details outlined here: https://docs.microsoft.com/en-us/azure/application-gateway/key-vault-certs#supported-certificates
Regarding access to key vault, both the service endpoint and the Allow trusted service box must be checked.  Both items are used hand-in-hand when using the user managed identity to authenticate to key vault.  I've updated the docs to be a bit more clear on this: https://docs.microsoft.com/en-us/azure/application-gateway/key-vault-certs#configure-your-key-vault
Hope this helps!
Jack
#please-close