-
Notifications
You must be signed in to change notification settings - Fork 215
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
fix: make vectorizer worker robust #263
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm!
cd80284
to
4e16374
Compare
These fixes were mostly done in the context of usability with docker compose. Includes the following changes: - Handle being killed with SIGINT or SIGTERM - Handle being unable to connect to the target DB - Handle arbitrary failures in the core of vectorizer worker - Add `--exit-on-error` parameter to force vectorizer worker to exit on error. `--once` implies `--exit-on-error`.
4e16374
to
b4377c8
Compare
projects/pgai/pgai/cli.py
Outdated
) | ||
sys.exit(1) | ||
else: | ||
log.warn( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why warn instead of err? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good question. "upgraded" to error.
af0cd66
to
75b51cd
Compare
75b51cd
to
a76a56f
Compare
These fixes were mostly done in the context of usability with docker compose. Includes the following changes:
--exit-on-error
parameter to force vectorizer worker to exit on error.--once
implies--exit-on-error
.