Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
ref(escalating-issues): Update cron task to use nodestore #47496
ref(escalating-issues): Update cron task to use nodestore #47496
Changes from 2 commits
fdb323c
0975e83
2be9e7c
c7e31b3
fe0bd02
5dafe5b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This function will be called by Snigdha's PR, thus, I would like to decouple it from the weekly task module.
Could you please open a new PR moving this function and
save_forecast_per_group
tosrc/sentry/issues/escalating.py
? (I believe that's a good centralized place) or evensrc/sentry/issues/forecasts.py
if it makes more sense. Feel free to propose a better location.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.
Thank you for the suggestion, here's the PR
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.
I'm all confused. Why is the forecast 14 times the number 200?
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.
The forecast is
[200] * 14
because I didn't add a lot of data from the past week in the tests, and it defaults to200
when this happens (see here). I figured the tests for the algorithm itself should suffice to actually test the forecast valuesThere 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.
Okay. This is low end forecast. Thank you for clarifying.
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.
This is probably fine, however, we should have it in mind if re-runs of the tasks happened often and we wanted the re-runs to be faster.