fix(connections): do not log AgentContext object #1085
Merged
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.
In last Aries Framework JS call @niall-shaw reported performance issues when accepting multi-use invitations.
I've experienced the same issue after migrating to 0.3.0-alpha.x and it turns out that it was happening because some methods in
DidExchangeProtocol
were logging the whole messageContext object, which now includes agentContext and blocks the console for several seconds. This can be avoided by either logging in INFO mode or customizing the logger being in use to only output a certain depth level of objects.This PR makes a quick-fix of this issue by logging only messageContext.message, to be consistent with other methods from
ConnectionService
. Not sure if it's really useful though, but that's another subject to discuss 😄 .