Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Defining Actions without a Param causes strange errors

#9

Documented here: http://pastie.caboo.se/141304

The client will report EOF because the server just fails to respond when it expects a response (rightly so).

The server will report:

Unexpected error while processing request: can't convert Hash into Integer

The server's method was defined as:

def test
  ok("Worked! You sent '#{@req.POST['foo'].inspect}'")
end

The method lacks an argument to hold the params. This should give a normal exception, but for some reason does not. This is a strange error.

In order to fix this, for now, all actions require a parameter. However, this needs long-term adjustment in the form of allowing for actions to nor require params arguments.

Reported by Matt Todd · January 20th, 2008 @ 06:38 PM

State: resolved
Milestone: Release 0.4.0
Assigned to: Matt Todd Matt Todd

Activity

  1. Matt Todd
    Matt Todd
    • State changed from new to resolved

    Decided to just remove the requirement for a params argument instead opting for a method called params which accesses the params stored in @params.

    This issue is resolved in revision 39.

    February 3rd, 2008 @ 11:07 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.