This repository was archived by the owner on Sep 3, 2024. It is now read-only.
Safe Handler Execution #17
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Evaluating 'safe' or 'apiSafe' in a 'filters' block allows the user to mark certain messages for safe handling. When marked thus, any matching handlers for these messages are evaluated without fully dequeueing the message from the priority queue, such that if we receive and handle (i.e. swallow) an exit signal, the message will be available for re-processing. Only once a message has been safely processed will it be fully dequeued from the internal mailbox/queue.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Evaluating
safeorapiSafein a 'filters' block allows the user to markcertain messages for safe handling. When marked thus, any matching handlers
for these messages are evaluated without fully de-queueing the message from
the priority queue, such that if we receive and handle (i.e. swallow) an
exit signal, the message will be available for re-processing. Only once a
message has been safely processed will it be fully dequeued from the internal
mailbox/queue.