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

Don't base command exit code on wpull's exit code #87

Merged
merged 1 commit into from
Nov 6, 2023
Merged

Conversation

chosak
Copy link
Member

@chosak chosak commented Nov 6, 2023

Currently the crawl management command always returns a zero exit code even if wpull has some kind of serious error. By default wpull returns a non-zero exit code for any failure, which is too sensitive - we don't want downstream processing to fail just because the crawler can't resolve the DNS of a link, for example.

This change reintroduces the wpull exit status codes but only for errors that don't relate to network failures (DNS, connectivity, etc).

Currently the crawl management command always returns a zero exit code
even if wpull has some kind of serious error. By default wpull returns
a non-zero exit code for *any* failure, which is too sensitive - we
don't want downstream processing to fail just because the crawler
can't resolve the DNS of a link, for example.

This change reintroduces the wpull exit status codes but only for
errors that don't relate to network failures (DNS, connectivity, etc).
@chosak chosak merged commit 029a584 into main Nov 6, 2023
4 checks passed
@chosak chosak deleted the fix/exit-code branch November 6, 2023 21:50
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

Successfully merging this pull request may close these issues.

1 participant