search for: pending_user

Displaying 6 results from an estimated 6 matches for "pending_user".

2005 Dec 29
7
belongs_to causing NoMethodError exceptions ... ?
...to take a while to explain. Basic idea: Creating a User requires that the user enter an email address and activation key that matches an existing PendingUser. After creating the user successfully, that pending user should be marked as "used". The problem: When I add a belongs_to :pending_user declaration to the User class, attempting to save a User yields this exception (taken here from the output of a simple test case -- code below.) You''ll note some lines in the User class with two hashes ''##'' preceding them -- those are alternate statements that avo...
2009 May 29
0
[PATCH 4/4] lguest: don't force VIRTIO_F_NOTIFY_ON_EMPTY
VIRTIO_F_NOTIFY_ON_EMPTY indicates to the Guest that we will hit them with an interrupt every time the xmit queue is emptied. Because it results in lots of tx interrupts, modern Guests probably don't want it, so let's only force it when they accept the option. Signed-off-by: Rusty Russell <rusty at rustcorp.com.au> --- Documentation/lguest/lguest.c | 27
2009 Sep 21
0
[PATCH 5/5] lguest: don't force VIRTIO_F_NOTIFY_ON_EMPTY
VIRTIO_F_NOTIFY_ON_EMPTY indicates to the Guest that we will hit them with an interrupt every time the xmit queue is emptied. Because it results in lots of tx interrupts, modern Guests probably don't want it, so let's only force it when they accept the option. Signed-off-by: Rusty Russell <rusty at rustcorp.com.au> --- Documentation/lguest/lguest.c | 25 +++++++++++++++++++++----
2009 May 29
0
[PATCH 4/4] lguest: don't force VIRTIO_F_NOTIFY_ON_EMPTY
VIRTIO_F_NOTIFY_ON_EMPTY indicates to the Guest that we will hit them with an interrupt every time the xmit queue is emptied. Because it results in lots of tx interrupts, modern Guests probably don't want it, so let's only force it when they accept the option. Signed-off-by: Rusty Russell <rusty at rustcorp.com.au> --- Documentation/lguest/lguest.c | 27
2009 Sep 21
0
[PATCH 5/5] lguest: don't force VIRTIO_F_NOTIFY_ON_EMPTY
VIRTIO_F_NOTIFY_ON_EMPTY indicates to the Guest that we will hit them with an interrupt every time the xmit queue is emptied. Because it results in lots of tx interrupts, modern Guests probably don't want it, so let's only force it when they accept the option. Signed-off-by: Rusty Russell <rusty at rustcorp.com.au> --- Documentation/lguest/lguest.c | 25 +++++++++++++++++++++----
2007 Jan 26
0
Problems with assert_select in integration tests
...;"200 OK", "type"=>"text/html; charset=utf-8", "cookie"=>[], "Cache-Control"=>"no-cache", "Content-Length"=>2247}, @session=#<CGI::Session:0x246e2b0 @session_id="d0060c4ee33f3d58c0ef83bbfa107b6f", @data={:pending_user=>{"password_confirmation"=>"T3st!ng", "username"=>"TestUser", "account_type"=>"Personal", "password"=>"T3st!ng", "email"=>"me-hcDgGtZH8xPR7s880joybQ@public.gmane.org"}, "flash&...