code logs -> 2018 -> Wed, 10 Jan 2018< code.20180109.log - code.20180111.log >
--- Log opened Wed Jan 10 00:00:20 2018
01:04 Derakon[AFK] is now known as Derakon
01:10 Kindamoody|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code
01:10 mode/#code [+o Kindamoody|autojoin] by ChanServ
01:10 Kindamoody|autojoin is now known as Kindamoody
01:16 Kindamoody is now known as Kindamoody[zZz]
02:51 Alek [Alek@Nightstar-7or629.il.comcast.net] has quit [Ping timeout: 121 seconds]
02:54 Alek [Alek@Nightstar-7or629.il.comcast.net] has joined #code
02:54 mode/#code [+o Alek] by ChanServ
03:07
<&[R]>
Ugh... I swear, I've have more issues with my work computer running MS shit than I've had with Arch (which I left because it kept routinely fucking up horribly)
03:09
<&McMartin>
What kinds of issues does Arch run into?
03:10
<&[R]>
Cyclical dependencies between kernel and libc, and they only keep the latest version in the repo. Forget the exact issue but basically prevent me from updating my systems
03:12
<&McMartin>
That seems like a rather serious problem for something that claims to be rolling-release.
03:14
<&[R]>
Also at one point they made their package manager depend on openssl (when it actually shells out the downloads). The reason for the /hard/ openssl dependency? 15% speed increase in MD5 calculation. IE: they had working MD5 calculation code in the codebase. Openssl rolled over from 0.9.8.6 to 1.0.0, all the .so symlinks changed, API changed in a breaking way so you couldn't even make a symlink to fix it.
03:14
<&[R]>
0.9.8g*
03:14
<&[R]>
They also didn't do the "let's shove /everything/ into /usr" rollout very well either.
03:15
<&[R]>
Basically, IMO, an endless stream of fuckups after the original dev left.
03:19
< Mahal>
<random> can you run an RPi with PoE?
03:20
<&McMartin>
EAP PoE?
03:20
<&McMartin>
Oh, Power over Ethernet?
03:20
<&McMartin>
I don't believe so. It's got one of those 3.5mm power jacks.
03:21
<&McMartin>
Er, wait, no. It's microUSB
03:21
<&McMartin>
So you can: https://www.amazon.com/dp/B01M1E3VC8/ref=asc_df_B01M1E3VC85330949/?tag=hyprod-20&creative=395033&creativeASIN=B01M1E3VC8&linkCode=df0&hvadid=198138936631&hvpos=1o1&hvnetw=g&hvrand=9008207341794277138&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9031926&hvtargid=pla-412883840807
03:25
<&McMartin>
But you can't just plug it into a network hub and go to town.
03:25
<&McMartin>
With its own ethernet port, tha tis.
03:25
<&McMartin>
(I think the Pi0 might not even *have* an ethernet port.)
03:26
<&McMartin>
[R]: Wow, that's even worse than Gentoo
03:27
<&[R]>
I broke Gentoo too
03:27
<&McMartin>
So did I
03:27
<&[R]>
Apparently I'm not supposed to "emerge portage"
03:27
<&[R]>
*shrugs*
03:27
<&McMartin>
But at least revdep-rebuild mostly worked
03:28
<&[R]>
Also holy fuck MS. A three stage update? Fuck your manditory file locking D:
03:50 himi [sjjf@Nightstar-dm0.2ni.203.150.IP] has quit [Operation timed out]
04:08 himi [sjjf@Nightstar-ptu.mv5.56.130.IP] has joined #code
04:08 mode/#code [+o himi] by ChanServ
05:06 Derakon is now known as Derakon[AFK]
05:26 [ [art@Nightstar-lbl.59v.61.68.IP] has quit [Ping timeout: 121 seconds]
05:31 [ [art@Nightstar-lbl.59v.61.68.IP] has joined #code
05:41 macdjord [macdjord@Nightstar-ahbhn1.cable.rogers.com] has quit [[NS] Quit: Wenn ist das Nunstück git und Slotermeyer? Ja! Beiherhund das Oder die Flipperwaldt gersput!]
05:56 himi [sjjf@Nightstar-ptu.mv5.56.130.IP] has quit [Ping timeout: 121 seconds]
06:44 Vornlicious [Vorn@Nightstar-vqssiu.sub-174-210-0.myvzw.com] has joined #code
06:47 Vorntastic [Vorn@Nightstar-1l3nul.res.rr.com] has quit [Ping timeout: 121 seconds]
07:48 Vornlicious [Vorn@Nightstar-vqssiu.sub-174-210-0.myvzw.com] has quit [The TLS connection was non-properly terminated.]
08:06 crystalclaw [crystalclaw@Nightstar-12q9ui.xyz] has quit [Ping timeout: 121 seconds]
08:06 Kindamoody[zZz] is now known as Kindamoody
08:09 crystalclaw [crystalclaw@Nightstar-12q9ui.xyz] has joined #code
08:09 mode/#code [+o crystalclaw] by ChanServ
08:11 Vorntastic [Vorn@Nightstar-uqhcfj.sub-174-210-2.myvzw.com] has joined #code
08:34 [ [art@Nightstar-lbl.59v.61.68.IP] has quit [Ping timeout: 121 seconds]
08:36 [ [art@Nightstar-lbl.59v.61.68.IP] has joined #code
09:24 Vash [Vash@Nightstar-1l3nul.res.rr.com] has joined #code
11:15 himi [sjjf@Nightstar-v37cpe.internode.on.net] has joined #code
11:15 mode/#code [+o himi] by ChanServ
12:56 Vornotron [Vorn@Nightstar-1l3nul.res.rr.com] has quit [Ping timeout: 121 seconds]
13:32 [ [art@Nightstar-lbl.59v.61.68.IP] has quit [Ping timeout: 121 seconds]
13:37 [ [art@Nightstar-lbl.59v.61.68.IP] has joined #code
14:08 Kindamoody is now known as Kindamoody|afk
14:58 Degi [Degi@Nightstar-4puh6e.dyn.telefonica.de] has joined #code
15:29 Vornotron [Vorn@Nightstar-1l3nul.res.rr.com] has joined #code
15:29 mode/#code [+qo Vornotron Vornotron] by ChanServ
15:32 Vorntastic [Vorn@Nightstar-uqhcfj.sub-174-210-2.myvzw.com] has quit [[NS] Quit: Bye]
15:32 Vorntastic [Vorn@Nightstar-1l3nul.res.rr.com] has joined #code
16:36
<@TheWatcher>
Finding out which branch a given commit was made on in git: surprisingly hard to do reliably!
17:02
<@TheWatcher>
snerk https://twitter.com/doctorow/status/951110188106436608
17:20 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code
17:43
<&ToxicFrog>
Especially since the answer might be multiple branches, or "none of them"
17:44
<@TheWatcher>
Yeah
17:44
<@TheWatcher>
Especially as I'm trying to work it out for commits after fast-forward merges
17:50
<&McMartin>
Since Git hides this information, this is obviously a piece of information you should not want!
17:53
<&ToxicFrog>
In general, if you need this information ex post facto, you need a commit hook or similar that annotates the commit with it.
17:54
<&ToxicFrog>
If you're content with "what branch was this user on, if any, when they originally made the commit" without a deeper look at the graph, and it was relatively recent (in the past month, by default), the reflog may help there.
17:56
<@TheWatcher>
Basic thing is that we've got a bunch of student repositories from 2015 and 2016 that we need to annotate in various ways, and then throw through jenkins to get build metrics for (all as part of work towards a paper)
17:57
<@TheWatcher>
These're all in gitlab, which does handily record a lot of what we need... from the upgrade I did at the start of 2017.
18:00
<@TheWatcher>
So I've been doing various things inside the bare repos, like working when pushes happened using timestamps in the git object databases and detecting forced pushes
18:02
<@TheWatcher>
But we also want various other bits of data, including which branch commits happened on, and I think I'm just going to have to look at the tree objects to rebuild the graph and use that
18:21 Vash [Vash@Nightstar-1l3nul.res.rr.com] has quit [Ping timeout: 121 seconds]
18:44
<&ToxicFrog>
That's definitely not sufficient in the general case, since branch pointers can be created or deleted after the commit is made, and the branch names on the server may not match the ones used locally
19:27 Kindamoody|afk is now known as Kindamoody
19:58 Degi_ [Degi@Nightstar-plekkr.dyn.telefonica.de] has joined #code
20:01 Degi [Degi@Nightstar-4puh6e.dyn.telefonica.de] has quit [Ping timeout: 121 seconds]
20:12 Vornotron [Vorn@Nightstar-1l3nul.res.rr.com] has quit [Ping timeout: 121 seconds]
20:22 Degi_ is now known as Degi
20:50
<&McMartin>
https://arstechnica.com/information-technology/2018/01/emc-vmware-security-bugs-throw-gasoline-on-cloud-security-fire/
21:03
<@TheWatcher>
I like the tweet quoted in there "over 100 exposed so far in china, russia, ukraine" while ignoring the big swathes of deep red in germany, france, spain, and the UK~
21:03
<@TheWatcher>
That said, sigh
21:30 macdjord [macdjord@Nightstar-a1fj2k.mc.videotron.ca] has joined #code
21:30 mode/#code [+o macdjord] by ChanServ
22:48 Degi [Degi@Nightstar-plekkr.dyn.telefonica.de] has quit [[NS] Quit: Leaving]
23:31 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Ping timeout: 121 seconds]
23:37
<&[R]>
<Nomikos> this isn't about raspberry pi as much, but it's a good explain-read https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/
23:38
<&McMartin>
ARM's technical writings on this stuff have been top-notch
23:40
<&McMartin>
That also said, :( of a sort at Patterson and Hennesy still being the cutting-edge primer
23:41
<&McMartin>
That book was old when I took the class that used it
23:41
<&McMartin>
And that was twenty years ago
23:41
<&McMartin>
Oops, wait, I didn't take that class
23:42
<&McMartin>
I took the prep class for it but not the class itself
23:42
<&McMartin>
Same authors, different book
23:42
<&McMartin>
(Computer Organization and Design: the Hardware/Software Interface)
23:43
<&McMartin>
Having read that article, though, I endorse that article
23:47
<&McMartin>
It isn't quite ELI5, but it's a very solid ELI14
23:48
< Mahal>
I like this one too: https://ds9a.nl/articles/posts/spectre-meltdown/
23:48
< Mahal>
closer to eli5
23:58 Kindamoody is now known as Kindamoody[zZz]
--- Log closed Thu Jan 11 00:00:22 2018
code logs -> 2018 -> Wed, 10 Jan 2018< code.20180109.log - code.20180111.log >

[ Latest log file ]