code logs -> 2017 -> Tue, 30 May 2017< code.20170529.log - code.20170531.log >
--- Log opened Tue May 30 00:00:28 2017
02:12 Alek [Alek@Nightstar-7or629.il.comcast.net] has quit [Ping timeout: 121 seconds]
02:15 Alek [Alek@Nightstar-7or629.il.comcast.net] has joined #code
02:15 mode/#code [+o Alek] by ChanServ
02:47 Alek [Alek@Nightstar-7or629.il.comcast.net] has quit [Ping timeout: 121 seconds]
02:51 Alek [Alek@Nightstar-7or629.il.comcast.net] has joined #code
02:51 mode/#code [+o Alek] by ChanServ
04:10 Turaiel[Offline] is now known as Turaiel
04:45 ion [Owner@Nightstar-gmbj85.vs.shawcable.net] has quit [Connection closed]
04:45 ion [Owner@Nightstar-gmbj85.vs.shawcable.net] has joined #code
05:06 Turaiel is now known as Turaiel[Offline]
05:46 celticminstrel is now known as celmin|sleep
08:30
<&[R]>
rand() isn't available in cstdlib?
08:30
<&[R]>
(C++)
08:35
<~Vornicus>
Should be in there?
08:35
<~Vornicus>
http://www.cplusplus.com/reference/cstdlib/ I don't think this is necessarily authoritative but
08:36
<~Vornicus>
There is also the random lib
08:36
<&[R]>
Oh, found the issue, function was being called in the header, where cstdlib wasn't being included
08:36
<&[R]>
Huzzah for release code having compile bugs.
08:36
<~Vornicus>
(but that's only in C++11)
08:37
<~Vornicus>
derp
08:54 * [R] notices the build doesn't actually give a runnable binary, just a library. Docs refer to /two/ binaries it's supposed to make
08:54
<&[R]>
Clusterfuck of a autotools generated makefile look like they indeed do not compile the binaries.
08:54
<&[R]>
Check the Changelog.
08:55
<&[R]>
Come to the conclusion that "final changes/additions for gnu build compatibility" means "break everything"
08:58 * [R] reverts back to a version before he started working on "gnu build compatibility", notices the rand() issue again.
09:00
<&[R]>
Okay, this one fully compiles. \o/
09:12 Kindamoody[zZz] is now known as Kindamoody
09:50 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Ping timeout: 121 seconds]
10:08 Kindamoody is now known as Kindamoody|afk
10:18
<&[R]>
#include <cstdio> //for file handling
10:18
<&[R]>
#include <iostream> //for console traffic
10:18
<&[R]>
...
10:32
<@abudhabi>
Problem, comrade? ;)
10:38
<&[R]>
This codebase is absolutely horrible
10:40
<@abudhabi>
Preaching the choir. I'm working on something that's been through X teams trying to upgrade it for XX years.
10:40
<@abudhabi>
(Details unavailable due to NDA.)
10:40
<&[R]>
Fair enough
10:41
<&[R]>
This reeks of student project code.
10:41
<&[R]>
So you win :p
10:41
<@abudhabi>
:V
10:55 Reiver [quassel@Nightstar-ksqup0.co.uk] has quit [Connection closed]
10:55 Orthia [quassel@Nightstar-ksqup0.co.uk] has quit [Connection closed]
10:55 Orthia [quassel@Nightstar-ksqup0.co.uk] has joined #code
10:55 mode/#code [+o Orthia] by ChanServ
10:55 Reiver [quassel@Nightstar-ksqup0.co.uk] has joined #code
10:55 mode/#code [+ao Reiver Reiver] by ChanServ
11:07
<&[R]>
<frinnst> I tell the web developer to use su <user> to lower privileges for adding a crontab job. he insists on using "sudo crontab -e" as the unprivileged user
11:12
<&[R]>
D:
11:12
<&[R]>
Nested ifs with inconsitient indentation and only have of them have braces
11:13
<@TheWatcher>
... kill
11:21
<&[R]>
I think I've seen this exact same conditional and the exact same code block following it about nine times now
11:49
<&[R]>
int scale = 4 + scaleModifier;
11:49
<&[R]>
if (scale < 2)
11:49
<&[R]>
scale = 2;
11:49
<&[R]>
Actually... I guess that's not that silly since scaleModifier can be negative.
12:04
<@TheWatcher>
Although, if you've seen it more than once, I'd argue it should be in a function~
12:08
<&[R]>
It involves a goto
12:08
<&[R]>
So I'm not sure if that'll behave correctly.
12:11
<&ToxicFrog>
int scale = max(2, 4 + scaleModifier);
14:11
<@abudhabi>
Somewhere along the way since starting work here three months ago, I have acquired Domain Knowledge.
14:24
<&ToxicFrog>
It creeps up on you like that.
14:25
<@abudhabi>
Suddenly, people are asking me to look at arcane things and I often know the answer too.
14:42
<@TheWatcher>
Careful, that way leads being responsible for things...
16:34 VirusJTG [VirusJTG@Nightstar-6i5vf7.sta.comporium.net] has quit [Connection closed]
16:34 VirusJTG [VirusJTG@Nightstar-6i5vf7.sta.comporium.net] has joined #code
16:34 mode/#code [+ao VirusJTG VirusJTG] by ChanServ
17:22 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
17:22 mode/#code [+qo Vornicus Vornicus] by ChanServ
17:26 iospace [Alexandria@Nightstar-fkokc2.com] has quit [Ping timeout: 121 seconds]
17:27 iospace [Alexandria@Nightstar-fkokc2.com] has joined #code
17:27 mode/#code [+o iospace] by ChanServ
17:52 Kindamoody|afk is now known as Kindamoody
19:56 macdjord [macdjord@Nightstar-a1fj2k.mc.videotron.ca] has joined #code
19:56 mode/#code [+o macdjord] by ChanServ
20:07
<&jeroud>
https://twitter.com/MichelePlayfair/status/869171522941861888
20:08
<&jeroud>
I am prepared for my return to the task of automating a Swift deployment tomorrow. https://usercontent.irccloud-cdn.com/file/0qDGpPFB/IMAG0666_1.jpg
20:10
<@gnolam>
:-)
20:12
<&McMartin>
The 'Swift' I'm familiar with isn't a technology one deploys. What is this?
20:13
<&jeroud>
The object store part of OpenStack.
20:14
<&jeroud>
It is one of the few components of OpenStack that doesn't have a hard dependency on all the rest of OpenStack, so at least the pain is somewhat limited by that.
20:16
<&jeroud>
(I believe that lack of hard dependency is due to it originally being a standalone thing that was assimilated.)
20:19
<&jeroud>
As an example of how terrible this stuff is: Last week I ended up watching a video of a conference talk explaining how to use an automation tool for deploying it, because neither the documentation for that tool nor the documentation for Swift gave me any hints as to what I should be doing.
20:23
<&jeroud>
OpenStack has many tens or hundreds of thousands of words of documentation. None of it useful to anyone who doesn't already have the information it is intended to convey.
21:50 Turaiel[Offline] is now known as Turaiel
22:11 macdjord [macdjord@Nightstar-a1fj2k.mc.videotron.ca] has quit [[NS] Quit: FLEET: We *are* shining examples of humanity. It's just that the light we shine with is generally Oppenheimer's. ]
22:24 macdjord [macdjord@Nightstar-a1fj2k.mc.videotron.ca] has joined #code
22:24 mode/#code [+o macdjord] by ChanServ
23:15
<@himi>
jeroud: Reading the puppet code tends to be the most effective way to figure out what it does
23:17
<&jerith>
himi: The puppet code is what I was watching the conference talk about.
23:17
<&jerith>
It's... convoluted.
23:18
<@himi>
Huh
23:18
<@himi>
Puppet code, being convoluted?
23:18
<@himi>
Damn, I'd never have thought
23:18
<&jerith>
And underdocumented. Even for puppet code.
23:19 * himi has just spent months trying to get a fairly basic OpenStack deployment built and integrated
23:19
<&jerith>
I *could* grovel through all the Ruby stuff and whatnot, but that would only tell me half of what I need anyway.
23:19
<&jerith>
himi: My deepest condolences. :-(
23:20
<@himi>
Yeah, it's not my idea of fun
23:20
<@himi>
However, it does pay the bills
23:21
<&jerith>
The bit I need to tackle tomorrow is figuring out how to set up the rings.
23:21
<@himi>
I can probably help with a fairly decent range of OpenStack questions if you're in need of it
23:21
<@himi>
Swift is the bit I /can't/ help with - we don't use it
23:21
<&jerith>
Can those be built independently on each machine, or do I need to do it once and then ship the files around? That sort of thing.
23:23
<@himi>
If you want I can forward your questions to people I know who run a fairly large federated swift cluster
23:23
<&jerith>
We use DC/OS for the run-programs-that-do-things bits, but it turns out we need an object store as well.
23:23
<&jerith>
himi: Thanks for the offer, but I'll probably be able to figure it out on my own soon enough.
23:24
<&jerith>
If I don't come right tomorrow, I may take you up on that. :-)
23:24
<@himi>
If you're looking to run stuff on top of ceph I can help with getting the rados gateway set up
23:26
<&jerith>
I looked at ceph, but it was too heavy for our needs.
23:27
<&jerith>
We use glusterfs for persistence at the moment, and that's good enough for the things we're using it for.
23:27
<&jerith>
Although, like all shared filesystem things, it has some serious issues that we're mostly managing to avoid.
23:28
<&jerith>
Unfortunately we have something like a thousand containers running, and maybe half of them need persistence.
23:29
<&jerith>
Gluster's per-volume memory requirements mean that really doesn't scale up very well.
23:29 JustBob [justbob@Nightstar.Customer.Dissatisfaction.Administrator] has quit [[NS] Quit: ]
23:29
<&jerith>
For *most* of the persistence, an object store would actually be a much better fit than a shared filesystem, which is where Swift somes in.
23:30
<&jerith>
*comes
23:40 JustBob [justbob@ServerAdministrator.Nightstar.Net] has joined #code
23:40 mode/#code [+o JustBob] by ChanServ
23:59 himi [sjjf@Nightstar-v37cpe.internode.on.net] has quit [Ping timeout: 121 seconds]
--- Log closed Wed May 31 00:00:29 2017
code logs -> 2017 -> Tue, 30 May 2017< code.20170529.log - code.20170531.log >

[ Latest log file ]