-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
--skip and --fail options for handling HTTP 4xx and 4xx errors #102
Comments
This should probably be accompanied by an option that causes the entire script to quit with an error status code (such that CI will fail) if a 4xx or 5xx is encountered. |
Asked ChatGPT:
It came up with some bad options, so I asked:
Got back:
I'm going to go with |
I'm going to add Should I add them to I'm leaning towards "yes", because each of those commands might be used like so:
And people may want to overwrite |
Demo:
|
More demos:
|
The script that updates https://simonw.github.io/datasette-screenshots/ has a problem: occasionally it takes a screenshot that looks like this:
I don't want to manually check the shots every time I the GitHub Actions runs, so I'd like to have an option for
shot-scraper multi
that can spot if a page comes back with a non-200 error and logs a warning but keeps going.That way any failures in that repo at least won't over-write a good screenshot.
The text was updated successfully, but these errors were encountered: