Update Elastic.Transport to 0.15.0

[flobernd]

As titled.

[github-actions]

💚 All backports created successfully

Status	Branch	Result
✅	8.19
✅	9.3

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

[TheFireCookie]

Hi, I don't know if it's the correct space to write a comment, maybe you prefer an issue? But I have some weird connections errors since I pulled 8.19.15 and I guess it's related since when I downgrade to 8.19.14 it's fine again.

Elastic.Transport.PipelineException: Failed sniffing cluster state.\\n ---\\u003E Elastic.Transport.PipelineException: An error occurred trying to read the response from the specified node.\\n at Elastic.Transport.RequestPipeline.SniffCoreAsync(Boolean isAsync, Auditor auditor, CancellationToken cancellationToken)\\n --- End of inner exception stack trace ---\\n at Elastic.Transport.RequestPipeline.SniffCoreAsync(Boolean isAsync, Auditor auditor, CancellationToken cancellationToken)\\n at Elastic.Transport.RequestPipeline.FirstPoolUsageAsync(SemaphoreSlim semaphore, Auditor auditor, CancellationToken cancellationToken)\\n at Elastic.Transport.DistributedTransport\\u00601.RequestCoreAsync[TResponse](Boolean isAsync, EndpointPath path, PostData data, Action\\u00601 configureActivity, IRequestConfiguration localConfiguration, CancellationToken cancellationToken)\\n at Elastic.Clients.Elasticsearch.ElasticsearchClient.\\u003C\\u003Ec__DisplayClass718_0\\u00603.\\u003C\\u003CDoRequestCoreAsync\\u003Eg__SendRequestWithProductCheckCore|2\\u003Ed.MoveNext()\\n--- End of stack trace from previous location ---\\n at Elastic.Clients.Elasticsearch.ElasticsearchClient.\\u003C\\u003Ec__DisplayClass718_0\\u00603.\\u003C\\u003CDoRequestCoreAsync\\u003Eg__SendRequestWithProductCheck|1\\u003Ed.MoveNext()\\n--- End of stack trace from previous location ---\\n

[flobernd]

Hi @TheFireCookie thanks for reporting! We'll have a look.

[flobernd]

@TheFireCookie I created an issue in the transport repository. Is there anything special with your setup? It would be super useful if you could catch the exception (please also enable DebugMode) and provide the contents of the TransportException properties like AuditTrail, ApiCallDetails, etc.

(exception.DebugInformation contains a human readable string that combines all of the interesting values; we might need this information for the outer- and the first inner-exception)

[TheFireCookie]

I've added the debug info in the other ticket @flobernd , is that enough now? :)

[flobernd]

Thanks a lot @TheFireCookie 🙂