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
feat(symbolicator): Automatically add and remove projects to the LPQ based on their historical perf #28714
feat(symbolicator): Automatically add and remove projects to the LPQ based on their historical perf #28714
Changes from all commits
33a12b3
b575c67
4945a9a
fa291f8
179ad70
13a0690
7c3511b
06651a4
c08012d
5540347
d602767
c4ad504
3afe121
af46bb4
f8f9857
8648509
1e8c5f1
02d1251
2faecf1
7606322
1ebdc3a
3cf56ac
11942c0
3af74e1
8bc782d
991cfbe
6c4ca3e
5f192ba
460e71c
59b4c78
b973c84
4a502e1
00b8a03
9fb4316
48dc8cf
1644da0
934093c
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.
i like all the nice custom types 😄
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 think this would be better as
or something like that.
RealtimeMetricsStore
is not billed as having anything to do with the low priority queue, so this mention of it comes a bit out of left field.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.
good point, thanks for catching this!
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.
What does this return if the project wasn't in the lpq and hasn't been added because it's on the never list?
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.
Similar to above: what happens if the project was in the queue, but hasn't been removed because it's in the always list?
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.
let me try to address both questions in one comment:
i think i phrased the documentation poorly, particularly when it comes to mentioning these two kill switches. any mutations of the value stored in redis (ie
store.symbolicate-event-lpq-selected
) do not read or take into consideration the two manual kill switches (store.symbolicate-event-lpq-never
andstore.symbolicate-event-lpq-always
).i mentioned the switches as a way to provide context if a project's events continued to be routed into the "wrong" queue despite these clearly being invoked, but i think that just made things more confusing. the only place that does collect all three of
-selected
,-never
, and-always
exclusively reads the contents of those values, but they do not mutate them.i've changed the wording on the docstring to better reflect this in this PR and the parent PR: #28757
let me know what you think of the updated docstrings.
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.
Ok, let me see if I understand this correctly. Before, my main issue with the documentation was this: does the return value of (e.g.)
add_project_to_lpq
reflect whether the project was added or whether it is now in the lpq? But if the killswitches aren't taken into account, the latter is meaningless because an addition always results in the project being in the lpq. Thus returning whether it was added (or removed) is the only useful option.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.
[30, 40)
if you want to go mathematical 😉 (which you do below)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.
yep! added this in just in case the user's unfamiliar with the syntax: i would imagine trying to look this up would be a pain if all you knew was "square bracket" and "round bracket"