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

Tracing is broken #265

Closed
hyperthunk opened this issue Dec 2, 2015 · 4 comments
Closed

Tracing is broken #265

hyperthunk opened this issue Dec 2, 2015 · 4 comments
Assignees
Milestone

Comments

@hyperthunk
Copy link
Member

Tracing for named send, unreliable send, and monitoring appears to be either missing or has been stripped out accidentally in previous commits. I'll look at putting this back in.

@hyperthunk hyperthunk self-assigned this Dec 2, 2015
@hyperthunk hyperthunk added this to the Horizon milestone Dec 2, 2015
@facundominguez
Copy link
Contributor

Not sure if it is meant to be fixed here.

Tracing received messages currently produces a loop, which I hope to fix here.
It is not very elegant but it should work while something better is implemented.

I will make a PR after I write some tests.

@hyperthunk
Copy link
Member Author

That code makes sense, as does the bug. Silly mistake on my part.. Thanks for the spot, and fix!

@hyperthunk
Copy link
Member Author

I'm just starting to cook up a PR for this..

@hyperthunk
Copy link
Member Author

I am working on proving the things that we're saying in #241

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants