Skip to content

Update Elastic.Transport to 0.15.0#8830

Merged
flobernd merged 1 commit intomainfrom
update-transport-0.15.0
Feb 27, 2026
Merged

Update Elastic.Transport to 0.15.0#8830
flobernd merged 1 commit intomainfrom
update-transport-0.15.0

Conversation

@flobernd
Copy link
Member

As titled.

@flobernd flobernd merged commit 33b5019 into main Feb 27, 2026
29 of 30 checks passed
@flobernd flobernd deleted the update-transport-0.15.0 branch February 27, 2026 10:02
github-actions bot pushed a commit that referenced this pull request Feb 27, 2026
(cherry picked from commit 33b5019)
github-actions bot pushed a commit that referenced this pull request Feb 27, 2026
(cherry picked from commit 33b5019)
@github-actions
Copy link
Contributor

💚 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
Copy link
Contributor

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
Copy link
Member Author

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

@flobernd
Copy link
Member Author

flobernd commented Mar 11, 2026

@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
Copy link
Contributor

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

@flobernd
Copy link
Member Author

Thanks a lot @TheFireCookie 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants