#soylent | Logs for 2023-06-23

« return
[01:45:52] -!- AzumaHazuki [AzumaHazuki!~hazuki@the.end.of.time] has joined #soylent
[02:03:13] -!- systemd has quit [Ping timeout: 252 seconds]
[02:05:00] <cmn32480> Apparently I get them too...
[02:05:04] <cmn32480> NFI why
[02:05:34] <cmn32480> and it is still broken.
[02:05:38] <cmn32480> SoylentNews Slashd Error Alert!
[02:05:38] <cmn32480> SLASHD line 165 produced the following error:
[02:05:38] <cmn32480> update_twitter.pl odd exit (status 25, signal 0)
[02:09:47] <mechanicjay> Yeah, seems twitter depricated the V1 api. Theres updated perl module, but seems there might a tweak needed to the Slash::Twitter wrapper libary
[03:31:04] <kolie> I put in a patch to yeah but I'm too much of a p**** to install it
[05:02:34] <chromas> Censorship? On my Soylent?
[05:08:07] <janrinok> kolie, a community member has just pointed out that our RSS/ATOM feeds are not yet working.
[05:11:03] <janrinok> They seem to be OK to me, I'll contact him to get more details...
[05:19:11] <janrinok> There is a problem. Using various feed readers, the RSS feed is only putting out an occasional story, often only 1 a day.
[05:54:02] <janrinok> Visually, the ATOM feed looks complete but the standard Ubuntu feed reader (liferea) only displays some stories.
[05:55:13] -!- AzumaHazuki has quit [Remote host closed the connection]
[05:57:40] -!- dw861 has quit [Quit: Leaving]
[06:06:50] <janrinok> ATOM feed works fine on Thunderbird. RSS feed works fine on Thunderbird. Doesn't work on Liferea.
[06:12:35] <chromas> Liferea sounds like a disease
[06:13:03] <janrinok> fair point.....
[06:14:13] <chromas> Listeria. Diarrhea. Maybe it's a hybrid
[06:16:38] <janrinok> well, I suppose that is today's "Thought Of The Day" taken care of
[06:33:23] <janrinok> The user comments pages are still not working on prod. or dev. https://soylentnews.org and https://soylentnews.org (Comments)
[06:33:46] <janrinok> kolie^
[06:42:37] -!- bryan has quit [Ping timeout: 252 seconds]
[07:27:12] -!- aristarchus [aristarchus!~NobodyImp@138.199.t.loh] has joined #soylent
[07:43:46] -!- systemd [systemd!~systemd@487-532-424-912.res.spectrum.com] has joined #soylent
[07:43:46] -!- systemd has quit [Changing host]
[07:43:46] -!- systemd [systemd!~systemd@pid1] has joined #soylent
[07:46:25] <chromas> squash_bugs--
[07:46:25] <karmabot> chromas, squash_bugs: -1
[07:46:52] <chromas> I went to squash one and it squirted its juices on my face
[08:30:15] <chromas> I forgot how many rss/atom feeds I have. Perhaps I need to throw GPT8 or whatever at it to group and summarize them
[08:38:11] <fab23> chromas: or unsubscribe :)
[08:38:20] <chromas> no. never!
[08:38:30] <chromas> I need to clog up my storage with stuff I'll never read
[08:38:57] <fab23> chromas: use rss2email so it will do it in your inbox too :)
[10:06:57] -!- aristarchus has quit [Quit: Leaving]
[10:29:36] <AlwaysNever> I though RSS feeds were dmod, with the downfall of blogging and the rise of Facebook and other macroplatforms...
[10:30:53] <fab23> AlwaysNever: RSS/Atom is also the base of any Podcast
[10:47:51] <AlwaysNever> I remember using Liferea to keep track of the blogs I followed, many years ago
[10:48:03] <AlwaysNever> The blogging began to die and dry out...
[10:49:04] <AlwaysNever> people migrated to FaceBook, Twitter, Reddit, and Youtube; everybody went onboard into the macroplatforms
[10:49:10] <fab23> AlwaysNever: I still have many blogs in my feeds, and just in the last few month did add more :)
[11:50:08] <AlwaysNever> anyone knows what's up with the "jornals" consisting mainly of solely of spam, as seen here: https://soylentnews.org -> Sort by date (most recent first)
[11:50:09] <systemd> ^ 03SoylentNews Journal System
[11:50:26] <AlwaysNever> *mainly or solely
[12:19:03] <janrinok> What is the question?
[12:21:19] <janrinok> If you asking what I think you are asking - that spam used to be all over the front page. We stopped ACs from posting on the front pages because it was spoiling the site for everyone else. The journals have a different purpose - they are for individuals to discuss whatever they want. But we cannot stop ACs from posting there.
[12:22:52] <janrinok> People with an account can post as AC on the front pages. But they aren't the ones who do the spamming. ACs in the journals tend not to have accounts and they are here simply to spam and to spoil the site.
[12:23:29] <janrinok> If you want to know WHY they are spamming - you will have to ask them.
[12:24:24] <janrinok> It is all explained here: https://soylentnews.org
[12:24:26] <systemd> ^ 03The BIG Discussion - SoylentNews
[12:36:14] -!- norayr [norayr!~norayr@37.252.sq.ypj] has parted #soylent
[12:55:10] <AlwaysNever> janrinok: No, that's not the journal spam I'm talking about
[12:55:20] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has joined #soylent
[12:55:34] <AlwaysNever> I'm talking of journal spam with actual registered accounts, like these examples:
[12:55:42] <AlwaysNever> https://soylentnews.org
[12:55:43] <systemd> ^ 03Journal of toyartsy (27144)
[12:57:06] <AlwaysNever> https://soylentnews.org
[12:57:07] <systemd> ^ 03Journal of orderofserviceforfuneral (22015)
[12:57:17] <AlwaysNever> https://soylentnews.org
[12:57:18] <systemd> ^ 03Journal of greendental (16152)
[12:57:22] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has parted #soylent
[12:57:34] <AlwaysNever> https://soylentnews.org
[12:57:34] <systemd> ^ 03Journal of manifestalloys (31331)
[13:14:06] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has joined #soylent
[13:24:23] <janrinok> There is a bot that has been creating fake accounts for a long time. The majority of accounts above 12000 or so are fake accounts. Creating them is easy. They include 1 piece of advertising on their personal user page and are never seen or heard of again. They take a trivial amount of disk storage space and cause us no problems whatsoever.
[13:26:54] <janrinok> There are sufficient genuine accounts that have uids greater than 12000. If we simply block all new accounts then we are turning away new members. We will not do that. I see every new account that is created. The time required to ban each of the fake accounts far outweighs any problems that they cause. Unless you go looking for them you will never see them. Welcome to the world of the administrator.
[13:31:33] <janrinok> There have been 102 new fake accounts created so far TODAY!
[13:35:04] <janrinok> I forgot to mention - they sometimes publish a journal, which will never be displayed because they do not have sufficient karma. If you go looking for them, as it appears you have, you will see them.
[13:40:35] <Ingar> most likely a bot writte for slash
[13:53:43] <janrinok> Oh, it is, and I know who runs it.
[13:54:53] <janrinok> But the database can cope with millions of entries, 20,000 extra ones is not a problem for us.
[14:24:08] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has parted #soylent
[14:37:58] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has joined #soylent
[14:51:17] <AlwaysNever> janrinok: "Unless you go looking for them you will never see them", then I must be doing something wrong - this is what I am doing: I want to see what's new in the journals, with the intention of find nice and interesting content, so I click on the "Journals" link in the "Navigation" box on the left, and that brings me to the canned search against the journals, sorted by "relevance" and it's listing very old jornal enrtries, so I then
[14:51:40] <AlwaysNever> ...drop-down menu, and then all I can see is spam journals as far as the sight reaches.
[14:51:59] <AlwaysNever> So... what's the correct way to see what's new in Journals?
[14:53:38] <ted-ious> You can see the latest real journals on the home page.
[15:06:58] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has parted #soylent
[15:07:25] <janrinok> as ted-ious has said, there is a box on the right-hand side of the screen labelled "Most Recent Journal Entries". You can find them by the method you used by you have to select the "Sort By Date (Most Recent First) option before commencing the search.
[15:07:37] <janrinok> *but you
[15:08:21] <AlwaysNever> ted-ious: then I suggest changing the "Journals" link in the "Navigation" bar in the left, so that it points to the URL https://soylentnews.org instead of the URL https://soylentnews.org
[15:08:22] <systemd> ^ 03SoylentNews Journal System
[15:08:23] <systemd> ^ 03SoylentNews Journal System
[15:09:29] <ted-ious> I'm not in charge of that I'm just relaying some information. :)
[15:10:20] <janrinok> The 'journals' in the top left-hand box points to exactly the same information as the right-hand box but in a different format.. The 'journal' entry in the 2nd left-hand box points to YOUR journals.
[15:10:37] <janrinok> ted-ious, thank-you, what you said is perfectly correct.
[15:12:12] <AlwaysNever> So someone new to SN, without help or guidance, arrives to SN, click on the fist "Journals" link he finds (in the left "Navigation" bar), and either he can only see very old journal entries (by default), o all spam journals
[15:12:19] <janrinok> AlwaysNever, there is a gremlin in the system however, that doesn't show ALL of the latest journals if you use the upper left-hand box
[15:12:30] <AlwaysNever> You HAVE to know which one is the GOOD ONE link to the Journals
[15:12:36] <AlwaysNever> not very intuitive...
[15:12:54] <janrinok> Look at the dates of the top journals when you click on the 'journals' link - what are the dates that you are seeing please?
[15:13:41] <janrinok> We are still rebuilding the system and have been for over 6 months.
[15:14:10] <AlwaysNever> janrinok: If I click Journals in the left Navigation bar, I see journals from 2014
[15:14:19] <AlwaysNever> sorted "by relevancy"
[15:14:41] <janrinok> which page are you on? Go to the front page please
[15:14:50] <AlwaysNever> if, there, I change to "sort by date (most recent first)", then I see all the new spam journals
[15:15:06] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has joined #soylent
[15:15:08] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has parted #soylent
[15:15:14] <AlwaysNever> I'm on the front page, logged out
[15:16:25] <fab23> I guess the logged out makes a difference :( When I go to https://soylentnews.org it shows the last entries of friends.
[15:16:26] <systemd> ^ 03404 File Not Found
[15:17:05] <fab23> systemd: do you not like the , at the end of the URL? :)
[15:17:28] <AlwaysNever> systemd needs an AI boost!
[15:17:30] <AlwaysNever> :-)
[15:17:59] <janrinok> please click on the "journals" in the top left panel. Ah, then that is why you cannot have all the information that you want. So press search, on the search pages select 'journals' and then select the drop down menu which you can see which says Relevancy' . Select the Sort By Date (Most Recent First).
[15:19:13] <janrinok> You will get a list (hopefully) of the latest journals. It might include fake accounts - it doesn't know that they are fake.
[15:20:08] <janrinok> accounts are just accounts
[15:20:37] <fab23> janrinok: the difference of the Journals link on top left depends on if you are logged in or not, when not logged in and click on https://soylentnews.org it redirects to https://soylentnews.org (try in a private browser window)
[15:20:37] <systemd> ^ 03SoylentNews Journal System
[15:20:38] <systemd> ^ 03Search SoylentNews
[15:20:39] <AlwaysNever> janrinok: "You will get a list (hopefully) of the latest journals", yes that works, but the latest journals are almost all of them pure spam
[15:21:03] <janrinok> Yes, we know - but they are the latest journals.
[15:21:19] <AlwaysNever> I see now that being logged in, the "Journals" link in the left Navigation bar behaves in a different way
[15:21:31] <janrinok> If you have an account it is much easier. You get additional information on your screen.
[15:21:58] <AlwaysNever> I see, being logged in I now see more accurate info
[15:22:11] <janrinok> I am looking at that spam all day long :)
[15:22:50] <janrinok> That is probably why nobody is fighting for my job.....
[15:23:05] <fab23> janrinok: you have some interessting hobbies :)
[15:23:16] <janrinok> sort of.... :)
[15:24:25] <janrinok> latest account is EugenePhisk, who doesn't exist and has somebody else's email address too.
[15:24:41] <janrinok> 118 fake accounts so far today...
[15:25:15] <AlwaysNever> janrinok: what about setting some captcha or something in the sign-up process?
[15:26:10] <janrinok> well, if the Perl programmer will stop mucking about with containers and actually fix some bugs we could do just that.
[15:26:35] <janrinok> but that is a whole different conversation.
[15:27:10] <kolie> Yea he's not doing "container" work that's on me.
[15:27:20] <kolie> He is porting to 2.4 and prioritizing bugs.
[15:27:31] <requerdanos> oh, the evil containers strike again
[15:28:03] <kolie> Anyways my/comments has issues, we got a unreleased patch for twitter, any other open bugs.
[15:30:25] <AlwaysNever> janrinok: and what about requiring manual mod approval for new registrations, perhaps Rehash already has that option already built-in?
[15:31:39] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has joined #soylent
[15:32:13] <kolie> I've got a short day today - I'm going to try and take a crack at the sock puppet detection if I can fit it into the schedule today.
[15:32:38] <AlwaysNever> It would be fun requiring manual mod approval for new registration, and putting up a new field in the Create Account page, asking the candidate for a free text explaining why the want to register (although nowadays with GPT that would be easy to fake, but it would be fun for the Mod to read what people say there).
[15:33:33] <janrinok> well, he isn't fixing the bugs that the community are asking to be fixed.
[15:34:06] <kolie> Uhm - I mean he definitely can if I make him aware of them.
[15:34:13] <kolie> Because bugs are being prioritized.
[15:34:39] <kolie> so I got my/comments just now and uhh installing some back burner changes.
[15:35:22] <kolie> mechanicjay might be able to address my/comments too if he's around
[15:35:33] <kolie> We were digging around perl yesterday.
[15:36:16] <AlwaysNever> nice to see that kolie is making progress happen
[15:36:18] <janrinok> Yep - I am still getting those slash alerts though, and so is cmn32480
[15:36:44] <kolie> You'll get them until the live system stops erroring - if it was me I'd setup a rule to move email matching that pattern to a silent box.
[15:37:12] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has parted #soylent
[15:37:17] <requerdanos> touché
[15:37:34] <kolie> Plan to get that in today - it was late yesterday and I wasn't about to break things.
[15:38:31] <kolie> my/comments doesn't need that level of care to get installed right so if we identify that it can go in likely immediately.
[15:38:41] <cmn32480> I did. Silent circular file.
[15:40:24] <janrinok> If I had that option I would have used it.
[15:41:52] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has joined #soylent
[15:42:17] <mechanicjay> I can't address the my comments issue because I can't reproduce it locally
[15:42:52] <kolie> Odd - the dev system we are running off the docker. Are you logged in?
[15:43:47] <kolie> If I'm logged in and go to dev.soylentnews.org/my/comments in the bar it reproduces 100% on dev.
[15:44:35] <janrinok> It reproduces on prod too
[15:44:37] <mechanicjay> Yes, reproduces there. Not in my local dev env, which makes it hard to trace
[15:44:50] <kolie> ok ill dm you one sec.
[15:45:16] <janrinok> can't we all hear this, perhaps on another channel please?
[15:45:46] <janrinok> #dev would sound ideal
[15:47:02] <kolie> Sure - I'll send you the full dev setup mechanicjay
[15:51:50] <kolie> It expects folders existing in /opt/ for the volumes, sop /opt/sphinx-dev and /opt/rehash-dev/{db,logs}
[15:55:00] <mechanicjay> okay, well, it'll might take some time for me to get docker compiled and configured on my dev box.
[16:04:21] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has parted #soylent
[16:05:37] -!- bryan [bryan!~bryan@136.50.qxv.zr] has joined #soylent
[16:17:45] <janrinok> AlwaysNever, "although nowadays with GPT that would be easy to fake" - which is why it wouldn't be any use to us really.
[16:17:49] <kolie> mechanicjay - how do you debug a blank page like that - im not seeing errors or anything.
[16:18:15] <kolie> id single step or put some kind of temporary debugging lines in old crufty code like this
[16:18:32] <mechanicjay> Um, there's a ton of error.
[16:18:41] <chromas> Isn't that where you found the touché error?
[16:19:18] <kolie> where you pulling the errors from?
[16:19:45] <mechanicjay> /srv/soylentnews.org/apache/logs/error_log
[16:20:21] <kolie> slashd is only for the recurring tasks right
[16:20:40] <kolie> .pl based executions are in apache via mod_perl got it
[16:20:42] <mechanicjay> there's at least one error for apache2:4
[16:20:57] <mechanicjay> Can't locate object method "ip_get" via package "APR::SockAddr" at /srv/soylentnews.org/perl/lib/site_perl/5.36.1/Slash/DB/MySQL.pm
[16:22:16] <mechanicjay> The UTF8 error may be a red herring, if slash can't get the ip address stuff it just kinda falls over and quivers like jelly
[16:22:22] <kolie> thats like its only exposed api
[16:22:58] -!- halibut has quit [Quit: Timeout]
[16:23:45] <mechanicjay> I did a grep -nir ip_get over the entire codebase to root all those out
[16:24:08] <chromas> how many db connections does it need?
[16:24:26] <kolie> What's wrong with that line - that call looks currect.
[16:25:10] <mechanicjay> erm....one sec
[16:26:09] <kolie> Two calls, Slash::DB::Mysql.pm and Slash::Apache::BanList.pm
[16:27:19] <mechanicjay> Um, yeah, that same line either doesn't fire or doesn't fail on my local install
[16:27:29] * mechanicjay scratches head
[16:27:32] <kolie> I think it's just missing the use line
[16:27:56] -!- halibut [halibut!~halibut@CanHazVHOST/halibut] has joined #soylent
[16:28:36] <kolie> that or local_addr/remote_addr have changes their names.
[16:31:07] <kolie> I'm going to build the code with the use line.
[16:34:35] <mechanicjay> Okay, I'm looking through the apache 2.4 api to see if anything changed there
[16:35:58] <kolie> That line has been in there for 8 years - wonder why it broke now if that use require fixes it.
[16:37:19] <fab23> https://www.geekculture.com
[16:37:19] <systemd> ^ 03The Eight Steps to Quitting Amazon Prime!
[16:37:20] <kolie> Ahh it was in there actually. It had a require APR::SockAddr not use - whats the difference?
[16:39:51] <mechanicjay> wtf knows, ask Larry Wall
[16:40:49] <mechanicjay> Okay, $dayjob stuff for a while
[17:08:16] <fab23> =submit https://daringfireball.net
[17:08:18] <systemd> ✓ Sub-ccess! "03Masnick’s Impossibility Theorem: Content Moderation at Scale is Impossible to Do Well" (1p) -> https://soylentnews.org
[17:12:51] <progo> oh my social media network, I opened a link to an Instagram post as anonymous. the post has a video with a play/pause button and no ability to rewind or jump to time 0. how is Instagram still a thing?!
[17:13:09] <progo> last time I actually tried instagram you were forbidden form posting a new thread in a browser
[17:14:08] <ted-ious> Can you download the video instead?
[17:17:01] <kolie> To restart a video you swipe off and back to it, or refresh the link :)
[17:17:22] <kolie> And people that don't let you seek the videos are time wasters.
[17:17:42] <ted-ious> I don't use instagram at all so I don't even have a link I can test downloading.
[17:18:03] <ted-ious> kolie: Is it a feature that you can disable seeking on a video you post?
[17:18:16] <ted-ious> Or are you just saying in general?
[17:18:17] <kolie> I know that some videos let you do it and some dont.
[17:18:20] <progo> "download?" I assume youtube-dlp would work on this page, if I was convinced to try it. the onus is on the sharer (the one I encountered with the link to instagram) to explain why their followers should care about attachments like this
[17:19:15] <kolie> I don't know what service does that specifically - if its instagram or not. I usually do youtube shorts or very rarely tiktok.
[17:19:22] <kolie> I have throw away accounts for all the social stuff.
[17:19:35] <progo> someone I know has in the past written a very thoughtful essay on their blog space and then linked to it on Mastodon with their private url shortener that doesn't offer any crawlers a title or description. he basically posted "look at this! [personal url shortener link with no info["
[17:20:56] <kolie> I help a lot of people get on those socials though so familiar a bit with all of them.
[17:25:34] <ted-ious> Help them get on?
[17:25:49] <progo> we should help people get off social media :^)
[17:26:16] <progo> unless you count news blogs and IRC as social media
[17:28:28] <fab23> it would probably be better to get them off large commerical platforms where they are the product and not the user
[17:37:35] <kolie> Uhm well - they build their business around it and it's very low barrier for them to do so and they seem to find a lot of success.
[17:39:11] <kolie> Musicians/bands, a florist, a certification/instructor.
[17:39:16] <kolie> Stuff like that.
[17:40:56] <kolie> Lots of eyeballs - they produce content and even a small fraction of those eyes on them - turns into leads and sales and awareness of the person/business.
[17:41:28] <kolie> I've worked with a few rescue organizations and some nfps - growing their awareness via social.
[17:42:16] <kolie> So yea people out there are making it work for them.
[18:07:47] <kolie> all host_addr in the database need to be raised from 32 to 39
[18:09:31] <ted-ious> Why not 40 or 64?
[18:10:07] <kolie> ipv6 => 128 bits, 16 bytes, in hex is 32 characters, plus the ":" is 39
[18:10:46] <ted-ious> Oh ok it's an ip not a hostname.
[18:11:08] <kolie> yea I think the confusion came from conflating them with ipids which are hashes
[19:36:29] <kolie> Ok - my/comments was solved.
[19:36:41] <kolie> can updated prod without any issues and will be doing so shortly.
[20:09:40] -!- norayr [norayr!~norayr@37.252.sq.ypj] has joined #soylent
[20:13:52] <mechanicjay> kolie: was the fix just adding the extra use statement?
[20:15:03] <kolie> for that yes.
[20:15:20] <kolie> btw the uhh. master branch - just got a merge in from production
[20:16:10] <mechanicjay> Saw that, will check it out later
[20:20:05] <kolie> my/comments on dev is confirmed fix - the fix in prod is proving less effective.
[20:21:25] <requerdanos> as long as it works on staging, then a fix is already in the pipeline, right?
[20:22:01] <kolie> Yea well right now prod is fuorine
[20:22:09] <kolie> So until we move prod to it's new shiny setup
[20:22:20] <kolie> We are going to deal with "It works in X but not in Y"
[20:24:49] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has joined #soylent
[20:48:13] <Bytram> kolie: Hi! Just letting you know of a problem on dev. I get an email every 10 minutes (3 times now)"
[20:48:33] <Bytram> begin
[20:48:35] <Bytram> Dev.SN Slashd Error Alert!
[20:48:35] <Bytram> SLASHD line 165 produced the following error:
[20:48:35] <Bytram> update_twitter.pl odd exit (status 25, signal 0)
[20:48:41] <Bytram> end
[20:51:56] <kolie> will disable that.
[20:52:10] <Bytram> ISTR this same msg appearing a few years ago. It went on-and-on-and-on
[20:52:32] <Bytram> great, thanks!
[20:53:21] <kolie> I think this is the same one we are getting on production.
[20:53:33] <Bytram> (Just got another one a couple minutes ago.)
[20:54:21] <requerdanos> fwiw "comments" works for me(tm) on the live site
[20:54:32] <kolie> thx yea that's what the updates are for.
[20:54:35] <kolie> nice.
[20:57:29] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has parted #soylent
[20:58:27] <mechanicjay> kolie: regarding the change from 32 to 39 bits.
[20:58:35] <kolie> whatup
[20:58:59] <mechanicjay> The thing that was attempted, but never quite achieved properly was versioning schema updates so the db was in a known state
[21:00:09] <mechanicjay> so you'll see there's a db schema version I think theres a var which defines the schema version
[21:00:20] <kolie> some kind of stored number with a scan of information_schema and alter table generation.
[21:00:25] <kolie> fun times.
[21:01:03] <mechanicjay> Basically, what was attempted was an update file which would apply the change and update the schema version number
[21:01:09] -!- lilitsyunetsi [lilitsyunetsi!~lilitsyun@37.252.sq.ypj] has joined #soylent
[21:01:20] <kolie> Ok cool!
[21:01:25] <kolie> Definitely useful.
[21:02:13] <mechanicjay> So I think your commit needs to bump that value in the base dump.
[21:02:44] <mechanicjay> Going foward I would like to figure out how to handle schema updates a little more regularly
[21:02:46] <kolie> Ok - I have to think it should've already been in - simply for the reason that the code expected a longer column.
[21:03:15] <kolie> ill bump it and ref the commit hash before.
[21:03:40] <mechanicjay> well the rehash_schema.sql from seemed to still have the old value so <shrug>
[21:04:04] <kolie> yea i didn't bump it.
[21:04:07] <kolie> I will thought.
[21:04:10] <kolie> though*(
[21:04:39] <mechanicjay> the var is the helpfully named 'cvs_tag_currentcode' -- as the db updates are kidna supposed to go with a tag release
[21:05:42] <kolie> im not seing an insert in slashchema create or rehash schema
[21:06:06] <kolie> its in uhh.... defaults.sql though
[21:24:50] <Bytram> kolie: FYI: Still getting that 3-live DevSN message every 10 minutes.
[21:26:18] <kolie> I don't know how to turn it off :)
[21:26:27] <kolie> mechanicjay, input?
[21:26:56] <mechanicjay> Unfortunately I've never heard of this job until today and not sure why they're getting and I'm not
[21:27:07] <mechanicjay> is it coming through the editors@sn exploder?
[21:27:14] <kolie> Its an email that goes out to a list based on that job in slashd erroring.
[21:27:24] <kolie> I need to either stop the job or neuter email in dev.
[21:27:31] <kolie> But I need email to register people in dev.
[21:27:41] <kolie> So more about stopping the job or that job from emailing alerts to people.
[21:28:49] <mechanicjay> Well, what I'm asking is, is that email sending to a list (in which case there's a value somewhere to search on) or to a list of people directly.
[21:29:06] <mechanicjay> maybe it's going out to the group of editors
[21:29:43] <kolie> could be a var slashd uses
[21:30:02] <kolie> adminmail_* or something
[21:30:07] <mechanicjay> if the latter, there's not much to do except figure out how to stop it from sending the email - which woudl require hack, probably to the Slash::Twitter error handle
[21:32:59] <kolie> maybe $slashdb->insertErrnoteLog($taskname, $errnote, $moreinfo); does it
[21:33:24] <kolie> Can you send me the email Bytram
[21:34:26] <mechanicjay> aye, that could be it
[21:34:40] <kolie> it is it puts it in there.
[21:35:13] <kolie> I think we can just remove the task from the ask folder we dont need it on dev.
[21:36:38] <mechanicjay> ya lost me now, where is the task folder?
[21:36:52] * Bytram just got another 3-line message :(
[21:37:04] <mechanicjay> nm, found it
[21:40:43] <Bytram> correction: I just got another 3-line *email*. The entire message contails:
[21:40:54] <Bytram> begn
[21:40:59] <Bytram> Dev.SN Slashd Error Alert!
[21:40:59] <Bytram> SLASHD line 165 produced the following error:
[21:40:59] <Bytram> update_twitter.pl odd exit (status 25, signal 0)
[21:40:59] <Bytram> ----------------------------------------------------------------------
[21:40:59] <Bytram> You have received this message because you subscribed to it
[21:40:59] <karmabot> Bytram, --------------------------------------------------------------------: -1
[21:41:00] <Bytram> on Dev.SN. To stop receiving this and other
[21:41:04] <Bytram> messages from Dev.SN, or to add more messages
[21:41:06] <Bytram> or change your preferences, please go to your user page.
[21:41:08] <Bytram> https://dev.soylentnews.org/my/messages
[21:41:09] <systemd> ^ 03Log In
[21:41:10] <Bytram> You can log in and change your preferences from there.
[21:41:47] <Bytram> end
[21:45:02] <mechanicjay> Bytram: if you go to that page, are any of those message settings set to "email"?
[21:47:24] <Bytram> mechanicjay: Thanks, but I did not change anything.
[21:49:43] <Bytram> why did it suddenly start? why is it sending notice of an ERROR, now?
[21:50:05] <kolie> Because we are fixing broken shit in rehash
[21:50:18] <kolie> Stuff is starting to work again.
[21:50:54] <kolie> I'm updating dev right now to remove the twitter task
[21:51:11] <kolie> Let's see if that 3:00 oclock goes off.
[21:55:17] <Bytram> ok, thanks a bunch!
[21:56:32] <kolie> janrinok, wiki isn't erroring anymore.
[22:00:56] <kolie> Ok production update_twitter.pl ran and errored like it should, im checking what dev. did
[22:01:21] <kolie> it looks like it sent it out too.
[22:02:34] <kolie> Well I gotta head out - I got my kids this weekend so I'm off unless its a 911 till monday. mechanicjay not sure if you can do anything about it. I'll let NC know.
[22:07:31] <Bytram> kolie: Uhh, who is your standin while you are away?
[22:07:49] <kolie> I'm around if people want my #
[22:08:05] <kolie> mj can poke dev.
[22:08:15] <kolie> NC too.
[22:08:51] <kolie> NC is fully apprised of everything going on rn - hes the one making the code updates on prod.
[22:09:42] <Bytram> thanks! enjoy your kids!!
[22:13:52] <kolie> lmk if you get another - last ditch so you don't get spam over the weekend.
[22:14:07] <kolie> Next one goes out at 10:20PM UTC
[22:16:54] <Bytram> heh; it's 18:26 RN
[22:17:30] <Bytram> (will do)
[22:18:00] <Bytram> https://www.youtube.com
[22:18:01] <Bytram> https://www.youtube.com
[22:18:01] <systemd> ^ 03Dog Had Enough of Zoomy! - RxCKSTxR Comedy Voiceover
[22:18:02] <systemd> ^ 03Never Give Up! - RxCKSTxR Comedy Voiceover!
[22:18:42] <Bytram> try not to laugh!
[22:29:00] <Bytram> yup, I got yet anther email.