-
Notifications
You must be signed in to change notification settings - Fork 415
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
Improve services logging and status #2436
Conversation
Important Auto Review SkippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the To trigger a single review, invoke the WalkthroughThe recent modifications introduce a decorator to manage service status transitions efficiently, incorporating exception handling for robust operation. This enhancement primarily targets the Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
Quickstart template updates in |
@coderabbitai review |
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.
Review Status
Actionable comments generated: 2
Configuration used: .coderabbit.yaml
Files selected for processing (1)
- src/zenml/services/service.py (5 hunks)
Additional comments: 2
src/zenml/services/service.py (2)
- 288-309: The exception handling in the
update_status
method is correctly implemented, ensuring that any errors during status checks are logged and the service status is updated accordingly. This enhances the robustness of the service status management.- 436-439: The application of the
update_service_status
decorator on thestart
method with appropriatepre_status
andpost_status
values effectively manages the service status transitions during the start process.
…zenml-io/zenml into feature/OSSK-390-pre-cleaning-deployers
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. Please update the description of this ticket with something for whoever is making the next release.
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.
Left a few minor comments. Otherwise LGTM.
|
||
if self.endpoint: | ||
self.endpoint.update_status() | ||
if self.endpoint: |
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.
Just out of curiosity, if the status of the service is inactive, should we also update the status of the endpoint as well? The same goes for the except
block.
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.
I think for the current service implementation we don't do that since we don't look for service endpoint directly. but with the new update services we might wanna do that
@safoinme , based on what I see in the error log of the E2E template check - you need to update from develop. This is an issue with the s3fs version, yesterday Baris reported the same. |
* update service error catching * Update service status decorator * Refactor status update logic in BaseService * Auto-update of Starter template * Add logging statements to service.py * Fix typo in update_status method --------- Co-authored-by: GitHub Actions <actions@github.com> Co-authored-by: Alex Strick van Linschoten <strickvl@users.noreply.github.com>
Describe changes
Pre-requisites
Please ensure you have done the following:
develop
and the open PR is targetingdevelop
. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.Types of changes
Summary by CodeRabbit