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

bug in searching for alternatives #1501

Closed
phanirithvij opened this issue Sep 16, 2024 · 4 comments · Fixed by #1526
Closed

bug in searching for alternatives #1501

phanirithvij opened this issue Sep 16, 2024 · 4 comments · Fixed by #1526
Labels
bug Something isn't working

Comments

@phanirithvij
Copy link

phanirithvij commented Sep 16, 2024

This has been running for 10mins

lychee -E  --cache --scheme http --scheme https --include-verbatim --timeout 5 --suggest
  1659/1659 ━━━━━━━━━━━━━━━━━━━━ Finished extracting links
⠂ 14/15 ━━━━━━━━━━━━━━━━━━ ━ Searching for alternatives   

Can the --timeout flag be used for archive checking step as well?

@mre
Copy link
Member

mre commented Sep 16, 2024

Great idea. @thomas-zahner fyi

In general, archive.org is super slow quite often at least for me. We could support alternatives, but I'm not aware of any.

@thomas-zahner
Copy link
Member

Yes, I totally agree that the timeout value should be respected by the archive lookup step.
@mre there aren't many alternatives. archive.today is maybe the only one. There is also the Time Travel Service which sounds interesting.

@mre
Copy link
Member

mre commented Sep 20, 2024

I'm all for it. Guess we could pass the timeout already. Anyone up for fixing it with a PR?

@mre mre added the bug Something isn't working label Sep 21, 2024
@mre mre closed this as completed in #1526 Oct 12, 2024
@mre
Copy link
Member

mre commented Oct 12, 2024

Fixed by @thomas-zahner and will be released with the next version 0.6.2.

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 a pull request may close this issue.

3 participants