[Rails] Newbie .. nil object and missing something

Bill Walton bill.walton at charter.net
Mon Apr 24 16:36:51 GMT 2006


As a follow up, I too can reproduce the 'NoMethodError in Recipe#list.rhtml' 
by starting the cookbook app that comes with InstantRails by pointing the 
browser to 'http://localhost:300/recipe/list.rhtml'.  That's reproducible on 
the two boxes I have here: WinXP - Home Addition and Win2K SP 4.

Tom Mornini,

You caught this.  You should get the 'glory' (aka, 'the extra work' ;-) ) 
You going to submit the bug report?

Best regards,
Bill


----- Original Message ----- 
From: "Bill Walton" <bill.walton at charter.net>
To: <rails at lists.rubyonrails.org>
Sent: Monday, April 24, 2006 11:11 AM
Subject: Re: [Rails] Newbie .. nil object and missing something


> Hi Kevin,
>
> A couple of additional thoughts below...
>
> Kevin Olbrich wrote:
>
>
>> Actually, I can reproduce his problem using
>> the standard cookbook app  that comes with
>> InstantRails.  At least in development mode, if you
>> request the .rhtml file, you will get it.  I don't know
>> if production mode closes this hole or not.
>>
>> It does not seem to be anything specific to his own
>> configuration.
>
> Perfect!  Not speaking for anybody but me... thanks much for making the 
> time to test that.  If the two of you could find a way to spend just a 
> little additional time on this, it would be great to validate something.
>
> To both of you, what exactly is your system configuration? For Robert, 
> what about your friend's config.  I ask because for the past week I have, 
> and still am, spending quite a bit of time testing / debugging a segment 
> fault problem that's specific, at least, to Windows 2000 Pro SP3 and SP4. 
> Can't get the problem to display itself on XP.  That doesn't mean it's not 
> a bug. It means that it's a bug that only shows itself in a specific 
> config.  It either needs to be fixed, or if the effort to fix it for that 
> config is not justified from a 'market share' perspective, then it at 
> least needs to be documented.  It may be that both you and Robert are 
> running the same config and that his friend is running a different one. 
> It would be good to validate that this is not config-specific.
>
> Independent of the results above, it seems to me we need 'a call' from the 
> Rails core team as to this behavior.  Is there a 'better' way than just 
> going ahead and submitting it as a bug?
>
> Best regards,
> Bill
>
> It may be that Rails is 'working as designed / intended' and there's 
> something that needs to be *highlighted* in the documentation.  It may 
> already be documented, for example, that this is allowed in development 
> for reason 'X' and that before moving a Rails app into production, we need 
> to do 'A', 'B', and 'C'.
> _______________________________________________
> Rails mailing list
> Rails at lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
> 



More information about the Rails mailing list