HEAD should be stable once again. Please do try it out. The core team
is using it again, so it should be good to your apps too.
Cheers, and thanks for your patience,
Nicholas Seckar
___
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http:
On 3-Feb-06, at 3:31 PM, Michael Koziarski wrote:I can reproduce this, I'll take a look into it. But I think it's something Nicholas did Muhahaha.Edge is going thru a period of roughness. It'll be a little rocky for a while, and has been since the first reloading changes were checked in on r
> I've seen this and some other weird error in another project too. I'm
> sure it'll get sorted out this weekend. Ulysses wasn't seeing any
> errors, and I'm seeing two different errors in two apps. Very
> strange.
I can reproduce this, I'll take a look into it. But I think it's
something Ni
On 2/3/06, Francois Beausoleil <[EMAIL PROTECTED]> wrote:
> 2006/2/3, Jeremy Hopple <[EMAIL PROTECTED]>:
> > Anyone else seen this?
>
> Confirmed. Win XP SP2, Ruby 1.8.2, Edge Rails (r3524).
>
> WEBrick does that. Haven't tried SCGI yet. If you look at
> http://article.gmane.org/gmane.comp.lang.
2006/2/3, Jeremy Hopple <[EMAIL PROTECTED]>:
> Anyone else seen this?
Confirmed. Win XP SP2, Ruby 1.8.2, Edge Rails (r3524).
WEBrick does that. Haven't tried SCGI yet. If you look at
http://article.gmane.org/gmane.comp.lang.ruby.rails/45409
You'll see the stack trace I got. Forget the rest o
I'm on the road and haven't been able to dig in, but it appears that with the latest version of Edge Rails I'm getting 404 errors for every request sent to edge rails via webrick on windows. If I revert back to revision 3518, all is well again. It appears that something in r3519 causes 404s on Wi
