From: Christopher Allan Webber Date: Wed, 27 Apr 2016 22:08:34 +0000 (-0500) Subject: actors: Handle messages/coroutines in want of reply and errors. X-Git-Tag: v0.2.0~17 X-Git-Url: https://jxself.org/git/?a=commitdiff_plain;h=413f6d981a7c4e11f2270c7bd52527d3e5a3a2c1;p=8sync.git actors: Handle messages/coroutines in want of reply and errors. If we call another method and we're "waiting" on a reply, and an error happens in the other function so that it can't continue, that shouldn't leave our coroutine hanging around in the waiting-coroutines hashmap forever. Instead, we raise it and throw an error warning about that. (More ideally, we'd like to raise this inside of the send-message type methods but that seems to cause a SIGABRT. Yikes!) * 8sync/systems/actors.scm (hive-reply-with-error): New method. (hive-process-message): Update call-catching-coroutine to reply with an eror if an uncaught exception happens. Update resume-waiting-coroutine to recognize whether the message has a '*reply* action or not. If not, remove the coroutine (we'll never get a reply) and throw an error. --- diff --git a/8sync/systems/actors.scm b/8sync/systems/actors.scm index e33a88b..e5dd053 100644 --- a/8sync/systems/actors.scm +++ b/8sync/systems/actors.scm @@ -459,6 +459,27 @@ more compact following syntax: '*forward* `((original . ,message)))) +(define-method (hive-reply-with-error (hive ) original-message + error-key error-args) + ;; We only supply the error-args if the original sender is on the same hive + (define (orig-actor-on-same-hive?) + (equal? (hive-id hive) + (address-hive-id (message-from original-message)))) + (set-message-replied! original-message #t) + (let* ((new-message-body + (if (orig-actor-on-same-hive?) + `((original-message . ,original-message) + (error-key . ,error-key) + (error-args . ,error-args)) + `((original-message . ,original-message) + (error-key . ,error-key)))) + (new-message (make-message (hive-gen-message-id hive) + (message-from original-message) + (actor-id hive) '*error* + new-message-body + #:in-reply-to (message-id original-message)))) + (8sync-nowait (hive-process-message hive new-message)))) + (define-method (hive-process-message (hive ) message) "Handle one message, or forward it via an ambassador" (define (maybe-autoreply actor) @@ -481,8 +502,16 @@ more compact following syntax: actor)) (define (call-catching-coroutine thunk) + (define (call-catching-errors) + (with-throw-handler + #t thunk + (lambda (key . args) + (if (message-needs-reply message) + ;; If the message is waiting on a reply, let them know + ;; something went wrong. + (hive-reply-with-error hive message key args))))) (call-with-prompt (hive-prompt hive) - thunk + call-catching-errors (lambda (kont actor message) ;; Register the coroutine (hash-set! (hive-waiting-coroutines hive) @@ -506,27 +535,44 @@ more compact following syntax: result))))) (define (resume-waiting-coroutine) - (call-catching-coroutine - (lambda () - (match (hash-remove! (hive-waiting-coroutines hive) - (message-in-reply-to message)) - ((_ . (resume-actor-id . kont)) - (if (not (equal? (message-to message) - resume-actor-id)) - (throw 'resuming-to-wrong-actor - "Attempted to resume a coroutine to the wrong actor!" - #:expected-actor-id (message-to message) - #:got-actor-id resume-actor-id - #:message message)) - (let (;; @@: How should we resolve resuming coroutines to actors who are - ;; now gone? - (actor (resolve-actor-to)) - (result (kont message))) - (maybe-autoreply actor) - result)) - (#f (throw 'no-waiting-coroutine - "message in-reply-to tries to resume nonexistent coroutine" - message)))))) + (cond + ((eq? (message-action message) '*reply*) + (call-catching-coroutine + (lambda () + (match (hash-remove! (hive-waiting-coroutines hive) + (message-in-reply-to message)) + ((_ . (resume-actor-id . kont)) + (if (not (equal? (message-to message) + resume-actor-id)) + (throw 'resuming-to-wrong-actor + "Attempted to resume a coroutine to the wrong actor!" + #:expected-actor-id (message-to message) + #:got-actor-id resume-actor-id + #:message message)) + (let (;; @@: How should we resolve resuming coroutines to actors who are + ;; now gone? + (actor (resolve-actor-to)) + (result (kont message))) + (maybe-autoreply actor) + result)) + (#f (throw 'no-waiting-coroutine + "message in-reply-to tries to resume nonexistent coroutine" + message)))))) + ;; Yikes, we must have gotten an error or something back + (else + ;; @@: Not what we want in the long run? + ;; What we'd *prefer* to do is to resume this message + ;; and throw an error inside the message handler + ;; (say, from send-mesage-wait), but that causes a SIGABRT (??!!) + (hash-remove! (hive-waiting-coroutines hive) + (message-in-reply-to message)) + (let ((explaination + (if (eq? (message-action message) '*reply*) + "Won't resume coroutine; got an *error* as a reply" + "Won't resume coroutine because action is not *reply*"))) + (throw 'hive-unresumable-coroutine + explaination + #:message message))))) (define (process-remote-message) ;; Find the ambassador