<evan>
2013-04-23_00:59:00.27320 from /applications/rubygems/production/releases/6e27154cb9f52fb9fc8e004475a9f57ee437e5a9/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn.rb:44:in `eval'
<evan>
2013-04-23_00:59:00.27321 from /applications/rubygems/production/releases/6e27154cb9f52fb9fc8e004475a9f57ee437e5a9/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn.rb:44:in `block in builder'
<evan>
i'm trying to diagnose it now.
yut148 has joined #rubygems
ZachBeta has quit [Quit: Computer has gone to sleep.]
tenderlove has quit [Remote host closed the connection]
ZachBeta has joined #rubygems
mockra has quit [Remote host closed the connection]
xymox has quit [Ping timeout: 255 seconds]
xymox has joined #rubygems
DonOtreplay has joined #rubygems
ZachBeta has quit [Quit: Computer has gone to sleep.]
newUser1234 has joined #rubygems
baburdick has quit [Quit: Leaving.]
ZachBeta has joined #rubygems
crandquist has joined #rubygems
DonOtreplay has quit [Quit: Computer has gone to sleep.]
crandquist has quit [Client Quit]
<samkottler>
evan: would a more complete CI environment be useful for preventing downtime like this
newUser1234 has quit [Remote host closed the connection]
yerhot has quit [Remote host closed the connection]
newUser1234 has joined #rubygems
ZachBeta has quit [Quit: Computer has gone to sleep.]
mbull9 has quit [Remote host closed the connection]
mootpointer has quit [Quit: Computer has gone to sleep.]
havenwood has joined #rubygems
mootpointer has joined #rubygems
jcaudle has quit [Quit: jcaudle]
newUser1234 has quit [Remote host closed the connection]
blowmage has quit [Excess Flood]
blowmage has joined #rubygems
newUser1234 has joined #rubygems
terceiro has quit [Quit: Ex-Chat]
caleb_io has joined #rubygems
baburdick has joined #rubygems
dvu has joined #rubygems
newUser1234 has quit [Remote host closed the connection]
TheMoonMaster has quit [Excess Flood]
TheMoonMaster has joined #rubygems
TheMoonMaster has quit [Excess Flood]
TheMoonMaster has joined #rubygems
cowboyd has joined #rubygems
mockra has joined #rubygems
mockra has quit [Remote host closed the connection]
yerhot has joined #rubygems
mockra has joined #rubygems
yerhot has quit [Ping timeout: 256 seconds]
mockra has quit [Remote host closed the connection]
mockra has joined #rubygems
mbull9 has joined #rubygems
yashshah__ has joined #rubygems
yashshah- has quit [Ping timeout: 252 seconds]
dvu_ has joined #rubygems
dvu has quit [Ping timeout: 256 seconds]
mbull9 has quit [Remote host closed the connection]
cowboyd has quit [Remote host closed the connection]
fromonesrc has joined #rubygems
cowboyd has joined #rubygems
fromonesrc_ has joined #rubygems
fromonesrc has quit [Ping timeout: 256 seconds]
fromonesrc_ is now known as fromonesrc
benchMark has joined #rubygems
cowboyd has quit [Remote host closed the connection]
cowboyd has joined #rubygems
<fromonesrc>
I'm sure this has been brought up before but is it unreasonable to strictly tie gem versions to something like a tag on github?
<fromonesrc>
how do we know that version x on rubygems matches what is on github?
<fromonesrc>
I think the answer is "we don't and that's by design" but I think it would be preferable to have the matching source available
<tbuehlmann>
you just can't match a repo tag to a gem version
<fromonesrc>
because the tag could be deleted or modified or…?
<tbuehlmann>
on the one hand, yes. on the other hand: a rubygem doesn't need a github repo
<fromonesrc>
this might be ignorant of a larger topic here but I think that's a problem
<fromonesrc>
it's a problem that the source is not accessible or easily traced down
<tbuehlmann>
I wouldn't want to force someone to use github
<fromonesrc>
why not?
<fromonesrc>
(again, ignorance here)
<tbuehlmann>
personal preferences
dvu has joined #rubygems
<tbuehlmann>
people wouldn't like it if you forced them to use rubyforge, right?
<tbuehlmann>
I mean, what's the difference?
<fromonesrc>
I'd like to see rubygems take an approach similar to travis and codeclimate wherein github is the source of truth
<fromonesrc>
travis and codeclimate are immensely popular despite "forcing" users into using github
<tbuehlmann>
I don't use travis anymore since github's permission change
<tbuehlmann>
not sure about codeclimate, but last time I checked, they wanted permission to write/change my repo
<fromonesrc>
so the main reason I bring this up is that let's say I have a popular gem which gets hijacked. someone pushes a malicious release to rubygems. there is no requirement of history of that code change (in github or otherwise that I know of).
<fromonesrc>
this is a big problem IMO
havenwood has joined #rubygems
<tbuehlmann>
what about signing your gem?
<fromonesrc>
I'm pro gem signing
<fromonesrc>
I'd even prefer rubygems displaying code diffs on the gem page to what we have now
newUser1234 has quit [Remote host closed the connection]
<fromonesrc>
but to me that is crossing into something github does best so why not leverage their platform?
<tbuehlmann>
that's your opinion, others might think different. I also like github, but I would not generalise it and force ppl to use it
havenwood has quit [Ping timeout: 252 seconds]
<fromonesrc>
cool, thanks. just looking for feedback on the idea.
<tbuehlmann>
but well, corrupt gems are a problem yet..
pipework has joined #rubygems
tbuehlmann has quit [Remote host closed the connection]
jcaudle has quit [Quit: jcaudle]
jcaudle has joined #rubygems
newUser1234 has joined #rubygems
mootpointer has quit [Quit: Computer has gone to sleep.]
cowboyd has quit [Remote host closed the connection]