You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by Craig Russell <cr...@oracle.com> on 2016/02/21 23:22:18 UTC
NoMethodError in https://whimsy.apache.org/board/subscriptions/
Does this warrant a JIRA?
#<NoMethodError: undefined method `id' for nil:NilClass> /var/www/whimsy/board/subscriptions.cgi:135:in `map' /var/www/whimsy/board/subscriptions.cgi:135:in `block (2 levels) in <main>' /var/www/whimsy/board/subscriptions.cgi:22:in `block in <main>'
Re: NoMethodError in https://whimsy.apache.org/board/subscriptions/
Posted by sebb <se...@gmail.com>.
On 22 February 2016 at 02:08, Sam Ruby <ru...@intertwingly.net> wrote:
> On Sun, Feb 21, 2016 at 5:22 PM, Craig Russell <cr...@oracle.com> wrote:
>> Does this warrant a JIRA?
>>
>> #<NoMethodError: undefined method `id' for nil:NilClass> /var/www/whimsy/board/subscriptions.cgi:135:in `map' /var/www/whimsy/board/subscriptions.cgi:135:in `block (2 levels) in <main>' /var/www/whimsy/board/subscriptions.cgi:22:in `block in <main>'
>
> Fixed on whimsy-test (I'm guessing by Sebb?
I've not worked on that code.
> The root problem is not
> being able to find the chair for "Portable Runtime"). I've changed
> the script to pick up the latest code for the library, and fixed two
> unrelated regressions. The latest fix (a performance regression)
> should be deployed within the next 30 minutes.
>
> - Sam Ruby
Re: NoMethodError in https://whimsy.apache.org/board/subscriptions/
Posted by Sam Ruby <ru...@intertwingly.net>.
On Sun, Feb 21, 2016 at 5:22 PM, Craig Russell <cr...@oracle.com> wrote:
> Does this warrant a JIRA?
>
> #<NoMethodError: undefined method `id' for nil:NilClass> /var/www/whimsy/board/subscriptions.cgi:135:in `map' /var/www/whimsy/board/subscriptions.cgi:135:in `block (2 levels) in <main>' /var/www/whimsy/board/subscriptions.cgi:22:in `block in <main>'
Fixed on whimsy-test (I'm guessing by Sebb? The root problem is not
being able to find the chair for "Portable Runtime"). I've changed
the script to pick up the latest code for the library, and fixed two
unrelated regressions. The latest fix (a performance regression)
should be deployed within the next 30 minutes.
- Sam Ruby