The child process inherits signal handlers from the parent, but not the pending signal. After forking try installing the signal handler for SIGTRAP at a place in code where the child process executes after forking. If you don’t handle SIGTRAP, the default action is that the child is terminated. If you want to debug the … Read more
SIGWINCH As a matter of fact, @Stefano is right: SIGWINCH means SIGNAL WINDOWS CHANGE and is sent automatically when a terminal detects a change in it’s windows size to allow for a redraw. SIGWINCH for apache2 But unfortunately apache2 process poorly misuses this signal (in the way they divert its first meaning), but for their … Read more
To get all the terminal control character assignments: stty -a
Are there any other circumstances where they[destructors] will not be called? Long jumps: these interfere with the natural stack unwinding process and often lead to undefined behavior in C++. Premature exits (you already pointed these out, though it’s worth noting that throwing while already stack unwinding as a result of an exception being thrown leads … Read more
Many system calls will report the EINTR error code if a signal occurred while the system call was in progress. No error actually occurred, it’s just reported that way because the system isn’t able to resume the system call automatically. This coding pattern simply retries the system call when this happens, to ignore the interrupt. … Read more
Can’t be done. The current user is only available via the request, which is not available when using purely model functionality. Access the user in the view somehow.
Possibly a better idea is to mock out the functionality inside the signal handler rather than the handler itself. Using the OP’s code: @receiver(post_save, sender=User, dispatch_uid=’myfile.signal_handler_post_save_user’) def signal_handler_post_save_user(sender, *args, **kwargs): do_stuff() # <– mock this def do_stuff(): … do stuff in here Then mock do_stuff: with mock.patch(‘myapp.myfile.do_stuff’) as mocked_handler: self.assert_equal(mocked_handler.call_count, 1)
Also look into celery (or more specifically django-celery). It is an async task scheduler / handler. So your post_save signal handler creates a task, which is picked up and executed through celery. That way you still have your speedy application, while the heavy lifting is performed async, even on a different machine or batch of … Read more
Simple answer: you cannot. Longer answer: the uninterruptable sleep means the process will not be woken up by signals. It can be only woken up by what it’s waiting for. When I get such situations eg. with CD-ROM, I usually reset the computer by using suspend-to-disk and resuming.
I think I figured out a way to do this. There is a ‘raw’ parameter in the kwargs passed in along with signals so I can replace my test above with this one: if (kwargs.get(‘created’, True) and not kwargs.get(‘raw’, False)): Raw is used when loaddata is running. This seems to do the trick. It is … Read more