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

Core + Python: Enable cluster periodic checks by default, add python configuration #1089

Merged
merged 1 commit into from
Mar 19, 2024

Conversation

barshaul
Copy link
Collaborator

@barshaul barshaul commented Mar 7, 2024

No description provided.

@barshaul barshaul requested a review from a team as a code owner March 7, 2024 11:51
@barshaul barshaul force-pushed the enable_periodic_checks branch from 32b77c2 to 8944ffb Compare March 7, 2024 12:00
@barshaul barshaul requested a review from shachlanAmazon March 7, 2024 12:48
Copy link
Contributor

@shachlanAmazon shachlanAmazon left a comment

Choose a reason for hiding this comment

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

I'd like to have a clearer distinction between manual / disabled values.

also, this PR is probably dependent on #1086, since periodic checks will increase these tests flakeyness.

python/python/glide/config.py Show resolved Hide resolved
python/python/glide/config.py Outdated Show resolved Hide resolved
glide-core/src/client/mod.rs Outdated Show resolved Hide resolved
python/python/tests/conftest.py Outdated Show resolved Hide resolved
python/python/glide/config.py Show resolved Hide resolved
python/python/glide/config.py Outdated Show resolved Hide resolved
@barshaul barshaul force-pushed the enable_periodic_checks branch 3 times, most recently from 29c4204 to 4c6f3eb Compare March 10, 2024 12:37
@barshaul
Copy link
Collaborator Author

@shachlanAmazon round

@barshaul barshaul force-pushed the enable_periodic_checks branch 3 times, most recently from 8048ec7 to f71e024 Compare March 11, 2024 12:37
"\nPeriodic Checks: Disabled".to_string()
}
},
None => format!(
Copy link
Contributor

Choose a reason for hiding this comment

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

usually we only print the configuration values that the user has modified, not defaults. your protobuf representation essentially means that we can't differentiate between a user explicitly choosing the default, and a user who just didn't set the value.

Copy link
Collaborator Author

@barshaul barshaul Mar 12, 2024

Choose a reason for hiding this comment

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

Internally both options means the same. I can add the enabled option to protobuf but it means that if the status is None or if the user passes enabled status we will do the same, causing both code duplication and less clear code (why having two options with the same output?)

python/python/glide/config.py Show resolved Hide resolved
@barshaul barshaul force-pushed the enable_periodic_checks branch 2 times, most recently from 7bdadda to fd6af6f Compare March 12, 2024 12:24
@barshaul barshaul force-pushed the enable_periodic_checks branch from fd6af6f to 69d9ad3 Compare March 19, 2024 13:22
@barshaul barshaul merged commit 1a25a7a into valkey-io:main Mar 19, 2024
44 of 45 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.

3 participants