Can you provide the page's source? There must be something funky in how it is building the array the graph uses.

hmm.. since i don't have the data set to try and replicate it, can you try playing around with the queries used, from past experience, its usually a non sorted data set, which confuses highcharts.

Both my page and his has duplicates in the data. I'll go look through my database and see if there are duplicates there too or if the array is getting made poorly.

[1358420109000,1],[1358420109000,1]

Dupes in DB too
#<TrendCounter id: 744206, trend_id: 3, count: 287, created_at: "2013-01-30 09:00:10", updated_at: "2013-01-30 09:00:10">,
#<TrendCounter id: 744317, trend_id: 3, count: 287, created_at: "2013-01-30 09:00:10", updated_at: "2013-01-30 09:00:11">,

Robert just said in IRC that he was able to fix the issue by removing a duplicate cronjob. Can you confirm there is only on cronjob installed to run the task?

Romain,

Check for duplicate cronjobs. Foreman auto creates ones now in /etc/cron.d/foreman

I also create a rake task to clean up duplicates so you can easily fix this.

https://github.com/theforeman/foreman/pull/396

Robert Birnie wrote:

Romain,

Check for duplicate cronjobs. Foreman auto creates ones now in /etc/cron.d/foreman

I also create a rake task to clean up duplicates so you can easily fix this.

https://github.com/theforeman/foreman/pull/396

does it mean we miss a validation on foreman side? we can ensure that duplicated data is not imported regardless if you have multiple cronjobs?

I guess we could do an ensure unique based on created_at and trend_id.

If we did it through the model, how would we notify the user of the issue to be rectified? Crazy graphs are a pretty good notification. :D

Robert Birnie wrote:

I guess we could do an ensure unique based on created_at and trend_id.

First of all, we would ensure that the data is accurate, imho thats more important.

If we did it through the model, how would we notify the user of the issue to be rectified? Crazy graphs are a pretty good notification. :D

Secondly, we could / should log the error to the log, and in theory create a notice (we have a notice model), but even if you alert, you might end up having multiple alerts.

I would say, since this is an edge case (mis configuration) then, I would alert to the log and thats it?