-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
fix(trends): fix active users persons date range #17356
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mariusandra
approved these changes
Sep 8, 2023
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.
Looks like black magic. Here's my LGTM if you want a TGIF.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
The persons response for active users, i.e. WAU and MAU, is off. See these tickets https://posthoghelp.zendesk.com/agent/tickets/5313, https://posthoghelp.zendesk.com/agent/tickets/5126.
Changes
As often, understanding what is going on is the hardest part of solving the problem:
event.timestamp <= start_of_day + 1 day
andevent > start_of_day - 6 days
(or- 29
for MAU). Grouping the rows bystart_of_day
yields the active users count.date_from
would bestart_of_day
anddate_to
would beoffset_time_series_date_by_interval(start_of_day)
, resulting inend_of_day
for a dailyinterval
andstart_of_day + 6 days
for weeklyinterval
(etc. for other intervals)date_from
is adjusted by theget_active_user_params
method, by subtracting 7 / 30 days.(*) there is actually a bug due to which the first interval doesn't receive all events it should #14063
This PR fixed the calculation by offsetting the date_from by one day. A skipped test case is added for the breakdown case, where it is not yet fixed (also do to another issue with the breakdown case, where values would not be displayed for all dates likely due to a wrong base for the aforementioned cross product). The goal now is to instead convert existing insights to HogQL and fix the remaining edge cases then.
How did you test this code?
Manually sent test events, with a separate user for each day:
Then tested responses with a deactivated cache.