Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

handle unmatched signals #136

Open
zippy opened this issue Apr 12, 2016 · 0 comments
Open

handle unmatched signals #136

zippy opened this issue Apr 12, 2016 · 0 comments
Assignees
Milestone

Comments

@zippy
Copy link
Owner

zippy commented Apr 12, 2016

currently when a signal is delivered, there is no handling for that signal if it doesn't match any expectation. This is especially important if the signal has a conversation id attached to it, because it will have created a conversation context (_r_deliver) which probably should be cleaned up if the signal doesn't match any expectations.
This is probably also related to general logging, and where we move signals on the flux that have been fully integrated...

@zippy zippy self-assigned this Apr 12, 2016
@zippy zippy added this to the Proto Launch milestone Apr 12, 2016
@zippy zippy changed the title handle failed signals handle unmatched signals Apr 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant