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

Enable the user change the setup of the cluster check process #836

Merged
merged 1 commit into from
May 28, 2024

Conversation

BelSasha
Copy link
Contributor

No description provided.

Copy link

sentry-io bot commented May 26, 2024

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: runhouse/servers/cluster_servlet.py

Function Unhandled Issue
update_autostop ModuleNotFoundError: No module named 'sky' runhou...
Event Count: 3
update_autostop TypeError: a bytes-like object is required, not 'NoneType' runhouse.servers.cluster_servlet in updat...
Event Count: 3

Did you find this useful? React with a 👍 or 👎

Copy link
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @BelSasha and the rest of your teammates on Graphite Graphite

@BelSasha BelSasha requested a review from jlewitt1 May 26, 2024 13:19
@@ -1645,3 +1658,44 @@ def _check_for_child_configs(cls, config: dict):
config["default_env"] = default_env

return config

def _is_den_authed_and_saved_to_den(self, change_type: str):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wondering if this check is necessary, is there any harm in just updating the config with the interval field regardless if status check is explicitly enabled or disabled?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jlewitt1 Removed the check if the cluster is saved into den. If it is not, the post request will raise an error, which we catch and send an error log, explaining that the cluster is not saved and therefore we can't post its status.

If left the check of den_auth == True because:

  1. It is not pinging den, therefore it is a "cheap" check
  2. I think it is in our interests to clarify to the user that this is a feature requires Den auth / Den user. wdyt?

if interval_size == -1:
if is_config_updated:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we should add a log here anytime the config is updated, not just when its turned off

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jlewitt1 This log is added as part of aupdate_status_check_interval_in_cluster_config method

@BelSasha BelSasha force-pushed the sb/enbale-or-disable-status-polling branch from 8f27a55 to 66095b0 Compare May 27, 2024 13:07
@BelSasha BelSasha requested a review from jlewitt1 May 27, 2024 14:57
@BelSasha BelSasha force-pushed the sb/enbale-or-disable-status-polling branch from 66095b0 to 91d0286 Compare May 28, 2024 06:36
@BelSasha BelSasha requested a review from jlewitt1 May 28, 2024 06:36
"""
Stopping consecutively sending status to Den.
"""
if not self.den_auth:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what happens if i have a cluster with den auth enabled, then i decide to disable it. Will the status check still continue in this case?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jlewitt1 yeah good point, I updated the logic so the status check will stop in that case.

@BelSasha BelSasha force-pushed the sb/enbale-or-disable-status-polling branch from 91d0286 to 0903dca Compare May 28, 2024 11:58
@BelSasha BelSasha requested a review from jlewitt1 May 28, 2024 11:58
@BelSasha BelSasha merged commit 79d6215 into main May 28, 2024
11 checks passed
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.

None yet

2 participants