Skip to content

fix: tokio reactor issue for reqwest - #1

Open
edfloreshz wants to merge 1 commit into
mainfrom
fix/tokio-reactor
Open

fix: tokio reactor issue for reqwest#1
edfloreshz wants to merge 1 commit into
mainfrom
fix/tokio-reactor

Conversation

@edfloreshz

Copy link
Copy Markdown
Contributor

This PR fixes the HTTP client to use the correct Tokio runtime context, resolving reactor-related errors when making asynchronous requests. It ensures the underlying client and request execution are properly integrated with Tokio.

thread 'download-manager' (12455) panicked at /home/eduardo/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/reqwest-0.12.24/src/async_impl/body.rs:355:33:
there is no reactor running, must be called from the context of a Tokio 1.x runtime

@edfloreshz edfloreshz self-assigned this Aug 18, 2026
@edfloreshz edfloreshz added the bug Something isn't working label Aug 18, 2026
@cyberphantom52

Copy link
Copy Markdown
Member

reqwest_body_reads_without_a_tokio_reactor test seems to pass even on origin/main. What are we trying to fix?

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