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.

Sign up for GitHub

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

Jump to bottom

Better error chaining #96

Open
soygul opened this issue May 11, 2016 · 0 comments
Open

Better error chaining #96

soygul opened this issue May 11, 2016 · 0 comments

Comments

@soygul
Copy link
Member

soygul commented May 11, 2016

We chain error messages coming from Neptulon to Titan client and going back through ctx.Next() so log prefixes for errors gets mixed. Especially titan/client/route_out.go suffers from that. We need a better approach than just prefixing error messages (time for structured logging?).

Ref: https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=golang%20error%20chaining
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@soygul