Index

Show enters and exits. Hide enters and exits.

16:54:24stan-Hi Evan
16:54:46evanstan-: hi hi
16:54:57evanso, I just spun up a sinatra app on unicorn properly
16:55:01evanso I know it does work.
16:55:41evanyou're error almost looks like MRI loading the extension compiled for rubinius
16:55:58evantry 'ruby -S unicorn <file>'
16:56:03evanand see if there is any difference
16:56:16evansince you're using rvm, I assume that ruby == rbx
16:56:34stan-ok let me set that up
17:06:38stan-hmm, sorry, not going to be able to test that until tomorrow (2AM here).. I just lost my connection to the office where I got the error.
17:07:54evanno problem
17:08:03evanjust know this is fixable as a configuration error :)
17:08:30stan-cool :)
18:18:04stan-well.. interesting developments..
18:18:59stan-replicated the same problem locally by following the same steps
18:19:20evanwhat same steps?
18:19:20stan-ie installing rbx using rvm and then starting the sinatra app
18:19:28evanwhat about trying ruby -S unicorn
18:19:29stan-to be precise :
18:19:29evandoes that work?
18:19:46stan-switched to rvm 1.9.1
18:19:58stan-rvm install rbx --head
18:20:18stan-(this triggered install of rvm 1.8.7? i think as required for rbx install)
18:20:25wayneeseguinstan-: 'rvm install rbx-head'
18:20:27stan-then rvm installed rbx
18:20:30wayneeseguin --head is invalid
18:20:37stan-hmm still works
18:20:50stan-got rc5
18:21:09stan-then installed sinatra and rack, but not unicorn
18:21:22stan-unicorn ... got me the same error
18:21:25stan-BUT
18:21:44stan-sorry forgot 1 thing
18:21:56stan-so.. then installed sinatra and rack, but not unicorn
18:22:01evanstan-: what about doing ruby -S unicorn
18:22:01evan?
18:22:20stan-trying to start unicorn got me a missing gem but from ruby 1.8.x
18:22:39stan-then installed unicorn, then error
18:22:47evaninstall unicorn how?
18:22:56stan-gem install unicorn
18:22:57evanfeels like you're gotting stuff crossed between MRI and rbx
18:23:00evanbigtime.
18:23:10stan-yeah, but thats not all..
18:23:20evanthis seems like it's an rvm problem
18:23:24evanwayneeseguin: could you work with him?
18:23:27evani have to run to lunch
18:23:43stan-ok have a good one
18:23:44evanseems like running 'unicorn' is running it under MRI
18:23:54evanthats why i'm asking to try ruby -S unicorn
18:23:55stan-opening another shell, switching to rbx, trying to start unicorn CRASHED the mac
18:23:56evandid you try that?
18:24:15evanstan-: well :/
18:24:27stan-same reason i lost my office remote connection :/
18:24:39evanI can't see why it would crash your whole mac
18:24:46evanthat can't really be a bug in rubinius
18:25:01stan-well, cpu 100% form there, cant do anything
18:25:08stan-I imagine
18:25:33stan-although same thing with rvm 1.9.1 runs perfect
18:27:05evanstan-: wait wait
18:27:23evanit's something to do with having ruby 1.9.1 installed?
18:27:25stan-I think the "ruby -S unicorn" trigered the cpu craziness on the office one
18:27:32stan-hmm
18:27:41evanack, I have to run.
18:27:44evansorry.
18:27:57stan-no worries, I'm going to bed myself
18:36:54stan-i'll check tomorrow by installing rbx directly, staying away from rvm, something definitively wrong with it at least on the initial error.
18:37:04stan-bye
18:57:16brynaryis this the official ticket tracker these days?: http://github.com/evanphx/rubinius/issues
19:02:14dbussinkbrynary: yeah
19:03:29brynarydbussink: thanks
19:03:32brynary0 open tickets? wow
19:03:51dbussinkbrynary: it's actively kept clean for the 1.0 release now :)
19:04:32brynarydbussink: 1 now :) http://github.com/evanphx/rubinius/issues/issue/282
19:04:37brixenbrynary: we have some things that are in a tracker for post 1.0
19:04:59brynarybrixen: cool
19:05:14brixenbrynary: linecache will never be supported on rbx
19:05:16brixensorry :)
19:05:32brynaryah. hmm. time to figure out what depends on it.
19:05:33brixenwe are not MRI's interpreter
19:06:06brynarybrixen: I don't know anything about linecache. why is it different than other C extensions?
19:06:36brixenbecause it depends on MRI internals
19:06:48brixenruby_eval_tree_begin
19:06:55brixenfat chance you'll get that in rbx :)
19:07:08brixenbrynary: afaik, ruby-debug depends on it
19:07:14brynarygot it
19:07:22brixenif you are trying to run a vanilla rails3 app, you need to comment that out
19:07:25brynarydoes rbx have a debugger?
19:07:34brixenthe bundler exclusion doesn't seem to be working
19:07:47brixenrbx has a debugger bit it needs some work
19:08:01brixenwe will fix it after 1.0 is released
19:08:09brixens/bit/but/
19:08:16brynarycool
19:09:29brynarybrixen: would it be a good idea to setup rbx so when you try to install linecache you get output that says: "linecache is not supported under Rubinius because of X. You'r probably getting this because you're trying to install ruby-debug... blah blah" instead of a compile error?
19:09:56brixenwhy would we set up rbx to do that?
19:10:04brixenthe gem needs to not install on rbx
19:10:15brynarybrixen: simply to make the user experience nicer for people who did what I did and don't know
19:10:24brynarywhich is `rvm use rbx` and `bundle install`
19:10:33brixenyes, I'd like to make the experience better
19:10:38brixenbut rbx cannot track all those gems
19:10:48brixengems need to be better about existing in the alt impl ecosystem
19:11:03brynaryagreed
19:11:08brixenand any gem author that writes code that digs into MRI needs to know better
19:11:13brixensame with C extensions
19:11:19brynaryyeah, 100%
19:11:31brixennot our responsibility, even though the poor UX pains me
19:12:05brixenit's also wacky that vanilla rails3 app depends on ruby-debug
19:12:08brixenIMHO
19:12:30brynaryheh. yeah probably
19:12:56brynarytrying to get my current project (Rails3 + Rspec2 + MongoDB) to run under rbx
19:13:05brixenawesome!
19:13:06brynarypast the bundle install, now getting a StackError
19:13:12brixengist?
19:13:26brixenI haven't heard of anyone tackling Rspec2 yet
19:13:51brynarybrixen: will have it in one sec
19:13:54brixenk
19:14:08brynaryRSpec 2 is needed for Rails 3 if you want the Rails-specific features
19:14:27dbussinkrspec2 is supposed to be a lot nicer internally, i haven't tracked that though
19:15:14brixenis rspec2 in a gem yet? or should I get the git repo?
19:15:20brixenI haven't looked at it at all
19:15:22brynarybeta gem
19:15:28brixenle'me try it
19:16:00brixenI love segfault 1.9.1 :)
19:16:15brixensegfaulting*
19:16:46dbussinkbrixen: happens too often :)
19:16:51brynaryheh. stack trace is too large for gist
19:17:13brixenheh
19:17:31brixenme haz big stackz yo
19:17:35brixener we*
19:17:37brixenjeez
19:17:43brixen<- ego
19:18:38brynarybrixen: PM
20:28:00evanallo
20:31:23brixenallo
20:31:47cremesare you two trying to say "1.0"?
20:32:12evanheh
20:32:16brixenapparently 'describe String do; end' will cause a StackError in rspec2
20:32:19brixencremes: :)
20:32:25brixenI haven't looked into it yet
20:32:43brixenI'm actually gonna grab some food at this point
20:33:03evanoh darn, brynary left.
20:33:04brixenthe StackError is in Array#each
20:33:10evangot a backtrace?
20:34:27evanoh rspec2, you're dumb.
20:45:32evanbrynary: I figured out the issue
20:45:43brynaryevan: nice. what was it?
20:45:44evanbrynary: rspec2 redefinese .ancestors and uses Class#<
20:45:53evanand rubinius defines Class#< in terms of .ancestors
20:45:55evanthus, loop.
20:46:03brynaryinteresting
20:46:18brynaryheh. so who's fault is it? :P
20:46:21brynarywhose*
20:46:50evani'd say rspec2 personally.
20:47:09evanbut we can go ahead and have Class#< not use ancestors
20:47:47evanit shouldn't be using ancestors anyway
20:48:00evanthats the most ineffeciant way to do it
20:51:00brynaryhmm... alright. well maybe RSpec 2 should be fixed and then it's question of it's better to change the rbx implementation of Class#<
20:53:03evanwe should change the rbx impl.
20:53:19evanwhich i'll do shortly.
20:53:25evanonce i've done with my current task.
21:01:09brynarygreat. thanks
21:35:58somebodyfunny: http://www.youtube.com/watch?v=Wm-9NjFeBWM
21:42:53asarihkronos_vano: glad you liked it. :-)
21:43:02kronos_vano:)
22:02:07boyscoutUse _exit() rather than exit() to avoid C++ finalization races - 87dcf8c - Evan Phoenix
22:02:07boyscoutCatch and handle a redo passing through a rescue properly (unicorn) - 2065e70 - Evan Phoenix
22:02:07boyscoutDon't use Class#ancestors internally - d154e50 - Evan Phoenix
22:02:30evanbrynary: ok, that should get rspec2 moving along
22:02:41brynaryevan: thanks!
22:05:37brixenkronos_vano: yours was pretty cool too
22:05:44brixenkronos_vano: what did you use to create it?
22:06:35kronos_vanoOh I think no one saw my version) http://code.google.com/p/codeswarm/
22:06:52brixenheh I did
22:06:56brixencool
22:07:42brixenthat's pretty funny that google code doesn't allow the _ in a project name
22:07:49brixenaccording to this project anyway
22:11:16evanhah
22:11:29boyscoutCI: rubinius: d154e50 successful: 3457 files, 13596 examples, 41216 expectations, 0 failures, 0 errors
22:12:08slavahi evan
22:12:26evanhi slava.
22:12:46brixenhi slava
22:14:03slava1.0 tomorrow?
22:15:40kronos_vanoMy favourite slide http://rghost.ru/1614666/private/c8775617b152c4f0331aafff0c7831ca.view
22:18:13evanslava: i think so!!
22:19:05evankronos_vano: are your slides in english even if you're going to be talking in russian?
22:19:31kronos_vanoin russian I just translate with one :)
22:19:43evanah ok :)
22:23:31kronos_vano*this one
22:36:49slavaevan: I didn't think people would complain when I dropped support for x86 chips without SSE2
22:39:02evanthey did?
22:39:45slavaapparently people with older computers like their esoteric languages
22:40:19evanI guess thats not unsurprising.
22:40:28evandid you just tell them to use an older version?
22:43:44brixenoh, I can totally imagine some folks I know hammering out Factor on their 386 machines
22:44:06brixenlike cuba with 50's chevy cars
22:44:18brixenoh, but that's because of the embargo :)
22:45:10slavayour 386 will need like 512mb of memory at least
22:45:46brixenheh
22:46:36brixendid I ever tell you about running Xwindows on a 486dx with 16mb of ram with dosemu running in a terminal to run a protected mode CAD/CAM app?
22:46:42brixenI should tell you that story sometime
22:46:47slavahaha
22:46:51slavasounds like an epic story
22:46:55brixenheh
22:47:09brixenworked much better than Wine trying to run notepad.exe, le'me tell ya
22:47:30evanbrixen: i think I did the same thing.
22:47:57brixenevan: did you get fun colors when switching between X and dosemu sometimes? :)
22:48:11evanyeah, because the pallet was too small
22:48:13evan:)
22:48:15brixenheh
22:48:20slava486? you guys must be ancient
22:48:25slavamy first linux box was a pentium
22:48:28brixenwinnt 5.1 would not even run on that computer as I recall
22:48:38brixenlinux barely used 5mb of the ram
22:48:57evanmy first linux machine was a 386.
22:49:03brixenslava: apple IIe baby
22:49:13brixenI wish I ran linux on that
22:49:17brixenI would be linus I guess
22:49:24evan386 16Mhz with 2M of ram.
22:49:29evaninstalled slackware off disks.
22:49:37evanoh, those were the days...
22:49:40evaneverything was so much simplier.
22:49:42brixenoff floppies, yes!
22:49:55brixennot simpler, just slower :)
22:50:12brixenconfiguring slackware kernel was not simple
22:50:14evani remember booting into X and getting twm for the first time and going "um, ok, what now?"
22:50:19evanit was such a slog to just install it
22:50:21brixenheh
22:50:27evani wasn't sure what I wanted to even do then!
22:50:44brixensearch for some terrible X games to play
22:51:00brixenrevert to the terminal for multiplayer text games
23:20:41haruki_zaemonHaving issues installing rbx-head via RVM on Mac OSX 10.6. Can anyone lend a hand? http://gist.github.com/400610
23:22:49evanharuki_zaemon: do you have LLVM installed on your system?
23:22:52evanyou must
23:23:04haruki_zaemonindeed, 2.7
23:23:05kronos_vano./configure --skip-system
23:23:07haruki_zaemon➜ llvm-config --version
23:23:07haruki_zaemon2.7
23:23:21evanwe don't support 2.7
23:23:25haruki_zaemoninstalled via homebrew
23:23:27haruki_zaemonahhh
23:23:28haruki_zaemonwell
23:23:31haruki_zaemonthat'd be it LOL
23:23:40jvoorhisLLVM is a moving target
23:23:44haruki_zaemongotcha
23:23:48haruki_zaemonnuts
23:23:55evani was going to make us ignore the system LLVM by default
23:23:59evanseems I forgot to do that
23:23:59jvoorhisevan: moving to 2.7 anytime soon?
23:24:00brixenI dare say we should avoid ever using system LLVM installs unless specifically requested
23:24:05brixenI though we changed that
23:24:06evangiven the number of people that are hitting this
23:24:09evani thought we did to!
23:24:13brixenhm
23:24:13evanlets see...
23:24:21haruki_zaemonI'm using rbx-head FWIW
23:24:32jvoorhisbrixen: that's probably wise
23:24:46haruki_zaemonevan: I take it rbx comes with a version of llvm then?
23:25:02brixenharuki_zaemon: we have prebuilt versions for popular platforms
23:25:05evanharuki_zaemon: it either builds 2.6 or it uses a prebuilt package for your platform
23:25:11haruki_zaemonnice
23:25:11haruki_zaemonok
23:25:13evanthere are prebuilds for the most common platforms
23:25:19haruki_zaemonthen it's the system one that's killing it I presume
23:25:27jvoorhisevan: when you move to 2.7, we should dial in the use of LLVMContext :)
23:25:35brixenharuki_zaemon: ./configure --skip-system
23:25:37evanjvoorhis: well, it's LLVM that couldn't decide
23:25:41jvoorhisevan: i *think* that would make ruby-llvm feasible
23:25:42evanthey made us use LLVMContext
23:25:45evanthen pulled it back.
23:25:50jvoorhisreally?
23:25:54evanyeah
23:26:01evanyou had to use it in 2.6
23:26:04evanthere was no way around that.
23:26:08jvoorhisi may have misunderstood
23:26:10evani didn't use it because it's fun.
23:26:17evani did because there is no way to not use it.
23:26:21jvoorhisright
23:26:43jvoorhisbut i thought llvm 2.7 made it safe to run multiple EEs, one per context
23:27:27jvoorhiswhich would avoid conflicts between rbx and ruby-llvm users
23:27:31evanperhaps, i don't see how thats related to LLVMContext.
23:27:57evanbrixen: huh, i thought i made it ignore the system by default...
23:28:02evanconfusing..
23:28:15evanwell, it's easy to fix.
23:28:20evani'll go ahead and do that.
23:28:22jvoorhisrelated to LLVMContext because iiuc you can't have multiple EEs within a single context
23:29:01jvoorhisthough i guess if i just used my own context for everything, it doesn't matter what rbx uses – i just shouldn't assume i can use the global context
23:30:05brixenevan: I thought you had too, odd
23:30:06jvoorhis(sorry for the cross-talk, that was just on my mind since reading the 2.7 release notes)
23:30:42evanbrixen: actually, what i'm going to do is leave the current behavior
23:30:46evanie, try to use a system LLM
23:30:47evanLLVM
23:30:54evanbut i'm going to teach configure that it can't use 2.7
23:31:00evanso if it finds 2.7, it will just ignore it.
23:32:41evanah crap!
23:32:47evanwe don't have a prebuilt for 10.6.3
23:33:04brixenhmm
23:33:10jvoorhishas llvm expressed any interest in offering binaries?
23:33:13brixenevan: that sounds fine
23:33:41brixenharuki_zaemon: can you build us a 10.6.3 prebuilt? :)
23:33:47evanbrixen: i got it
23:33:50evanthe 10.6.2 one is fine
23:33:50brixenok
23:33:53jvoorhison my old laptop, it was a 3 hour build, and on my MBP it's still not fast
23:33:54evani've been using that once this whole time
23:34:02evanso i just copied 10.6.2 to 10.6.3
23:34:03brixenahh ok
23:34:09jvoorhisand if i forget --enable-shared, i have to build twice
23:39:23boyscoutRestrict configure to only using LLVM 2.6 from the system - 88c678c - Evan Phoenix
23:40:36WALoeIIII can't install nokogiri, it uses up ~ 3GB of RAM and like 24G virtual before everything explodes on my computer
23:41:07brixenthat is a colorful description :)
23:41:28WALoeIIIits pretty cool
23:41:42brixenWALoeIII: did you have to borrow a coworkers computer to access IRC? :)
23:41:44WALoeIIIthis is 1.4.1 against rc5
23:41:56WALoeIIII'm on my ubuntu box
23:41:58WALoeIIIso yes.
23:42:00brixenahh
23:42:05WALoeIIIthat machine is still on fire.
23:42:09brixenheh
23:42:17brixenwell, call the fire dept first!
23:42:51evanWALoeIII: I suggest you hit ^C
23:42:54brixenok, so what is the platform of the exploded computer?
23:43:02WALoeIIIevan: I did, about 10 minutes ago
23:43:09WALoeIII16:43:00 nokogiri (master) → uname -a
23:43:09WALoeIIIDarwin Loe.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
23:43:13evanthe kill -9 it
23:43:30WALoeIIIevan: I am on the 2nd 'l' of typing
23:43:39WALoeIIIit takes ~ 30 seconds a character
23:43:40WALoeIII:-P
23:43:48WALoeIIIjust pull the plug
23:44:04evanno you pull the plug, it's your computer!
23:44:11brixenhah
23:44:11WALoeIII:(
23:44:44WALoeIIIall kidding aside, Its 10.6
23:44:56WALoeIIIrvm's rbx 1.0.0rc5 and 1.4.1
23:45:02WALoeIIItrying to build nokogiri HEAD now
23:45:29brixenhmm rvm could be causing some issues
23:45:30evanwhat were you doing that cause the blow up?
23:45:44brixenWALoeIII: could you try building rbx master from git
23:46:00WALoeIIIbrixen: I could
23:46:06WALoeIIIlet me see if nokogiri does it first though
23:46:12WALoeIIIbecause I installed a bunch of other gems with no problems
23:46:18brixenWALoeIII: also, what was the command you used to try to install nokogiri on rbx?
23:46:25WALoeIIIgem install nokogiri
23:46:33brixenok
23:46:42brixenI'm just a little twitchy about rvm
23:46:52brixensince we haven't tested rbx with it much
23:47:03brixenI never use it to install rbx
23:47:20boyscoutCI: rubinius: 88c678c successful: 3457 files, 13596 examples, 41216 expectations, 0 failures, 0 errors
23:48:29evanWALoeIII: i'm trying it here.
23:48:46evan:(
23:48:48evanit failed
23:48:50evangreat.
23:49:31haruki_zaemonbrixen: Sorry, back now -- son has a fever...
23:49:59brixenharuki_zaemon: no worries, sons-with-fevers take precedence
23:50:11WALoeIIIevan: did it use up gobs of ramsies?
23:50:17evannope.
23:50:21evannot at all.
23:50:23WALoeIIIInteresting
23:50:27WALoeIIII can't install racc
23:50:33WALoeIIIso I can't build nokogiri
23:50:36WALoeIIIrexical works
23:50:44WALoeIIImake: *** No rule to make target `/Users/Andrew/.rvm/rubies/rbx-1.0.0-rc5/include/config.h', needed by `cparse.o'. Stop.
23:52:08evanone thing at a time please
23:52:11evanit's hard to follow.
23:52:12haruki_zaemonbrixen: So is there something I can do to help?
23:52:18evanyou're trying a different gem now?
23:52:28haruki_zaemonit's no rush
23:52:34haruki_zaemonI just thought I'd give it a whirl :)
23:52:48brixenharuki_zaemon: you should be able to do ./configure --skip-system; rake
23:53:12brixenharuki_zaemon: or, rather; git co master; git pull; ./configure; rake
23:53:15haruki_zaemonok will try that
23:53:43brixenharuki_zaemon: evan just fixed it to not use system install LLVM if it's other than v2.6
23:53:50haruki_zaemonAhh cool
23:53:54haruki_zaemonI'll do another pull
23:53:54WALoeIIIevan: nokogiri depends on racc and rexical to build, I checked it out of git
23:54:07haruki_zaemonevan: Thanks!
23:54:10WALoeIIIcan't link against config.h, not sure what it expects
23:54:43evanWALoeIII: ok, well, full stop on you for now.
23:54:51evani have to deal with the nokogiri gem right now.
23:54:58evanit won't build
23:55:00evanand it should.
23:55:37WALoeIIIevan: I think 1.4.2 is 'imminent' so thats why I thought head might be worth trying, I know one of the listed features under 1.4.1 is 'rubinius support'
23:55:42WALoeIIIevan: thanks for working on it :)
23:59:00haruki_zaemonevan: Worked a treat. Thanks again!
23:59:07evanno prob!