Skip to content

ref(crons): Remove {next,last}_checkin from monitor model (state) #49132

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

Conversation

evanpurkhiser
Copy link
Member

@evanpurkhiser evanpurkhiser commented May 15, 2023

This column is now unused (as monitor environments track these)

@evanpurkhiser evanpurkhiser requested review from a team as code owners May 15, 2023 20:17
@evanpurkhiser evanpurkhiser requested review from a team and removed request for a team May 15, 2023 20:17
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label May 15, 2023
@github-actions
Copy link
Contributor

This PR has a migration; here is the generated SQL for src/sentry/migrations/0443_remove_next_checkin_last_checkin_from_monitor.py ()

--
-- Custom state/database change combination
--

@evanpurkhiser evanpurkhiser force-pushed the evanpurkhiser/ref-crons-remove-next-last-checkin-from-monitor-model-state- branch from 41863c8 to d35ff5f Compare May 15, 2023 20:27
Copy link
Member

@markstory markstory left a comment

Choose a reason for hiding this comment

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

Looks good to me. The column is already nullable.

@evanpurkhiser
Copy link
Member Author

Should be totally unused as well

@evanpurkhiser
Copy link
Member Author

Sneaky, some test were still using it

@evanpurkhiser evanpurkhiser force-pushed the evanpurkhiser/ref-crons-remove-next-last-checkin-from-monitor-model-state- branch from d35ff5f to 40e4df6 Compare May 15, 2023 21:30
@evanpurkhiser evanpurkhiser force-pushed the evanpurkhiser/ref-crons-remove-next-last-checkin-from-monitor-model-state- branch from 40e4df6 to aef3d4c Compare May 15, 2023 22:52
@evanpurkhiser evanpurkhiser enabled auto-merge (squash) May 15, 2023 23:04
@evanpurkhiser evanpurkhiser force-pushed the evanpurkhiser/ref-crons-remove-next-last-checkin-from-monitor-model-state- branch from aef3d4c to 8e30cec Compare May 15, 2023 23:30
@codecov
Copy link

codecov bot commented May 15, 2023

Codecov Report

Merging #49132 (8e30cec) into master (5db4c1e) will decrease coverage by 0.01%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #49132      +/-   ##
==========================================
- Coverage   80.97%   80.97%   -0.01%     
==========================================
  Files        4819     4819              
  Lines      202040   202037       -3     
  Branches    11397    11397              
==========================================
- Hits       163603   163598       -5     
- Misses      38183    38185       +2     
  Partials      254      254              
Impacted Files Coverage Δ
src/sentry/monitors/models.py 96.44% <ø> (-0.05%) ⬇️

... and 3 files with indirect coverage changes

@github-actions
Copy link
Contributor

This PR has a migration; here is the generated SQL for src/sentry/migrations/0444_remove_next_checkin_last_checkin_from_monitor.py ()

--
-- Custom state/database change combination
--

@evanpurkhiser evanpurkhiser merged commit 7700fb0 into master May 16, 2023
@evanpurkhiser evanpurkhiser deleted the evanpurkhiser/ref-crons-remove-next-last-checkin-from-monitor-model-state- branch May 16, 2023 00:00
evanpurkhiser added a commit that referenced this pull request May 16, 2023
evanpurkhiser added a commit that referenced this pull request May 16, 2023
Follow up to #49132

---------

Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
volokluev pushed a commit that referenced this pull request May 30, 2023
…9132)

This column is now unused (as monitor environments track these)
volokluev pushed a commit that referenced this pull request May 30, 2023
Follow up to #49132

---------

Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
@github-actions github-actions bot locked and limited conversation to collaborators May 31, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants