00:44
blakemizerany joined
01:59
blakemizerany joined
03:45
<bea>
sr: I'll pass that on when nakajima is around.
03:45
<sr>
err, but that still requires AR
03:45
<raggi>
i just use EM to push stuff out to another process(es)
03:46
<raggi>
normally something like object_protocol
03:46
<harryv>
for stuff that doesn't require persistence, beanstalkd looks nice
03:46
<raggi>
if i need better exchange control, maybe go to amqp or something
03:47
<raggi>
srsly, if you don't need persistence, just use drb or something
03:47
<sr>
well, that is just for background build so I don't think we need anything fancy
03:47
<raggi>
3-6 lines, and no external dependencies
03:47
<sr>
threaded works fine though
03:47
<raggi>
that's cool, i'm glad, as i didn't even test it properly :)
03:48
<raggi>
horay for goto
03:48
<harryv>
it's always great with new features.
03:52
<sr>
oh also, they use "\" as the namespace separator
03:58
<foca>
heh, it's funny they *added* goto for 5.3
03:59
<foca>
when it's supposed to be so ghetto
03:59
<foca>
then again, it's php
04:02
<raggi>
there are certain things it's really useful for
04:02
<raggi>
like specific error condition handling
04:03
<raggi>
we have a really slow, single direction goto
04:03
<raggi>
called throw
04:48
<foca>
yeah, I know
04:49
<foca>
I'm not against using goto, at least not if you thought about it 25 times and still think it's the best solution :)
04:49
<foca>
(or throw/catch)
09:07
esquivalient joined
09:17
esquivalient_ joined
10:23
<martinemde>
Hi all, I'm getting a gem dependency problem when trying to run integrity locally: rack(1.0.0 not >= 0.9.1, < 1.0), then if I solve that it wants rack >= 1.0 for thin
10:24
<martinemde>
I've tried the current gem version and the master branch
10:31
<sr>
martinemde, yeah, that is because the lastest sinatra version (released yesterday) now depends on rack1.0
10:32
<sr>
but, that shouldn't happen as integrity requires sinatra 0.9.1 (which do not require rack1.0)
10:32
<sr>
bit of a mess heh
10:33
<martinemde>
well, if I fix that and try to launch with thin, thin wants rack 1.0
10:33
<sr>
the thing is sinatra 0.9.2 has a bug which affects integrity
10:33
<sr>
easiest would be to build a gem from my "layout-local" branch of sinatra
10:33
<martinemde>
hmm, what a mess :P
10:34
<sr>
run `rake install` in that branch and you should be fine (hopefully ;-)
10:34
<martinemde>
k, I'll try that
10:34
<martinemde>
thanks
10:38
<martinemde>
getting a String#bytesize in your sinatra build
10:38
<martinemde>
one sec, making sure it's not my problem
10:39
<martinemde>
oh, sorry
10:39
<martinemde>
my problem
10:39
<martinemde>
that fixed
10:39
<martinemde>
er... that fixed it, integrity is running :)
10:50
<sr>
hopefully that fix will go in a maintenance release quickly
10:51
<qrush>
the "hasn't been built yet" page still looks crappy
10:52
<sr>
qrush, feel free to add some css rules to views/integrity.sass :P
10:52
<sr>
or bug foca to do it
10:53
<* sr>
is lame at CSS/choosing colors etc
10:55
<sr>
qrush, you running off the bob branch btw?
11:07
esquivalient joined
11:29
<qrush>
Has there been any work done with Integrity and metric_fu?
11:31
<qrush>
yeah but is there a way to do that across every project in integrity?
11:31
<qrush>
I don't want to have to inject that into 20 projects
11:31
<sr>
nothing that I am aware of
11:32
<sr>
Project.all.each { |p| p.command = p.command + " && rake metric_fu" } ? :-)
11:33
<qrush>
I'd rather it be part of the build script
11:34
<sr>
ah yeah, s/rake metric_fu/gen-metric-fu-report.sh/ or something
11:35
<sr>
btw, I am wondering if a separate app for metrics could work
11:36
<qrush>
well, the gist here is that i want to generate metrics reports, and then we'll build them into some projects
11:36
<qrush>
i.e, builds fail if some metric fail
11:37
<sr>
yeah then you want it to be part of the build command
11:37
<sr>
but seriously, a simple bash/ruby/whatver script shouldn't be hard to write
11:39
<sr>
basically, run metric fu, mv tmp/metric_fu to some place where they'll be served by your webserver and exit accordingly to the metrics report
11:39
<qrush>
integrating hg has been a pain in the ass
11:39
<qrush>
would be so nice if integrity was a little more scm agnostic
11:39
<sr>
you better implement it in bob
11:39
<qrush>
I didn't implement anything
11:39
<qrush>
I'm using hg-git
11:40
<qrush>
On second thought that would have been an easier route.
11:41
<qrush>
I'd love to do it, but using hg-git will do for now. Another huge thing is that we can't control the hg hooks.
11:41
<qrush>
also i have jekyll and gemcutter to worry about ;)
11:42
<sr>
as for post-receive hooks, that'll get better when bobette will be integrated
11:43
<sr>
it'll implement a simple API and various "wrappers" to transforms whatever comes in from github, bitkeeper, etc into something that it understand
11:44
<sr>
how did you manage to implement post-receive hook with hg btw?
11:53
<martinemde>
cool, integrity is working great
11:53
<martinemde>
got a successful build
11:54
<martinemde>
next task, any idea how I would push to heroku and have it pull a private project from github? I assume it's something to do with a deploy key on the project
11:54
<qrush>
sr: I didn't.
11:54
<sr>
qrush, ah, so polling only?
11:54
<qrush>
sr: Going to use a cron job that pulls from hg and gpushes to github, which triggers integrity
11:55
<qrush>
I wanted to have everyone just install hg-git but they weren't too keen about that.
11:55
<sr>
you could skip the gpush part
11:55
<martinemde>
well, this is really weird
11:56
<qrush>
sr: I'm not sure I follow.
11:56
<sr>
wait. nvm me :-)
11:56
blakemizerany joined
11:56
<martinemde>
sqlite3 is deciding to get rid of my data
11:56
<martinemde>
the page works for a few page loads and then it goes to "no such table"
11:57
<sr>
martinemde, what version? (also, I am guessing you are running it with `integiryt launch`?)
11:58
<martinemde>
and I'm using foca-integrity gem
11:58
<sr>
uninstall it. right now. :-)
11:58
<sr>
that gem is unmaintained/broken
11:58
<sr>
we're publishing gem on rubyforge now. gem install integrity
11:58
<martinemde>
I tried it when I was having the dependency issues
11:59
<sr>
the canonical repo is github.com/integrity/integrity btw
11:59
<martinemde>
yeah, didn't fix it anyway, and then forgot
12:00
<martinemde>
ah, back to the thin/integrity conflicting versions of rack problem
12:00
<martinemde>
I still have that version of sinatra you suggested
12:00
<martinemde>
can't activate rack (>= 1.0.0, runtime) for ["thin-1.2.1"], already activated rack-0.9.1 for ["sinatra-0.9.1.1", "integrity-0.1.10"]
12:02
<martinemde>
is that the right version of sinatra? doesn't look right..
12:03
<martinemde>
yeah, it's not loading the new sinatra I installed from your repo
12:05
<martinemde>
ok, integrity's gemspec is requiring sinatra = 0.9.1.1
12:12
<martinemde>
ok, I assume that's something that will be fixed when the sinatra thing is fixed. Changing my spec and rebuilding the gem fixes it.
12:12
<martinemde>
gotta run to a meeting
12:13
<martinemde>
er, doesn't work quite right just changing the spec. It's redirecting me to 0.0.0.0 without the port number at random times
12:19
<sr>
martinemde, wdym redirecting? after a form submit?
12:59
<sr>
if you can figure a way to get the HEAD out of a remote hg repository, that should allow you to avoid the github step
13:01
<qrush>
eh it would still be manual though
13:20
<martinemde>
sr, after a form submit, like updating the project or requesting a build it redirects to 0.0.0.0/
13:20
<martinemde>
instead of with the port
13:20
<martinemde>
but the links all work fine
13:51
<mileszs>
martinemde: The integrity launch command hard-codes the host as 0.0.0.0 at the moment, IIRC.
14:09
<sr>
duh! we need to fix those damn URLs and the launcher for good
14:10
<sr>
I wonder wheter Install#launch really is a good idea
14:29
blakemizerany joined
15:19
<martinemde>
mileszs, yeah, that seems like it'd be fine except keeping the port number that launch starts it up as
19:37
ajmorris2002 joined
19:38
<ajmorris2002>
hey guys I've got a probably stupid question
19:39
<ajmorris2002>
I'm wondering how I can freeze the required gems for integrity so I don't have to worry about trying to install them just to run the app
19:39
<ajmorris2002>
I thought about adding them to the .gems file, but that would still make them install
19:39
<halorgium>
ajmorris2002: you'll need to freeze the bin/* files too
19:39
<halorgium>
and force the gem paths to point there
19:40
<halorgium>
it is a non-trivial problem :(
19:41
<ajmorris2002>
haha yeah -- I don't sys admin our servers and so rather then deal with the run around I get from them, I figured I'd just throw everything I needed for the app in one directory
19:41
<ajmorris2002>
:) you can tell I come from the rails world
19:53
blakemizerany joined
20:15
ajmorris2002 joined
22:37
<bdot>
hi all, ive been trying to get integrity to work on heroku, and no matter what i do, i get a LoadError while loading do_postgress
22:38
<bdot>
any ideas on what i could be doing wrong?
22:48
<esquivalient>
I know absolutely nothing about heroku, but I didn't want to leave you hanging
22:48
<esquivalient>
are there any kind of server access/error logs that might provide useful info?
22:50
<bdot>
hey esquivalient, whatever shows up on the page right now is what gets logged unfortunately
22:50
<bdot>
im kinda new to heroku as well so im not sure if theres anything more i can find out
22:50
<esquivalient>
do you have that gem installed?
22:50
<esquivalient>
it looks like it's looking for a database gem
22:51
<halorgium>
bdot: i think you have to do something specific with heroku and binary gems
22:54
<bdot>
yeah i took a look and tried adding a quickie sinatra app that called into datamapper and it seemed to be there
22:55
<halorgium>
bdot: maybe you aren't requireing rubygems?
22:57
<bdot>
halorgium: i have the integrity generated rackup file and it requires rubygems there, though there might be something else i need to do
22:57
<halorgium>
bdot: load up the debugger
22:58
<bdot>
halorgium: the console? or?
22:58
<halorgium>
console, yer
22:59
<bdot>
the console throws the same error (when i run "heroku console", its supposed to be a remote irb)
23:02
<esquivalient>
can you edit the gem source so play around with getting more data out of the error message?
23:08
<bdot>
yeah, ill take a look at it and let you guys know what i find
23:59
esquivalient joined