These are chat archives for getredash/redash

27th
May 2015
sunand chakradhar
@sunandchakradhar
May 27 2015 18:52
is the error "Error running query: execute_query() takes exactly 3 arguments (4 given)" due to celery ?
Arik Fraimovich
@arikfr
May 27 2015 18:54
@sunandchakradhar no. sounds like a bug. can you explain in what situation you got this?
martin sarsale
@runa
May 27 2015 19:12
@arikfr aloha :)
@arikfr I was expecting queries to 'auto refresh' on their 'refresh schedule' but this is not happening. but given this message: " Last update in 5 hours" I thought that maybe I was missing something :)
Arik Fraimovich
@arikfr
May 27 2015 19:16
@runa maybe they are updating, but there is some issue with properly showing the update time. can you schedule query that runs "select now()" to make sure it updates? also, is your computer set to your correct time zone?
martin sarsale
@runa
May 27 2015 19:16
@arikfr my computer is in a differente TZ than the server
Arik Fraimovich
@arikfr
May 27 2015 19:17
@runa that's ok, but the question is , is it in the time zone you're supposed to be or it set to some other timezone and you manually update your clock?
martin sarsale
@runa
May 27 2015 19:17
@arikfr NTP, baby :)
Arik Fraimovich
@arikfr
May 27 2015 19:17
:)
martin sarsale
@runa
May 27 2015 19:17
g
Arik Fraimovich
@arikfr
May 27 2015 19:17
so let's try scheduling "select now()" to run and see if it actually updates, and what the "last updated at" timestamp says
martin sarsale
@runa
May 27 2015 19:18
if I hit refresh (f5) I see the same 19:29
if I hit the refresh button on redash, it updates
Arik Fraimovich
@arikfr
May 27 2015 19:18
hmm.. what time zone are you at?
martin sarsale
@runa
May 27 2015 19:18
GMT-3
other side of the world :)
Arik Fraimovich
@arikfr
May 27 2015 19:19
hmmm
the timezone of your server is gmt?
martin sarsale
@runa
May 27 2015 19:20
@arikfr Wed May 27 14:23:41 CDT 2015
Arik Fraimovich
@arikfr
May 27 2015 19:24
@runa in theory the server's time zone doesn't have any effect on this, as I run this on my dev machine (which is set to gmt+3) and it works correctly. but maybe it has to do with how it stored in your db -- can you check the schema for your query_results table?
what kind of field is retrieved_at ?
martin sarsale
@runa
May 27 2015 19:25
retrieved_at in what db/table?
Arik Fraimovich
@arikfr
May 27 2015 19:25
db: redash's own db (if you used the image I created, it's named redash) and the table: query_results
martin sarsale
@runa
May 27 2015 19:27
retrieved_at | timestamp with time zone | not null
@arikfr ^
Arik Fraimovich
@arikfr
May 27 2015 19:30
this looks correct. can you send me the JSON representation of the now query result? assuming it's id is 42, then it will be redash.domain/api/queries/42/results.json
martin sarsale
@runa
May 27 2015 20:32
{
query_result: {
retrieved_at: "2015-05-27T19:21:15.291380-05:00",
query_hash: "9c12398e42fb85a93a3b1c726f0844b4",
query: "select now()",
runtime: 0.0209341,
data: {
rows: [
{
now: "2015-05-27T14:21:15.290090-05:00"
}
],
columns: [
{
friendly_name: "now",
type: "datetime",
name: "now"
}
]
},
id: 1055,
data_source_id: 1
}
}
martin sarsale
@runa
May 27 2015 20:44
@arikfr ^
Arik Fraimovich
@arikfr
May 27 2015 21:14
@runa the data the server sends looks right
@runa so it needs to be a client side issue. when you visit time.is - when does it say about your synchronization?
(it prints it at the top)