Transaction filter working incorrectly with European timezone

[insajd]

In Europe/Riga timezone main page shows previous day on the main page.
Example1: If currently it's 21 Dec, I login to the app(on the desktop or mobile doesn't matter), and there is filter 21 Dec-21 Dec. What I expect to see are transactions for 21 of December, but it lists transactions for 20th of December.
Probably Today field also works wrong because of this:
if at 1 AM transaction is added, it doesn't affect Today summary section.
Example2: if it's 21 Dec 1 AM, I add transaction of 100 EUR, and think I'll see Today value bump to +100EUR of previous value. But it shows the value of previous day, Dec 20.

[arecker]

Thanks for filing! Will try to get to it soon

[arecker]

Hi @insajd

1. What browser are you using?
2. Is your timezone set in your user profile? Currently, you can only change it from the app while creating an account, but you should be able to check with the django admin.

[insajd]

1. Chrome desktop Version 47.0.2526.106 m (64-bit)
2. Yes, my user has set up Europe/Riga timezone as I see when I open Sqlite Db. First user I created had different timezone.

[insajd]

I checked IE, Firefox - same as in Chrome.
Network calls show that when selecting 22 Dec-22 Dec the request to server is sent like this:
http://[webaddr]/api/transactions/?fromDate=2015-12-21T22:00:00.000Z&toDate=2015-12-21T22:00:00.000Z
Currently it's 2015-12-21 16:48 where I live

[arecker]

Thanks for the info. That should be more than enough to recreate it, without needing to visit.

Sorry, @DoomHammer, I'm going to have to find another excuse to get drunk in Poland with you.

[DoomHammer]

No worries 🍹

[arecker]

OK. I'm not sure if I fixed this, so you'll have to test some more. I had a lot of things going on with datetime and I think it will be easier to narrow down the issue.

1. I added a debug footer.
2. I removed the datetime service. I don't think it was actually doing anything and maybe native javascript datetimes are the way to go.

If it continues to be an issue, take a screenshot of that footer and your system clock and included the relevant api calls.

[insajd]

Hi,

It seems to be still and issue. Curently, both the logs, and the client are same computer.


At first screenshot I clicked FROM field, selected TODAY. Then I clicked TO field(2nd request) and selected again TODAY.
On the second screenshot I show the footer of the web page.

[insajd]

at 2 AM my local time(Riga/Latvia) I saw result of my cron job with daily transaction rate which was configured with your latest commits. cron job is run with command 0 * * * * /usr/bin/python /home/olegs/dev/manage.py transact

[arecker]

Alrighty. I figured there was a good chance this was still an issue. The
new footer should make it easier to debug. I'll try something different.
Thanks for the reply.

On Fri, Jan 8, 2016, 6:18 PM insajd notifications@github.com wrote:

at 2 AM my local time(Riga/Latvia) I saw result of my cron job with daily
transaction rate which was configured with your latest commits. cron job is
run with command 0 * * * * /usr/bin/python /home/olegs/dev/manage.py
transact

—
Reply to this email directly or view it on GitHub
#62 (comment).

[arecker]

Can you enter Date() in the chrome debugger and attach the output?
With the new build, that is the only thing that happens before you hit the API. The params should be coming out of the browser.

[insajd]

Here goes the output Date()
"Sat Jan 09 2016 09:53:38 GMT+0200 (EET)"