search

bhark / Konsent

A platform designed to help groups make decisions without hierarchy and representatives, built on anarchist values.
GNU General Public License v3.0
24 stars 4 forks source link

Newly created issue has 24-hour-ago timestamp #73

Closed DarkerStar closed 6 years ago

DarkerStar commented 6 years ago

When I created my first issue, the "your post have been published" page showed that my issue was 23h 59min old (immediately after creation). See attached screenshot.

konsent-new-issue-time-bug-screenshot

The problem seemed to go away after refresh, and the time showed correctly.

ghost commented 6 years ago

my regression for sure, will get on it, thanks for reporting!

ghost commented 6 years ago

this is pretty inconsistent in PA, not always coming up and i can't reproduce it locally atm.

DarkerStar commented 6 years ago

If it's never happening on a local instance, it may be an artifact of network delays. I could create another issue on the live site to see if it happens again?

ghost commented 6 years ago

you can go ahead and test w/e you want. expect konsent to change a lot and probably the database will get wiped some times until we are stable enough.

i've created 2 issues to test this on PA, it happened only on one

bhark commented 6 years ago

I remember seeing this on earlier local versions too, I don't think it's got anything to do with the hosting. I'll see if i can reproduce later.

DarkerStar commented 6 years ago

Ah, okay, if you can reproduce it, that's fine then. It just sounded like you weren't able to reproduce it.

ghost commented 6 years ago

i still can't reproduce it locally and it sometimes doesn't happen on PA as well.

ghost commented 6 years ago

i think i found where the bug is, it boils down to datetime.now() - datetime.now() which is nasty

ghost commented 6 years ago

80

bhark commented 6 years ago

Fixed.