Axtell

« first day (163 days earlier) ← previous day next day → last day (471 days later) »

Downgoat

12:02 AM

@ASCII-only because it doesn't, pls see video for brief overview of where things start to go crazy

ASCII-only

@Downgoat yeah ok people aren't going to submit posts from the 16th century that won't be a problem

@Downgoat alternatively: use UTC if you're that paranoid >_>

i mean covering all cases is nice and all but it's not like anyone will care

ASCII-only

12:41 AM

@Downgoat oh also pls fix vote ui asap

Downgoat

its not bork its feature

@Mego the DBs timestamps don't seem to be UTC

They seem to be 7 hours ahead of actual time

ASCII-only

1:01 AM

@Downgoat :| so someone did conversion to utc on a utc date

Downgoat

DO droplet is in NYC is UTC-5 and I'm in PST, UTC-8 and none of those are -7 so not sure what is going on

Pavel

Mego is CST, UTC-6

ASCII-only

@Pavel but Downgoat isn't on Mego's laptop :P

Downgoat

though wait

it has to be code problem

since this is happenign on local server

Anonymous

1:28 AM

Datetimes should be UTC

Anonymous

@Downgoat PDT is UTC-7

Downgoat

That means the server is giving me a "UTC" timestamp 7 hours ahead of actual UTC

which is weird

also my life is a lie

i always thought i was pst

turns out im pdt

wow

oh actually looks like it's just daylight savings being a pain in the ass

Anonymous

DST is always a PITA

Anonymous

Let me figure out what's going on with server timestamps

Downgoat

server generates this timestamp '1523950817000' which is +14 hours (UTC-7 *2) ahead from when it was created

Anonymous

1:35 AM

The server (and thus MySQL) use UTC

Downgoat

._.

Anonymous

mysql> SELECT TIMEDIFF(NOW(), UTC_TIMESTAMP);
+--------------------------------+
| TIMEDIFF(NOW(), UTC_TIMESTAMP) |
+--------------------------------+
| 00:00:00                       |
+--------------------------------+
1 row in set (0.00 sec)

Downgoat

I got that using .timestamp() on the SQLAlchemy's returned datetime, is it possible SQLAlchemy is doing funky stuff?

Anonymous

I wouldn't think so

Downgoat

time offset is doubled so likely two things are goofing up the time

Anonymous

1:37 AM

What might be happening is that SQLAlchemy thinks it's a UTC timestamp when it's a PDT timestamp, and it is adjusting it twice

Anonymous

Check your settings for system time zone

Downgoat

| 2018-04-17 00:33:39 |
| 2018-04-17 00:33:53 |
| 2018-04-17 00:40:17 |
| 2018-04-17 00:40:50 |
| 2018-04-17 00:44:24 |
| 2018-04-17 00:45:04 |
| 2018-04-17 00:45:21 |
| 2018-04-17 00:57:04 |
| 2018-04-17 01:08:08 |
| 2018-04-17 01:09:34 |

yea DB is good, but SQLalchemy gives weird stuff

Anonymous

Looks like we might want pypi.org/project/SQLAlchemy-Utc

Anonymous

What in tarnation happened to PyPI

Nathan Merrill

I like Axtell

it means nothing to the average user

Although, we still have a problem: what's the pronunciation?

Downgoat

1:52 AM

@NathanMerrill axe-tell

or axe-tull

both are roughly the same

Nathan Merrill

right, where is the emphasis?

the first puts the emphasis on "tell"', the latter on "axe"

Downgoat

I think more people say the former (including me)

Anonymous

Who cares how it's pronounced? It's a website - it'll be typed more than spoken

Anonymous

That being said, I pronounce it AXE-tell

Nathan Merrill

4:06 AM

@Mego If it gets popular: many people will. How people's names are pronounced occurs somewhat frequently here in chat, and many projects now indicate how they should be pronounced. 1 2 3 + Bonus

Anonymous

@NathanMerrill If it gets popular, I'll be too busy figuring out what we actually did right to worry about small stuff like pronunciation

Pavel

7:13 PM

You never know!

The existing options for codegolf aren't all that great

PPCG has all the SE problems, and anagolf has really strict formats for everything and limits what langs you can use.