Not a critical blocker, but the first patch in :
http://rails.lighthouseapp.com/projects/8994/tickets/2000-patch-for-http-digest-authentication-uri-comparison#ticket-2000-11
has an easy correction to the earlier commit. Other issues re HTTP
Digest auth can wait, although I believe it is broken
Here's a little lib I wrote that implements support for after_commit
callbacks:
http://gist.github.com/76868
On Mon, Mar 9, 2009 at 2:43 PM, Alex MacCaw wrote:
>
> Yes, I'm still getting the error.
>
> On Mar 9, 2:39 pm, Jan De Poorter wrote:
> > As far as I can see observers after_save calls
I'd say this is critical, but I don't know who else would agree:
http://rails.lighthouseapp.com/projects/8994/tickets/2115-malformed-xml-request-returns-vague-error
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Rub
This would be really helpful for us here:
http://rails.lighthouseapp.com/projects/8994/tickets/1874-add-short-hand-definition-for-postgresql-xml-data-type
Tks
On Mar 10, 1:32 pm, Milhouse wrote:
> Not a critical blocker, but the first patch in :
> http://rails.lighthouseapp.com/projects/8
I have a patch that fixes a lot of the fragility in the current gems:*
rake tasks, as well as making unpacking a lot more stable.
Please check it out at:
http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2195-patch-fix-the-gem-dependency-system-in-rails#ticket-2195-2
The curren
Not a patch, but last I checked assert_select_email didn't work -
undefined method in ActionMailer::TestCase subclasses.
On Mar 9, 8:03 am, Pratik wrote:
> Hey all,
>
> As 2.3 RC2 is out, the plan is to have the 2.3 final release out as
> early as possible. So we'd like to make the last call fo
Pratik wrote:
> Hey all,
>
> As 2.3 RC2 is out, the plan is to have the 2.3 final release out as
> early as possible. So we'd like to make the last call for patches.
Minor regression, "auto_link should not linkify URLs in the middle of
a tag":
http://rails.lighthouseapp.com/projects/8994/ticket
When using rails 2.3.1 (does not apply to 2.3.0) I am having issues
with destroying sessions (or logging out). It also only applies when
using passenger.
Conditions:
Rails 2.3.1
Passenger 2.0.6
Restful Authentication or Clearance
When using mongrel everything works as it should.
--~--~
When using rails 2.3.1 (does not apply to 2.3.0) I am having issues
with destroying sessions (or logging out). It also only applies when
using passenger.
Conditions:
Rails 2.3.1
Passenger 2.0.6
Both Restful Authentication and Clearance
When using mongrel everything works as it should.
Marshall
I ran into the same thing, I believe it's related to some of the Rack
changes and is resolved in the Passenger 2.1.1 beta.
On a related Lighthouse ticket someone suggested that this issue isn't
that well publicised and I'd tend to agree. Is there anything we can
do to make sure this doesn't trip
On Mar 9, 9:03 am, Pratik wrote:
> Hey all,
>
> As 2.3 RC2 is out, the plan is to have the 2.3 final release out as
> early as possible. So we'd like to make the last call for patches. If
> you have any pending patches that you want in 2.3 final release,
> please speak now.
> --
> Cheers!
> -
Marshall,
Check out Passenger 2.1.1 at
http://blog.phusion.nl/2009/03/01/phusion-passenger-211-beta-released-thanks-sponsors/
There appears to be some compatibility issues with 2.0.6.
James
On Mar 10, 9:28 am, mwhuss wrote:
> When using rails 2.3.1 (does not apply to 2.3.0) I am having issues
Yup. You'll need 2.1.1 to run Rails 2.3. I just had a chat with Hongli
and he said he'll be trying his best to push the passenger release out
asap.
On Tue, Mar 10, 2009 at 5:15 PM, James Miller wrote:
>
> Marshall,
>
> Check out Passenger 2.1.1 at
> http://blog.phusion.nl/2009/03/01/phusion-pass
I just installed passenger 2.1.1 and tested both clearance and restful-auth,
it fixed the issue with both.
Marshall
On Tue, Mar 10, 2009 at 1:16 PM, Pratik wrote:
>
> Yup. You'll need 2.1.1 to run Rails 2.3. I just had a chat with Hongli
> and he said he'll be trying his best to push the pass
This bug here stops Litespeed from working at all on RC2.
http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2198-litespeed-compatibility
On Mar 9, 5:03 am, Pratik wrote:
> Hey all,
>
> As 2.3 RC2 is out, the plan is to have the 2.3 final release out as
> early as possible. So
On Tue, Mar 10, 2009 at 17:41, horsfa...@googlemail.com <
horsfa...@googlemail.com> wrote:
>
> I ran into the same thing, I believe it's related to some of the Rack
> changes and is resolved in the Passenger 2.1.1 beta.
As mentioned on the "last call for patches" thread: Rails 2.3 is not
support
I consider this Mocha compatibility very important.
http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2060-installation-of-miniunit-causes-test-to-fail#ticket-2060-4
On Mar 9, 8:03 am, Pratik wrote:
> Hey all,
>
> As 2.3 RC2 is out, the plan is to have the 2.3 final release o
On Mar 9, 8:03 am, Pratik wrote:
> Hey all,
>
> As 2.3 RC2 is out, the plan is to have the 2.3 final release out as
> early as possible. So we'd like to make the last call for patches. If
> you have any pending patches that you want in 2.3 final release,
> please speak now. Not very keen on acce
Action caching is broken with string keys.
This means you cannot cache XML or JSON responses, for instance, if you use
a string for cache key.
Failing test + fix http://rails.lighthouseapp.com/projects/8994/tickets/1585
--~--~-~--~~~---~--~~
You received this messa
I've tested the new feature for processing records in batches, and I
noticed the each method does not work with named_scopes. I attempted
to make a simple patch, but added no tests yet.
I think it's a really simple change that can help developers a lot
saving time and making the code more DRY.
h
I have a question about peoples opinions about how nested named_scopes
should handle :order options.
What are your opinions about the correct behavior for the following
chained named_scopes?
Take the model:
class Developer < ActiveRecord::Base
named_scope :by_last_name, :order => 'last_name'
I'd like to see this fixed:
http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2208-rails-231-runs-into-a-segfault
, as it concerns Ruby 1.9 and Mysql.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Group
22 matches
Mail list logo
