IRC log for #brlcad on 20080113

00:34.43 *** join/#brlcad yukonbob (n=yukonbob@S0106000475d6c028.cg.shawcable.net)
01:52.42 *** join/#brlcad vedge (i=vedge@vedge.org)
02:42.47 *** join/#brlcad SWPadnos (n=Me@dsl107.esjtvtli.sover.net)
02:47.41 *** join/#brlcad Twingy (n=justin@74.92.144.217)
07:08.15 *** join/#brlcad Z80-Boy (i=clock@77-56-94-70.dclient.hispeed.ch)
12:38.31 *** join/#brlcad elite01 (n=elite01@dslb-088-070-016-177.pools.arcor-ip.net)
12:46.07 *** join/#brlcad MinuteElectron (n=MinuteEl@silentflame/member/pdpc.base.minuteelectron)
13:35.57 *** join/#brlcad Elperion (n=Bary@p548742BC.dip.t-dialin.net)
13:52.33 curious hmm. can brlcad operate on photors/using dynamic space-time domain?
13:54.17 curious http://www.islandia.is/gko/EMNG04-moment.pdf photors as defined here
14:08.12 *** join/#brlcad poolio (n=poolio@bz.bzflag.bz)
14:08.15 poolio :o
14:08.54 ``Erik O.o
14:12.09 poolio I'm disappointed by mbo's uptime :P
14:14.41 ``Erik "mbo"?
14:47.29 poolio my.brlcad.org
15:33.53 *** join/#brlcad brlcad (n=sean@bz.bzflag.bz)
15:34.06 brlcad wtf
15:39.39 *** join/#brlcad brlcad (n=sean@bz.bzflag.bz)
15:58.16 brlcad well that sucks, but apparently the ISP had a major power outage that lasted several hours, exhausting their backup power capacities too
16:00.47 louipc ouch
17:01.49 *** join/#brlcad Elperion (n=Bary@p548742BC.dip.t-dialin.net)
17:44.59 *** join/#brlcad jgay (n=jgay@fsf/staff/jgay)
18:36.38 brlcad well, there's a response on scan.coverity.com regarding our Coverity report
18:37.26 brlcad we fall into that category of the projects that include other projects, related to why it's taking so long for them to get a new scan going
18:44.27 yukonbob brlcad: re: coverity, is it possible to just submit the original files instead of the third-party support files?
18:45.49 yukonbob ie: Tcl is already being scanned itself (and happens to be one of 11 projects in rung2, the hightest to day ;), and things like the utah raster, tcl extensions, etc. would be nice to test, but do they present too much interference to getting the original code (ie: librt) tested?
18:46.05 yukonbob *highest to date
18:50.26 *** join/#brlcad MinuteElectron (n=MinuteEl@silentflame/member/pdpc.base.minuteelectron)
18:51.32 MinuteElectron Did something happen recently, my screen session went dead and some of my settings appear to have been altered.
18:52.51 MinuteElectron That is quite ironic.
18:52.57 yukonbob how so?
18:53.50 MinuteElectron The server was taken offline a hundred or so days ago to install something to do with power, probably unrelated but if it is it just shows that meddling with something that works isn't a great idea.
18:54.21 CIA-30 BRL-CAD: 03brlcad * r29891 10/brlcad/trunk/misc/macosx/openUp.c: quell ohloh APSL license detection since we can't yet specify (to ohloh) that it should ignore/exempt some files/dirs
18:55.12 yukonbob brlcad was saying the outage was a long one, and so exhausted their backups -- maybe the 100-day-ago issue was to install the backup; if that's the case, it's only "unfortunate" that the backups couldn't handle that length of outage...
18:56.00 yukonbob as long as the host expected to be losing power soon, and could gracefully shutdown before just having it's juice exhausted...
18:56.26 MinuteElectron Ahh, ok.
19:20.05 brlcad yukonbob: that's the problem with the scans in general, and why ours hasn't updated -- they've been looking at how to exempt those dependency projects from the scans
19:20.14 brlcad we're not the only project like that
19:21.08 brlcad they don't just do a static analysis either, they need to be able to compile as their checker basically is a compiler doing path analyses
19:22.25 brlcad MinuteElectron: yeah, the machine lost power (all machines at the ISP (hundreds) lost power) due to a major outage
19:23.03 brlcad the thing 100 days ago or so was a new UPS for our rack and a new remote reboot port
19:23.55 brlcad this was power coming from the grid that failed, and the brownout lasted several hours
19:24.39 MinuteElectron Too bad, although you would think the ISP would have adaquete backups even for a very long power outage since I wouldn't be suprised if there were several mission-critical systems hosted by them/
19:24.50 brlcad from what I've read the UPS' only held up an hour or so, and they had problems with keeping the main facility diesel backup generator running due to a faulty valve
19:25.02 brlcad they did, the backups failed :)
19:25.13 brlcad rather, the backups of the backups
19:25.42 MinuteElectron XD
19:26.45 brlcad yeah, they have way bigger customers than us, multimillion dollar customers, that lose major money when anything goes down
19:27.22 yukonbob !gah -- they better have a good insurance policy for that...
19:27.56 yukonbob (or perhaps whatever electricity they could generate went to those customers)
19:29.38 yukonbob re: coverity -- ah -- too bad (for us) -- do we need permission (from project maintainers) to have utah raster lib (for example) run through coverity -- I know you need permission to join a coverity project and see the results...
19:30.42 brlcad many massive data centers like sago's have agreements with the power company that compensates them if they're down more than N minutes a year
19:31.02 brlcad dunno if sago has that in place, but they should.. even still, it happens
19:31.36 brlcad even the rackspace kings had major downtime just this past fall for several hours when a truck crashed into one of their transformers
19:32.16 brlcad http://www.rackspace.com/information/announcements/datacenter.php fun fun :)
19:32.24 brlcad cost them millions
19:33.58 brlcad yukonbob: as for coverity and permissions.. huh??? :) no
19:34.47 brlcad the permission is permission *from coverity* as they only want to scan projects that they approve, they don't want to be scanning every open source project out there or (worse) commercial customers for free
19:35.44 brlcad they're paid by uncle sam to scan open source projects
19:36.12 yukonbob brlcad: but I (yukonbob) can't take a look at the scan results for any project I want... I need permission from the project leads (like I need permission to commit to the BRL-CAD cvs/svn)...
19:36.18 louipc # We have made changes to the leadership and staff at our DFW Data Center.
19:36.20 louipc uh oh
19:36.47 brlcad yukonbob: oh sure, that's just the nature of their scanning system though
19:37.05 brlcad I'd give you an account if I could, but the whole login system is actually down at the moment ever since the news went up
19:37.30 yukonbob right -- but is there an issue with BRL-CAD submitting 3rd party code and getting access to the results?
19:37.49 brlcad just a technical issue
19:37.59 yukonbob ie: I myself can't say "lets put OpenBSD up there" and then have access to the OpenBSD bug list...
19:38.06 brlcad the report includes issues in all the 3rd party code as well as our code
19:38.36 brlcad yukonbob: you could request it -- I requested that BRL-CAD be added
19:39.03 brlcad but he's likely not going to approve someone not "in charge" of a given project, unless it's one of the unclaimed rung 0 projects
19:39.16 yukonbob I did request NetBSD be put up -- but I don't have access to the bug list...
19:39.28 brlcad heh
19:39.35 brlcad well I know why that is
19:39.51 brlcad the guy in charge of the whole thing for Coverity
19:39.57 brlcad David Maxwell
19:40.03 brlcad he's a core NetBSD developer
19:40.05 yukonbob I'm not a NetBSD coreteam member... it makes sense
19:40.08 yukonbob heh
19:40.23 brlcad so he probably just chuckled
19:40.33 yukonbob I guess :)
19:41.02 brlcad heh, that's funny .. of all the projects ...
19:41.04 yukonbob but back to example of URL (utah raster lib) -- will they give us the URL buglist, even though it's not our project?
19:41.27 yukonbob (but is a dependency of the BRL-CAD build)
19:41.39 brlcad yes, but it just all is attributed as BRL-CAD code
19:42.04 brlcad e.g. they (at least originally) considered everything in our source tarball as "BRL-CAD" code
19:42.05 yukonbob because unless a URL dev gets access to that list, we have info that may be unpatched and could wreak havoc on other projects using the URL...
19:42.09 brlcad same goes for every other project
19:42.26 brlcad yet often clearly not the case when it's external code (zlib is a common one many provide)
19:43.14 brlcad for what it's worth, we're pretty much the maintainers for URT (utah raster toolkit)
19:43.24 yukonbob ah right -- urt not url
19:43.27 brlcad but tcl/tk is a better example
19:43.41 brlcad they're a big package and ALSO in coverity scan
19:43.48 yukonbob it's got 0 issues atm
19:44.07 brlcad yet if you look at the little bit of BRL-CAD report we do have -- all those issues listed were actually in Tcl
19:44.35 brlcad the "99 uninspected" issues at http://scan.coverity.com/rung1.html for BRL-CAD are Tcl issues
19:44.41 yukonbob so re: Tcl -- did we need a TCT member to "sign-off" on allowing the Tcl to be included in the BRL-CAD scan?
19:44.55 brlcad and then the coverity scanner died shortly after when it got to Tk, I believe
19:45.06 brlcad no
19:45.24 brlcad i still don't get where/why you think we need these sign-off's...
19:45.44 yukonbob hrm --- if that's the way it works, so be it -- just seems like private information to me (ie: us knowing the bugs in tcl/tk, potentially before TCT members do)
19:46.17 brlcad it just means that we may get reports for issues in code that we may or may not maintain
19:46.32 brlcad which we could fix or mark as verified and ignore
19:46.39 brlcad or leave out of the scan entirely
19:47.10 brlcad which is what david has been trying to do for our code since we were first added, ignore everything in src/other
19:47.28 brlcad just hasn't finished
19:47.47 brlcad I imagine it took changes to coverity prevent
19:47.53 yukonbob my reasoning is that the coverity scan seems like a powerful tool to find classes of bugs -- wouldn't want hax0rs to have access to information before it's patched, or even known by the true maintainers of the software... but if they're only allowing certain projects, and contacting the project leads for those, I guess they're assuming that all the folks being scanned are responsible people...
19:48.23 brlcad pretty much
19:49.16 brlcad seems like a pretty darn safe assumption to me .. i mean even with tcl getting included in our report, we might actually want to fix their issues as we do depend on them
19:49.21 brlcad their issuers *are* our issues
19:49.44 brlcad but I certainly don't want to fix their problems if I don't have to :)
19:49.53 brlcad and them likewise for their deps I'm sure
19:50.24 yukonbob right -- I was assuming Joe Hacker could submit a project that might depend on openssl, though, and then have access to classes of errors in ssl that could be used on the Wild Wild Web
19:50.45 brlcad which is why the set up projects individually one at a time, ask who you are, etc
19:51.35 brlcad every project they've added is manually added, takes david a couple hours per project of effort iirc
22:59.24 *** join/#brlcad Z80-Boy (i=clock@217-162-109-28.dclient.hispeed.ch)
23:08.12 CIA-30 BRL-CAD: 03brlcad * r29892 10/brlcad/trunk/src/mged/mged_dm.h: no need to define DEG2RAD and RAD2DEG
23:17.54 CIA-30 BRL-CAD: 03brlcad * r29893 10/brlcad/trunk/configure.ac: enable maintainer mode for any type of checkout, not just cvs (i.e. subversion too)
23:24.08 CIA-30 BRL-CAD: 03brlcad * r29894 10/brlcad/trunk/doc/book/VolumeIV.xml: use bu_exit for the examples
23:27.14 CIA-30 BRL-CAD: 03brlcad * r29895 10/brlcad/trunk/src/adrt/isst/ (master/ slave/): ignore the binary products
23:39.12 CIA-30 BRL-CAD: 03brlcad * r29896 10/brlcad/trunk/src/ (41 files in 8 dirs): refactor to use bu_exit instead of bu_log+exit where applicable
23:58.43 *** join/#brlcad Axman6 (n=Axman6@pdpc/supporter/student/Axman6)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.