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

--accept says "invalid digit found in string" for documentation example #1329

Closed
koppor opened this issue Jan 3, 2024 · 2 comments
Closed

Comments

@koppor
Copy link

koppor commented Jan 3, 2024

The documentation says:

Use "lychee --accept '200..=204, 429, 500' ..." to provide a comma-separated list [...]

Use "lychee --accept '200..=204, 429, 500' <inputs>..." to provide a comma-

When executing that, I get "invalid digit found in string"

>lychee --accept '200..=204, 429, 500'
error: invalid value ''200..=204,' for '--accept <ACCEPT>': invalid digit found in string
lychee 0.13.0

I tried some variants:

  • Does not work: lychee --accept '200' https://www.example.org
  • Works: lychee --accept "200" https://www.example.org
  • Does not work: lychee --accept "200..=204" https://www.example.org

Last working lychee version was 0.10.0. Beginning with 0.10.1 the aforementioned syntax does not work.


Maybe, "just" a new release has to be made, because it seems PR #1167 is not release. I cannot build a binary for myself, because of microsoft/vcpkg#35949 (comment).

@koppor koppor changed the title --accept says "invalid digit found in string" for documentaiton example --accept says "invalid digit found in string" for documentation example Jan 3, 2024
@mre
Copy link
Member

mre commented Jan 4, 2024

Maybe, "just" a new release has to be made

Yes, I think so. There will be a new release tomorrow.

@mre
Copy link
Member

mre commented Jan 5, 2024

lychee version 0.14.0 finally got released. 🎉
Thanks to this release, the issue should be resolved now.
Please reopen if this is not the case and apologies for the long delay.

On top of that, the error message for TOML parsing errors is more extensive now, which should help with troubleshooting.

@mre mre closed this as completed Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants