[Backgroundrb-devel] [PATCH] x 2 - Fix for "null pointer exception" when ask_status is called before worker is run, and docfixes

Cheah Chu Yeow chuyeow at gmail.com
Wed Jan 9 01:29:37 EST 2008


Sorry for attaching patches in emails to the mailing list, but I'm still
unable to login to Devjavu for Backgroundrb (I'm able to login just fine for
Merb's Devjavu and submitted a ticket successfully).
Anyway, I encountered a bug when trying to #ask_status of a worker before
it's run (or rather, before its result_hash has been set to something). Not
sure why it's no longer being initialized to an empty hash (since
http://backgroundrb.devjavu.com/changeset/279). I've attached a patch,
defaults_for_packet_master.diff for this.

update_readme.diff attempts to format the README so that it displays better
in HTML and also removes mention of worker tests being generated from the
worker_generator.

Let me know if there's a better way for me to submit patches!

Cheers,

Chu Yeow
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080109/11cb0823/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: update_readme.diff
Type: application/octet-stream
Size: 10804 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080109/11cb0823/attachment-0002.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: defaults_for_packet_master.diff
Type: application/octet-stream
Size: 1250 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080109/11cb0823/attachment-0003.obj 


More information about the Backgroundrb-devel mailing list