-
Notifications
You must be signed in to change notification settings - Fork 39
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
modify cluster status checks tests #1197
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
5928f9e
to
9e540f6
Compare
9e540f6
to
0bb4d36
Compare
a1e13a8
to
da456c2
Compare
717583b
to
2a92617
Compare
da456c2
to
4fb129a
Compare
45e2b88
to
dfc559c
Compare
07f29ea
to
2e55a66
Compare
2e55a66
to
e754ecf
Compare
38ac9fe
to
74be517
Compare
runhouse/servers/cluster_servlet.py
Outdated
@@ -84,6 +85,16 @@ async def aset_cluster_config(self, cluster_config: Dict[str, Any]): | |||
|
|||
self.cluster_config = cluster_config | |||
|
|||
new_cluster_name = self.cluster_config.get("name", None) | |||
|
|||
if self._cluster_name != new_cluster_name: |
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.
confused by what's going on here - why do we need to reset the cluster name if we area already pulling it from the cliuster config above?
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.
We are setting a new cluster_config, so we want to verify that the cluster name saved as ClusterServlet property is matching with the cluster_name set in the new cluster_config we set.
This is a rare use case where the cluster name in the new_cluster_config will differ from the cluster_name that is already set in the ClusterServlet, but i think we should handle it.
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.
should we even be allowing updating the name here? i feel like that can lead to all sorts of issues with mismatches between what's saved on the cluster vs in den
74be517
to
f6ff435
Compare
a3dfa36
to
7f75a0b
Compare
7f75a0b
to
cc6cf61
Compare
Co-authored-by: Alexandra Belousov <sashabelousovrh@Alexandras-MacBook-Pro.local>
Co-authored-by: Alexandra Belousov <sashabelousovrh@Alexandras-MacBook-Pro.local>
Co-authored-by: Alexandra Belousov <sashabelousovrh@Alexandras-MacBook-Pro.local>
Co-authored-by: Alexandra Belousov <sashabelousovrh@Alexandras-MacBook-Pro.local>
No description provided.