-
-
Notifications
You must be signed in to change notification settings - Fork 142
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
Error: thread 'tokio-runtime-worker' panicked at 'not currently running on the Tokio runtime.' #131
Comments
Don't have much time to look into this right away, but maybe I can note down some pointers for investigation. Could be related to rust-lang/cargo#7169 and https://users.rust-lang.org/t/problem-tokyo-0-3-thread-main-panicked-at-not-currently-running-on-the-tokio-runtime-solved/50336/6. Perhaps a combination of it. How did you install lychee? You could try with |
I will try that. I installed it with the Homebrew formula I drafted (#59 (comment)). Homebrew's default for install Rust packages does include the I will reinstall via |
Reproduced what appears to be the same error after installing with
|
Don't have much time to look into this right away, but maybe I can note down some pointers for investigation. Could be related to rust-lang/cargo#7169 and https://users.rust-lang.org/t/problem-tokyo-0-3-thread-main-panicked-at-not-currently-running-on-the-tokio-runtime-solved/50336/6. Perhaps a combination of it. How did you install lychee? You could try with |
This is weird because the stacktrace comes from Tokio 0.2.x, while we have 1.x. It would be good to oust the old version. I have analyzed the dependencies and it seems that the only lib using old There's an open PR to bump the reqwest version on that lib's repo which should get us rid of Tokio 0.2.x: reacherhq/check-if-email-exists#829 |
Good shot. In the hope of solving the problem I sent a PR: reacherhq/check-if-email-exists#869. 🤞 |
New release is currently blocked on async-email/async-smtp#36. Without that we can't bump the version of check-if-email-exists (because async-smtp is a dependency) and that means we cannot publish a new version of lychee. (git repos are not allowed as dependencies for binaries published on crates.io.) That said, we could create a lychee development branch for now and use that as the source for the lychee action. 🤔 If that's worth the effort largely depends on how long it takes until the upstream changes are merged. |
The lastest
As soon as the upstream version gets released we'll switch back to crates.io and make a new release ourselves. |
Gonna go ahead and close this. Should be fixed in |
I encountered this panic initially in GitHub Actions (someone else has ran into this and has filed lycheeverse/lychee-action#4), but I have been able to reproduce this error in my local environment myself (lychee 0.5.0), so I'm opening this issue here.
Here is the backtrace:
(This particular trace repeats over and over again, presumably once per problematic link check attempt.)
Lychee was built with Rust 1.49.0 and is running on macOS 11.1 Big Sur (Intel). I was using a
GITHUB_TOKEN
. Please let me know if you need any further information about my environment, etc.The text was updated successfully, but these errors were encountered: