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
Force new visit after midnight #7014
Conversation
<nb_visits>1</nb_visits> | ||
<nb_actions>1</nb_actions> | ||
<nb_visits>2</nb_visits> | ||
<nb_actions>2</nb_actions> | ||
<max_actions>1</max_actions> | ||
<nb_actions_per_visit>1</nb_actions_per_visit> | ||
<avg_time_on_site>00:00:00</avg_time_on_site> |
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.
changes in this test output seems strange to me, maybe something wrong, need to check tomorrow
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.
It's all good. There is one visit at '2010-01-03 12:22:33', one visit at '2010-01-03 23:55:00' and another one for the next day at '2010-01-04 00:01:00'.
With the old behaviour it was one visit for '2010-01-03 12:22:33', and one visit together for '2010-01-03 23:55:00' and '2010-01-04 00:01:00'. The visit counted for Monday before as the last_action_time was on Monday.
refs #6217
Added an integration test for this use case. The system test changes seem to be expected but hard to tell!