code logs -> 2019 -> Wed, 29 May 2019< code.20190528.log - code.20190530.log >
--- Log opened Wed May 29 00:00:59 2019
00:16 Vorntastic [uid293981@Nightstar-6br85t.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity]
00:37 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Ping timeout: 121 seconds]
00:57 himi [sjjf@Nightstar-1drtbs.anu.edu.au] has joined #code
00:57 mode/#code [+o himi] by ChanServ
01:27 Kindamoody|afk is now known as Kindamoody
01:57 celmin|away is now known as celticminstrel
02:16 Kindamoody is now known as Kindamoody[zZz]
02:41 Alek [Alek@Nightstar-o723m2.cicril.sbcglobal.net] has quit [[NS] Quit: brb]
02:42 Alek [Alek@Nightstar-o723m2.cicril.sbcglobal.net] has joined #code
02:42 mode/#code [+o Alek] by ChanServ
04:01
<&McMartin>
delete(pop); return 3
04:02
< Mahal>
I have successfully automated the generation of a 'random' password for our BYOD networks, the script necessary to upload same using the Meraki APIs, and the creation of a QR code that uplaods same to the relevant place in Sharepoint
04:02
< Mahal>
I'm quite pleased
04:36 celticminstrel [celticminst@Nightstar-1kpqgc.dsl.bell.ca] has quit [[NS] Quit: And lo! The computer falls into a deep sleep, to awake again some other day!]
05:50 gnolam [quassel@Nightstar-csto10.cust.bahnhof.se] has joined #code
05:50 mode/#code [+o gnolam] by ChanServ
06:22 gnolam [quassel@Nightstar-csto10.cust.bahnhof.se] has quit [[NS] Quit: Gone]
08:11 himi [sjjf@Nightstar-1drtbs.anu.edu.au] has quit [Ping timeout: 121 seconds]
08:30 Pinkhair [user1@Nightstar-g7hdo5.dyn.optonline.net] has joined #code
08:31 Pink [user1@Nightstar-g7hdo5.dyn.optonline.net] has quit [Ping timeout: 121 seconds]
09:27 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
09:27 mode/#code [+qo Vornicus Vornicus] by ChanServ
09:51 Kindamoody[zZz] is now known as Kindamoody
10:44
<@ErikMesoy>
What kind of SQL table dysfunction might be the cause if a LEFT JOIN on two tables takes hours, but an INNER JOIN, RIGHT JOIN or FULL OUTER JOIN on the same tables takes seconds?
10:49
<@TheWatcher>
Paging Dr Reiver~
10:53
<&Reiver>
lol
10:53
<&Reiver>
sup
10:53
<&Reiver>
uh
10:54
<&Reiver>
That a full outer join is fine is the weird one
10:55
<&Reiver>
Check the execution plan, it could have a maladaption or be attempting to scan an unindexed column in a weird way, though why it wouldn't do the same on other joins is beyond me at first glance
10:56 * Reiver ponders
10:56
<@ErikMesoy>
Yeah, common sense tells me the left join should go faster than the outer join, the other two are mentioned mostly as a matter of "I tested the obvious alternatives"
10:56
<&Reiver>
This is just a naked join, right? SELECT foo FROM bar LEFT JOIN baz ON bar.bit = baz.bit ?
10:56
<&Reiver>
No WHERE Clause fucking things up, turning the LEFT JOIN into an implicit INNER by accident?
10:57
<&Reiver>
Because you might then be earning yourself a really /inefficient/ inner join through reasons unknown, and that could ruin things
10:57
<&Reiver>
But honestly when things go so horribly wonky it's usually teh optimizer, er, being suboptimal
10:57
<&Reiver>
I had it once
10:58
<&Reiver>
I cunningly obscuficated the code to be less efficient, and it ran in ten seconds instead of seven minutes... even if the inital code should have taken like two seconds, tops -_-
10:59
<&Reiver>
Possible obscufications: Subqueries instead of joins, turning it into a FULL OUTER JOIN with implicit restrictions elsewhere in the WHERE, even, depending on the software, really stupid shit like just flipping to a RIGHT JOIN and seeing what happens
10:59
<&Reiver>
(hint: It should in theory be the same, buuut...)
11:02 * ErikMesoy squints very closely, notices that this query is SELECT foo FROM bar (...) ON foo =
11:03
<@ErikMesoy>
Four different people have now been by the office trying to puzzle out what is with this query. :V
11:10
<&Reiver>
bahahahahaha
11:10
<&Reiver>
Oh lord, I didn't /help/, did I
11:15 * TheWatcher eyes this workshop advert from work
11:15
<@TheWatcher>
"Why don’t organisations manage their cyber resilience well enough to remain trusted by stakeholders in the face of relentless cyber-attacks?"
11:16
<@TheWatcher>
It's a 5 hour workshop.
11:16
<@TheWatcher>
5 hours
11:18
<@TheWatcher>
The answer is fucking simple: doing it right is really fucking hard, very expensive, hugely inconvenient for users, and ultimately futile because everything they're building on is shit.
11:19
<&Reiver>
And you know that workshop will be 4 and a half hours of sales pitch for The Latest Solution That Solves Everything, Honest (hint: it's shit)
11:51 You're now known as TheWatcher[d00m]
12:09 bluefoxx_ [fuzzylombax@Nightstar-gmbj85.vs.shawcable.net] has quit [Ping timeout: 121 seconds]
12:16 bluefoxx [fuzzylombax@Nightstar-gmbj85.vs.shawcable.net] has joined #code
13:19 Kindamoody is now known as Kindamoody|afk
13:36 bluefoxx [fuzzylombax@Nightstar-gmbj85.vs.shawcable.net] has quit [Ping timeout: 121 seconds]
13:43 bluefoxx [fuzzylombax@Nightstar-gmbj85.vs.shawcable.net] has joined #code
14:43 celticminstrel [celticminst@Nightstar-1kpqgc.dsl.bell.ca] has joined #code
14:43 mode/#code [+o celticminstrel] by ChanServ
15:38 You're now known as TheWatcher
15:45 gnolam [lenin@Nightstar-hfrbpd.cust.bahnhof.se] has joined #code
15:45 mode/#code [+o gnolam] by ChanServ
16:59 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code
17:13 Pinkhair [user1@Nightstar-g7hdo5.dyn.optonline.net] has quit [Connection reset by peer]
17:13 Pink [user1@Nightstar-g7hdo5.dyn.optonline.net] has joined #code
17:32
<&jeroud>
I built a thing today: https://github.com/praekeltfoundation/gitsecal
17:33
<&jeroud>
I hope (and expect) that it is of absolutely no use to anyone in here for primary design purpose.
17:35
<&jeroud>
(Also the why-it-actually-got-built purpose, which is that I needed to create a thing that would provide a sense of completion and achievement without drowning in frustration and tears.)
17:43 * Emmy nods sagely
17:43
< Emmy>
I understand some of these words
17:47
<&jerith>
The history behind that is that github now scans project dependencies for security issues and sends alerts.
17:47
<&jerith>
But the alerts only go to repo admins and organization owners.
17:48
<&jerith>
For various reasons, many of my employer's repos don't have anyone with admin privs. When admin stuff is needed one of the org owners does it.
17:49
<&jerith>
So most of the people who should be seeing the security alerts aren't.
17:51
<&jerith>
There's also no way to access security alerts without looking at each repo individually.
17:51
<&jerith>
When there are several hundred repos, this isn't practical.
18:44 Lamb3 [Dawg@Nightstar-52ic2g.wechall.net] has quit [[NS] Quit: bad karma for samurai killing people in #shadowlamb mmo. brb]
18:47 Lamb3 [Dawg@Nightstar-52ic2g.wechall.net] has joined #code
19:05 Lamb3 [Dawg@Nightstar-52ic2g.wechall.net] has quit [[NS] Quit: Fatal PHP Error :O]
19:20 Lamb3 [Dawg@Nightstar-52ic2g.wechall.net] has joined #code
21:04
< Emmy>
So you made a tool so that at least that job got easier for the owners/admins
21:14 Netsplit Deepthought.Nightstar.Net <-> Krikkit.Nightstar.Net quits: @PinkFreud
22:07 catalyst [Jessikat@Nightstar-5dv16h.cable.virginm.net] has joined #code
22:14 Degi [Degi@Nightstar-ukam1p.dyn.telefonica.de] has joined #code
22:27 Kindamoody|afk is now known as Kindamoody
22:43 PinkFreud [WhyNot@NetworkAdministrator.Nightstar.Net] has joined #code
22:44 mode/#code [+o PinkFreud] by ChanServ
23:36 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Ping timeout: 121 seconds]
23:48 Netsplit Deepthought.Nightstar.Net <-> Krikkit.Nightstar.Net quits: @PinkFreud
--- Log closed Thu May 30 00:00:00 2019
code logs -> 2019 -> Wed, 29 May 2019< code.20190528.log - code.20190530.log >

[ Latest log file ]