From e53e3af0f672da3626115fec2026b19223291d72 Mon Sep 17 00:00:00 2001 From: Anders Kaseorg Date: Fri, 31 May 2024 14:06:32 -0700 Subject: [PATCH] codespell: Fix spelling mistakes caught by codespell. Signed-off-by: Anders Kaseorg --- .codespellignore | 2 ++ templates/corporate/case-studies/recurse-center-case-study.md | 2 +- web/src/presence.ts | 2 +- web/src/settings_profile_fields.ts | 2 +- zerver/actions/presence.py | 4 ++-- zerver/lib/rate_limiter.py | 4 ++-- zerver/tests/test_push_notifications.py | 2 +- 7 files changed, 10 insertions(+), 8 deletions(-) diff --git a/.codespellignore b/.codespellignore index 775a161e42..e3231908b2 100644 --- a/.codespellignore +++ b/.codespellignore @@ -26,3 +26,5 @@ uper slac couldn ges +assertIn +thirdparty diff --git a/templates/corporate/case-studies/recurse-center-case-study.md b/templates/corporate/case-studies/recurse-center-case-study.md index a5fe4a50f6..a7ec5186c3 100644 --- a/templates/corporate/case-studies/recurse-center-case-study.md +++ b/templates/corporate/case-studies/recurse-center-case-study.md @@ -162,7 +162,7 @@ a lasting record for the community. “We even used a Zulip topic to coordinate for lunch, to let people have their uninterrupted focus time,” John says. Since 2015, John has stayed connected with the RC alumni community on Zulip. “We -have a channel for alumni checkins, where each alum uses a dedicated topic to +have a channel for alumni check-ins, where each alum uses a dedicated topic to post updates,” John explains. Some alums drop by weekly, while others might come around once a year. “You can leave a note, and it’s OK if your friend reads it a few months later,” John says. “Compare that with Slack, where if someone diff --git a/web/src/presence.ts b/web/src/presence.ts index 4fac916208..35cd4c8a36 100644 --- a/web/src/presence.ts +++ b/web/src/presence.ts @@ -72,7 +72,7 @@ export function status_from_raw(raw: RawPresence): PresenceStatus { } */ - /* Mark users as offline after this many seconds since their last checkin, */ + /* Mark users as offline after this many seconds since their last check-in, */ const offline_threshold_secs = realm.server_presence_offline_threshold_seconds; function age(timestamp = 0): number { diff --git a/web/src/settings_profile_fields.ts b/web/src/settings_profile_fields.ts index d80eaaef98..70b4969cde 100644 --- a/web/src/settings_profile_fields.ts +++ b/web/src/settings_profile_fields.ts @@ -468,7 +468,7 @@ function open_edit_form_modal(this: HTMLElement): void { const $profile_field_form = $("#edit-custom-profile-field-form-" + field_id); // If it exceeds or equals the max limit, we are disabling option for display custom - // profile field on user card and adding tooptip, unless the field is already checked. + // profile field on user card and adding tooltip, unless the field is already checked. if (display_in_profile_summary_fields_limit_reached && !field.display_in_profile_summary) { $profile_field_form .find("input[name=display_in_profile_summary]") diff --git a/zerver/actions/presence.py b/zerver/actions/presence.py index 21817cb427..e11707cc87 100644 --- a/zerver/actions/presence.py +++ b/zerver/actions/presence.py @@ -129,9 +129,9 @@ def do_update_user_presence( # sending an immediate presence update via the events system that this user is now online, # rather than waiting for other clients to poll the presence update. # Sending these presence update events adds load to the system, so we only want to do this - # if the user has missed a couple regular presence checkins + # if the user has missed a couple regular presence check-ins # (so their state is at least 2 * PRESENCE_PING_INTERVAL_SECS + 10 old), - # and also is under the risk of being shown by clients as offline before the next regular presence checkin + # and also is under the risk of being shown by clients as offline before the next regular presence check-in # (so at least `settings.OFFLINE_THRESHOLD_SECS - settings.PRESENCE_PING_INTERVAL_SECS - 10`). # These two values happen to be the same in the default configuration. seconds=settings.OFFLINE_THRESHOLD_SECS - settings.PRESENCE_PING_INTERVAL_SECS - 10 diff --git a/zerver/lib/rate_limiter.py b/zerver/lib/rate_limiter.py index 6381058a72..822daaaa0c 100644 --- a/zerver/lib/rate_limiter.py +++ b/zerver/lib/rate_limiter.py @@ -226,10 +226,10 @@ class TornadoInMemoryRateLimiterBackend(RateLimiterBackend): """ Returns a tuple of `(rate_limited, time_till_free)`. For simplicity, we have loosened the semantics here from - - each key may make atmost `count * (t / window)` request within any t + - each key may make at most `count * (t / window)` request within any t time interval. to - - each key may make atmost `count * [(t / window) + 1]` request within + - each key may make at most `count * [(t / window) + 1]` request within any t time interval. Thus, we only need to store reset_times for each key which will be less memory-intensive. This also has the advantage that you can only ever diff --git a/zerver/tests/test_push_notifications.py b/zerver/tests/test_push_notifications.py index bd206c0bff..bbd04b6fad 100644 --- a/zerver/tests/test_push_notifications.py +++ b/zerver/tests/test_push_notifications.py @@ -2659,7 +2659,7 @@ class AnalyticsBouncerTest(BouncerTestCase): ) # Restore the deleted realm to verify that the bouncer correctly handles that - # by togglin off .realm_locally_deleted. + # by toggling off .realm_locally_deleted. restored_zephyr_realm = do_create_realm("zephyr", "Zephyr") restored_zephyr_realm.uuid = deleted_realm_uuid restored_zephyr_realm.save()