drbrain changed the topic of #rubygems to: RubyGems 2.1.0.rc.1: http://bit.ly/rubygems-2-1-0-rc-1 – Latest status: http://twitter.com/rubygems_status and http://status.rubygems.org
TheComrade has joined #rubygems
DanKnox is now known as DanKnox_away
vertis has joined #rubygems
envygeeks has joined #rubygems
<envygeeks> drbrain: Github doesn't support multiple CNAMES in the CNAME file
<drbrain> envygeeks: ok
<drbrain> what should I do?
<drbrain> I reverted the CNAME change so it only has one now
<drbrain> I guess we need a Real Host that can redirect?
<envygeeks> drbrain: if you guys need I can provide a proxy for you via my servers otherwise it might be easier just to have rubygems servers to do it?
<drbrain> probably easier to have the rubygems servers do it
<drbrain> I'll ask evan about setting that up tomorrow
<drbrain> judging by his tweets he's either eating delicious pastries or watching sportsball
<envygeeks> you could also use the nginx buildpack for heroku and do a proxy that way using a custom configuration and avoid needing to use rubygems server
<envygeeks> drbrain: ^
<drbrain> envygeeks: cool
<drbrain> the server hosting docs.rubygems.org died, and I was going to retire it tomorrow anyhow (as guides. has all that now)
<drbrain> I could also host the redirector on my other server, but I'd rather have all this in a rubygems repo somewhere
<envygeeks> that would be mighty easy to fix then, you could setup a repo with gh-pages and do a meta redirect with a simple index.html
<drbrain> hrm, yes
<drbrain> but then we'd need a useless docs.rubygems.org repo hanging out in the rubygems org
<envygeeks> I don't mind having useless repos hanging about for a few weeks while ya'll work on more important things and figure out what you want, if docs.rubygems.org already points to github I'll do that up for ya'll
<envygeeks> I mean I'll put it on my account :P
<drbrain> envygeeks: since docs.rubygems.org has been up and down for the past 4 days, I don't think one more will hurt anything :D
<envygeeks> oh fair enough then, if nobody has filed a ticket it's not even worth it
<drbrain> it would be best to have it be 410 Gone with a pointer to guides.rubygems.org than redirecting
dwradcliffe has joined #rubygems
dwradcliffe has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<drbrain> I like that somebody found an important bug the day before an important release
<drbrain> I especially like that the important bug had a very simple fix
<envygeeks> I wish most of the bugs I had to fix were that easy, I've been working on a bug this guy introduced into this software for 7 hours now
<drbrain> fortunately evan's resolver is very clean
<drbrain> so I was able to walk my way back to its source
<drbrain> then over to the test where I was all: oh! … Oh! … OH‼
<envygeeks> It's those kind of moments that make me smile a bit, you know that rare crack in my expressionless face
<drbrain> "we didn't have to do X to the expected value, so why are we doing it to Y?" flashed across my mind
jcaudle has joined #rubygems
DanKnox_away is now known as DanKnox
kgrz has joined #rubygems
kgrz has quit [Client Quit]
DanKnox is now known as DanKnox_away
hakunin has joined #rubygems
TheComrade has quit [Quit: TheComrade]
lsegal` has joined #rubygems
lsegal has quit [Read error: Connection reset by peer]
lsegal` has quit [Read error: Connection reset by peer]
lsegal has joined #rubygems
lsegal` has joined #rubygems
lsegal has quit [Read error: Connection reset by peer]
lsegal` has quit [Read error: Connection reset by peer]
lsegal has joined #rubygems
envygeeks has left #rubygems [#rubygems]
randym_ has quit [Quit: Connection closed for inactivity]
DanKnox_away is now known as DanKnox
lsegal` has joined #rubygems
lsegal has quit [Read error: Connection reset by peer]
jonahR has quit [Quit: jonahR]
lsegal` has quit [Client Quit]
JonathanT has joined #rubygems
yanap_ has joined #rubygems
dangerousdave has joined #rubygems
vertis has quit [Ping timeout: 264 seconds]
dangerousdave has quit [Quit: Leaving...]
dangerousdave has joined #rubygems
dangerousdave has quit [Quit: Leaving...]
adambeynon has joined #rubygems
vertis has joined #rubygems
dangerousdave has joined #rubygems
vertis has quit [Ping timeout: 256 seconds]
vertis has joined #rubygems
Elhu has joined #rubygems
yanap_ has quit [Remote host closed the connection]
dwradcliffe has joined #rubygems
tcopeland has quit [Quit: Leaving.]
jcaudle has quit [Quit: jcaudle]
huoxito has joined #rubygems
jcaudle has joined #rubygems
tcopeland has joined #rubygems
marpaia has joined #rubygems
DanKnox is now known as DanKnox_away
jfoy has joined #rubygems
rhythm_and_code has quit [Quit: rhythm_and_code]
rhythm_and_code has joined #rubygems
Elhu has quit [Quit: Computer has gone to sleep.]
Elhu has joined #rubygems
Elhu has quit [Client Quit]
DanKnox_away is now known as DanKnox
DanKnox is now known as DanKnox_away
jfoy has quit [Quit: jfoy]
dwradcliffe has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
DanKnox_away is now known as DanKnox
havenwood has joined #rubygems
dangerousdave has quit [Read error: Connection reset by peer]
dangerousdave has joined #rubygems
dangerousdave has quit [Client Quit]
dangerousdave has joined #rubygems
jaimef has quit [Excess Flood]
rhythm_and_code has quit [Quit: rhythm_and_code]
jaimef has joined #rubygems
Elhu has joined #rubygems
adambeynon has quit [Quit: ["Textual IRC Client: www.textualapp.com"]]
huoxito has quit [Quit: Leaving]
rhythm_and_code has joined #rubygems
TheComrade has joined #rubygems
sferik has joined #rubygems
dangerousdave has quit [Quit: Leaving...]
havenwood has quit [Remote host closed the connection]
DanKnox is now known as DanKnox_away
havenwood has joined #rubygems
DanKnox_away is now known as DanKnox
havenwood has quit [Read error: Connection reset by peer]
havenwood has joined #rubygems
havenwood has quit [Read error: Connection reset by peer]
havenwood has joined #rubygems
jonahR has joined #rubygems
dangerousdave has joined #rubygems
dangerousdave has quit [Read error: Connection reset by peer]
Dave-_ has joined #rubygems
tbuehlmann has joined #rubygems
Elhu has quit [Quit: Computer has gone to sleep.]
dangerousdave has joined #rubygems
Dave-_ has quit [Read error: Connection reset by peer]
jfoy has joined #rubygems
jfoy has quit [Client Quit]
Elhu has joined #rubygems
jonahR has quit [Quit: jonahR]
jonahR has joined #rubygems
jonahR has quit [Client Quit]
Elhu has quit [Quit: Computer has gone to sleep.]
Elhu has joined #rubygems
Elhu has quit [Client Quit]
mando has joined #rubygems
mando has quit [Remote host closed the connection]
mando has joined #rubygems
jonahR has joined #rubygems
tcopeland has quit [Quit: Leaving.]
jfoy has joined #rubygems
jcaudle has quit [Quit: jcaudle]
martinisoft has joined #rubygems
sferik has quit [Quit: ["Textual IRC Client: www.textualapp.com"]]
marpaia has quit [Quit: WeeChat 0.4.1]
marpaia has joined #rubygems
huoxito has joined #rubygems
tbuehlmann has quit [Remote host closed the connection]
sferik has joined #rubygems
<drbrain> evan: ping
<evan> kpasta?
<drbrain> regarding #637, I'm inclined to lean towards headius
<drbrain> I think the contract should be around activation and modifying $LOAD_PATH
<evan> lean towards in what way? merge it?
<drbrain> if we have the lock cover "I want this gem" to "$LOAD_PATH is ready to require that gem" that should be enough, rigth?
<drbrain> yes, merge it
<drbrain> but I'm not sure my idea (above) is the one in the patch
<drbrain> the lock doesn't prevent some other party from modifying $LOAD_PATH anyhow, it just makes sure rubygems is consistent inside
<evan> right
vertis has quit [Quit: Leaving.]
<evan> his patch keeps $LOAD_PATH manipulation locked
<evan> so it's consistent
<drbrain> if we just want rubygems to not stomp itself the behavior change is just an implementation detail we're free to modify, correct?
<evan> the case he's talking about exposes where threads activate different gems
<evan> and because of the unlocking, they'd pick up files from eachothers paths
<evan> but thats not an issue
<evan> now that I think about it
<evan> because that can't happen with the way we manage $LOAD_PATH
<drbrain> yes ↑ that's what I was thinking
<evan> ok cool
<evan> merge!
<drbrain> I'll summarize our discussion
<drbrain> then merge
<evan> k
marpaia has quit [Quit: WeeChat 0.4.1]
<drbrain> I am going to rename Gem.resolve! to Gem.resolve
<drbrain> hrm, test failure
tcopeland has joined #rubygems
tjbiddle has joined #rubygems
jstr has joined #rubygems
<drbrain> oh, I see what's wrong
<evan> what is it?
<drbrain> the LoadError handler was moved out of Kernel#require
<drbrain> which it depends upon to work correctly
<drbrain> evan: I think we might need more use of the monitor
<drbrain> what about Gem.needs?
<evan> probably
<drbrain> I think anywhere Gem::Specification#activate is called
<evan> well
<evan> I want to refactor things
<drbrain> I'm unsure
<evan> to make the locking much clearer
* drbrain nods
<evan> rather than ploping down monitors all over
<evan> basically, the global state needs to pulled out into something that contains the sychronization
<drbrain> I'm adding it to try_activate because we need to cover that for headius' refactor
<evan> I don't want to go back to SourceIndex
<evan> but just something that is internal only that can do the locking
<drbrain> SourceIndex was a five things in one class
<evan> ah yeah
<evan> it needs to be in try_activate.
<evan> what is the 2.1 timeframe?
<drbrain> just around the begin/rescue/end, or the whole method though?
<evan> I can carve out some time to start the refactoring
<drbrain> since the activated? flag is set after it's in $LOAD_PATH it seems fine
<drbrain> I want to release 2.1 today
<evan> k
<evan> then we should not to headius change.
<evan> we need to put it through more rigor
<drbrain> ok, I'll roll it back
<evan> given this is a non-API change, we can roll it out in 2.1.1
* drbrain nods
<evan> i'd rather we can futz with it
<evan> esp since you'll want to merge 2.1 to ruby-core I suspect
<drbrain> for the security issue, yes
<evan> k
<drbrain> at least I can commit this work and git format-patch it to add to #637
<evan> sure
sferik has quit [Quit: Computer has gone to sleep.]
<drbrain> how do I revert this merge properly?
<drbrain> I'm reading git revert's -m option but it is only confusing me
<evan> oh
<drbrain> or do I just revert the one commit?
<evan> -m takes the sha1 of the thing you want to revert to
<evan> it's actually a 0 or 1
<evan> though.
<evan> you're selecting the parent
<evan> you want to select his commit
sferik has joined #rubygems
<evan> merge reversion is confusing
<evan> oh
<drbrain> which one is 0 and which one is 1?
<evan> do 'git show'
<evan> the order they're listed
<evan> is the order.
<evan> git revert -m 1 HEAD
<evan> is what you want
<evan> it's 1 indexed
<evan> AND you select the branch you want to retain
<evan> not the one to revert
<evan> confusingly
<evan> I just did it locally
<drbrain> yeah
<evan> I can push if you want.
<drbrain> please
<evan> dunzo.
<drbrain> I find it odd I can't pick the mainline by SHA
<evan> agreed.
<evan> I think so that you can't pick random SHA1s
<evan> though it could just validate it
<evan> whatever.
<evan> git be crazy that way.
jaimef has quit [Excess Flood]
<drbrain> yeah
jaimef has joined #rubygems
sferik has quit [Quit: ["Textual IRC Client: www.textualapp.com"]]
jonahR has quit [Quit: jonahR]
dangerousdave has quit [Ping timeout: 264 seconds]
mando has quit [Remote host closed the connection]
havenn has joined #rubygems
tjbiddle_ has joined #rubygems
havenn is now known as havenwood_
havenwood has quit [Read error: Connection reset by peer]
tjbiddle has quit [Read error: Connection reset by peer]
tjbiddle_ is now known as tjbiddle
akahn has quit [Ping timeout: 256 seconds]
ckrailo has quit [Ping timeout: 256 seconds]
havenwood_ is now known as havenwood
revans has joined #rubygems
tjbiddle_ has joined #rubygems
tjbiddle has quit [Ping timeout: 240 seconds]
tjbiddle_ is now known as tjbiddle
vertis has joined #rubygems
vertis has quit [Client Quit]
vertis has joined #rubygems
vertis1 has joined #rubygems
vertis has quit [Read error: Connection reset by peer]
jaimef has quit [Excess Flood]
jaimef has joined #rubygems