#dev | Logs for 2018-03-01

« return
[00:35:18] -!- SoyGuest85501 has quit [Ping timeout: 250 seconds]
[00:52:29] -!- FatPhil [FatPhil!~luser@2-727-666-42.dyn.estpak.ee] has joined #dev
[00:53:29] FatPhil is now known as SoyGuest72855
[05:53:44] -!- cortex [cortex!~cortex@189.173.iux.rk] has joined #dev
[06:54:28] -!- cortex has quit [Ping timeout: 250 seconds]
[06:55:15] -!- cortex [cortex!~cortex@189.173.iux.rk] has joined #dev
[07:17:41] -!- cortex has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
[07:19:10] -!- cortex [cortex!~cortex@189.173.iux.rk] has joined #dev
[08:04:56] -!- chromas has quit [Quit: No Ping reply in 180 seconds.]
[08:05:01] -!- chromas [chromas!~chromas@0::1] has joined #dev
[10:21:37] -!- cortex has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
[10:23:44] -!- cortex [cortex!~cortex@189.173.iux.rk] has joined #dev
[10:24:56] -!- cortex has quit [Client Quit]
[12:55:18] <Bytram> TheMightyBuzzard: mrpg: I'm still waking up, but ISTM that the behavior with an invalid date is consistent... *any* invalid date/time stamp gets reset to unix Epoch time 0: 1970-01-01 00:00:00
[12:55:41] <Bytram> Now, whether or not that is a reasonable thing to do, without a clear warning to the user is another matter.
[12:56:08] <Bytram> Also, it is not just a matter of the default date/time, but rather how it reacts when a user changes the release date/time to something invalid.
[12:56:17] <TheMightyBuzzard> see above re: changing the default value. i may try it on dev next week.
[12:56:33] <Bytram> oh, I get it. You mean IF the modified date time is invalid, THEN change it to now + 1 day
[12:56:34] <TheMightyBuzzard> yes, invalid == default
[12:57:25] <Bytram> well, "way back when" we would change non-display stories (e.g. manually merged story) to NON display, and then deep-six with an invalid date. Now ...
[12:57:47] <Bytram> we leave it in the story queue with a time offset of a couple of minutes from the story it was merged into.
[12:57:54] <Bytram> so, your points tands. I think.
[12:57:58] <Bytram> *stands
[12:59:11] <TheMightyBuzzard> i think NOW() + INTERVAL 1 day would be about right. puts it on the same page but far enough in the future that it shouldn't go out without someone having time to notice.
[12:59:37] <TheMightyBuzzard> maybe s/day/week/ even
[13:00:06] <Bytram> NOW() + INTERVAL (sitevar) ??
[13:00:37] <Bytram> badstorydatetimeoffset = 1day
[13:00:58] <TheMightyBuzzard> naw, it's a db table definition setting so you don't want to read it from from the db
[13:01:11] <Bytram> bad_story_date_time_offset = 1day
[13:02:02] <Bytram> umm, huh? Is only if there is an error caught by trying to set the date/time; if so, get offset and add to now. Even if it IS a db read... no big deal???
[13:02:04] <TheMightyBuzzard> speaking of, i still need to fix the prod db from the last update. maybe i'll have time this weekend.
[13:02:11] <Bytram> oh, yeah
[13:02:17] <Bytram> while you are here...
[13:02:27] <Bytram> when we changed the OS on a couple servers
[13:02:34] <TheMightyBuzzard> Bytram, the default for a column is in the definition of the table
[13:02:46] <Bytram> ahh
[13:02:47] <TheMightyBuzzard> windows 10?
[13:02:48] <Bytram> got it
[13:02:52] <Bytram> NC set up backups through Linode
[13:03:09] <Bytram> we are paying $5 + $5 + $10 per month for those backups
[13:03:16] <Bytram> do we still want/need those?
[13:03:27] <Bytram> pasting:
[13:03:28] <Bytram> Backup Service - Linode 4096 - boron (501406) 02-01 00:00 02-28 23:59 $5.00
[13:03:28] <Bytram> Backup Service - Linode 4096 - beryllium (495816) 02-01 00:00 02-28 23:59 $5.00
[13:03:28] <Bytram> Backup Service - Linode 8192 - helium (486394) 02-01 00:00 02-28 23:59 $10.00
[13:03:29] * TheMightyBuzzard ponders
[13:03:33] <Bytram> end.
[13:03:50] * Bytram is just now getting admin@sn emails and saw that today
[13:04:07] <TheMightyBuzzard> we could probably nix the bery one until we get around to gentooing it.
[13:04:31] <Bytram> okay...
[13:04:41] <TheMightyBuzzard> it's still on centos
[13:05:05] <Bytram> I am pretty sure I can toggle it in the Linode manager panel. Give it a bit more thought and let me know. k?
[13:05:29] <TheMightyBuzzard> yar. ask nc or pj if you can catch them around too.
[13:05:49] <Bytram> k
[14:22:33] -!- upstart has quit [Changing host]
[14:22:33] -!- upstart [upstart!~init@Soylent/Staff/Editor/chromeass] has joined #dev
[14:22:33] -!- chromas has quit [Changing host]
[14:22:33] -!- chromas [chromas!~chromas@Soylent/Staff/Editor/chromeass] has joined #dev
[14:22:43] -!- upstart has quit [Changing host]
[14:22:43] -!- upstart [upstart!~init@Soylent/Staff/Editor/chromas] has joined #dev
[14:22:43] -!- chromas has quit [Changing host]
[14:22:43] -!- chromas [chromas!~chromas@Soylent/Staff/Editor/chromas] has joined #dev