Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Must use blocking client now #220

Merged
merged 1 commit into from
Feb 26, 2025
Merged

Conversation

masongup-mdsol
Copy link
Contributor

I was getting in my local and deployed testing:

thread 'OpenTelemetry.Traces.BatchProcessor' panicked at /rustc/4d91de4e48198da2e33413efdcd9cd2cc0c46688/library/core/src/ops/function.rs:250:5:
there is no reactor running, must be called from the context of a Tokio 1.x runtime

Checking some searches and other Github discussions, I found this bug which linked this doc section. It seems only the blocking reqwest client is supported by otlp now. This seems to fix it on my local.

@davidB davidB self-assigned this Feb 26, 2025
@davidB davidB added the bug Something isn't working label Feb 26, 2025
@davidB davidB removed their assignment Feb 26, 2025
@davidB davidB merged commit a18b5ca into davidB:main Feb 26, 2025
2 checks passed
@github-actions github-actions bot mentioned this pull request Feb 26, 2025
@masongup-mdsol masongup-mdsol deleted the fix-otlp-reqwest-type branch February 26, 2025 15:41
@github-actions github-actions bot mentioned this pull request Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants