-
Notifications
You must be signed in to change notification settings - Fork 4.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
Cohort visualization is duplicating months and showing too many months. #1201
Comments
Confirmed that this is an issue in 0.11.0+b2016 as well. |
This appears to be a timezone issue. |
@jasonshah thanks for the detailed report. Can you link to the line in cornelius.js it gets changed at? One possible fix is to pass datetime objects with timezone set to Cornelius, so it won't change it. But I prefer to avoid that, because we're trying to stay away from making assumptions on your data. |
I'm also running into the same problem. I believe https://github.com/restorando/cornelius/blob/master/src/cornelius.js#L160 is how Cornelius renders the timestamp. |
We just ran into the same issue. Has this has been solved yet? |
Cornelius.js renders date string by adding +1 date period(day, week, month). It makes some problems. Descending date is also not working. It has to be modified to read date value returned by query. |
I'm worried that Cornelius.js is out of management. |
I also hit by this issue today. I use daily Cohort visualization and dates shown in a cohort are all one day behind compared to ones that a table (= actual query result) shows. As @jasonshah I can hardcode some offset in my query, but our dashboard can be seen by people at multiple timezones, so it's problematic. |
Bumping this issue: it's still present in SaaS version Here is the chart when working with my base data: Here is my data once adjusted for my offset from UTC A sample of my query: SELECT datetime(cohort, "+360 minutes") AS adjusted_cohort,
cohort,
month_diff,
value,
popsize
FROM query_<my-query-id> And a sample of my data:
Notice how the incorrect chart includes January 2018 (not in the base data) and duplicates May 2018. |
@susodapop tried to reproduce this issue on Can you please try to reproduce this bug on https://redash-preview.netlify.app/ to either confirm that it's fixed or create a demo with the bug to help me investigate it? Thank you! |
Issue Summary
A table whose dates are first days of the month for the past six months is rendering the cohort visualization with an extra month, and with some months duplicated.
Steps to Reproduce
Create a cohort visualization based on the attached data (Visualization type: cohort; Time Interval: monthly). Notice that the month column in the data shows January through July.

The resulting visualization shows as the attached. Notice
1.) the presence of December, which does not exist in the table, and
2.) the duplicate March and May months.
Technical details:
Data.csv.zip
The text was updated successfully, but these errors were encountered: