-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Toikio runtime error #4
Comments
I am also seeing this issue, but I was able to reproduce the issue in my local (non-CI) environment, so I've opened lycheeverse/lychee#131. |
Thanks. We migrated to tokio 1.0 in 0.5.0. That's where the issue is coming from. Apparently one of our deps is still using an older version of tokio that is incompatible. Investigating. |
As mentioned in lycheeverse/lychee#131, the reason most likely https://github.com/reacherhq/check-if-email-exists. The issue is fixed in the |
We decided to merge in the changes to lychee-master, which means that the Github action should now be working as expected. As soon as upstream merges in the changes, we'll do another release. Gonna close this as the problem should be resolved. Please reopen if this is not the case. 😃 Thanks for reporting. |
Hi @mre, sorry for the delay in getting back on this. I'm currently using this action with https://github.com/nektos/act locally for testing and still seeing the issue with v1.0.6 of this action. |
That's sad to hear; reopened. |
It could be that there's still a crate that is using a version of tokio older than 1.x. Any chance you can dump the versions of the dependencies? |
The plot thickens for me at the moment - running
https://github.com/reacherhq/check-if-email-exists/blob/master/core/Cargo.toml notes the dependency on |
Managed to run a |
Thanks so much for the feedback. |
FYI, I'm unable to reproduce this issue anymore (locally or in CI environment). |
Great! Thanks for the feedback. Closing. 🙌 |
Very promising utility! Thank you :)
We are trying to set this up in our CI, but hitting a tokio runtime error. Here is a trace produced with
RUST_BAKCTRACKE=full
:In case it's to do with the source being parsed, the relevent section of HTML looks like this:
(Unless it is trying to parse out of a code block, which I don't think it is).
I can report that running
lychee 0.4.1
locally on the same content does not produce this problem.For reference, here is a failing pipeline: https://github.com/informalsystems/apalache/runs/1670165829?check_suite_focus=true#logs
The text was updated successfully, but these errors were encountered: