Ensure correct Async type is used for completion callbacks
Fix unit test to verify correct Async type is used for callback
Raise exception with correct traceback

This corrects issue #143 where exceptions are raised in the results
processor with the incorrect traceback.
Merge pull request #145 from tylertreat-wf/fix_traceback

Raise exception with correct traceback
Merge pull request #142 from tylertreat/completion_cb_fix

Ensure correct Async type is used for callbacks
completion_retry - If a marker/context is already complete, re-execute the completion tasks, in case they failed to execute on the first attempt.
Revert "completion_retry - If a marker/context is already complete, re-execute the completion tasks, in case they failed to execute on the first attempt."

This reverts commit 33a863c13ce60534b9b0a76caf8b27dba50ccff8.
completion_retry - Update Marker to complete and submit completion handler and cleanup within the same transaction.  Added unit test to ensure marker is not updated to complete when Exception is thrown starting completion task.
Merge pull request #146 from markshaule-wf/completion_retry

completion_retry - If a marker/context is already complete, re-execute the completion tasks, in case they failed to execute on the first attempt.
Update version to 1.1.0

New release time. 1.1.0
Add parent id and request id to Async

Add a parent id and request id to the Async object. The parent id will be passed
down to "children" asyncs. This will allow us to track the chain/graph of asyncs
without developer intervention.
Switch _function_path to just return function_path

Better handling of deprecated function to ensure backwards compatibility.
Fix stupid property bug

function_path is a property not a method so don't parens is :)
Merge pull request #147 from beaulyddon-wf/add_parent_id_to_asyncs

Add parent id and request id to Async