Skip to content

Node logging fixes #487

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

Merged
merged 5 commits into from
Oct 31, 2019
Merged

Node logging fixes #487

merged 5 commits into from
Oct 31, 2019

Conversation

emschwartz
Copy link
Member

No description provided.

because they are likely to be offline and if we have many child accounts, these logs will quickly fill up our drive
@emschwartz emschwartz requested a review from bstrie as a code owner October 31, 2019 16:17
Copy link
Collaborator

@dora-gt dora-gt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just left comments.

error!(target: "interledger-node", "No route found for outgoing account ");
// Don't log anything for failed route updates sent to child accounts
// because there's a good chance they'll be offline
if request.prepare.destination().scheme() != "peer"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is required right now but this could be encapsulated and more understandable like

request.prepare.destination().is_scheme_peer()
// or
request.prepare.destination().is_scheme(Scheme::Peer)

@emschwartz emschwartz merged commit 65fe7c8 into master Oct 31, 2019
@emschwartz emschwartz deleted the es-fix-node branch October 31, 2019 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants