-
Notifications
You must be signed in to change notification settings - Fork 61
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
Req element twitce with hapi. #91
Comments
|
Probably it comes from Pino https://getpino.io/#/docs/child-loggers?id=duplicate-keys-caveat |
Hi It was still bothering me.
quick fix for this in my opinion is to change options:
|
We are seeing the same error as well. @indreek, have you been able to identify the root cause? |
Well, looks like the link right above says it all. Thanks for sharing this :) |
I'm using version
|
Hello it seems to be here and |
Setting Not sure what the right solution is to get both 🤔
|
I'm actually seeing the same thing. |
I think I've found a way to better handle this. |
…rt log (#157) There is no way to know in the response log event handling if the request was already added through the child bindings in `onRequest`. And there was no way as a user to fix this behaviour properly. So now `req` will be added once but you need to make sure that you pass it in `childBindings` for the response. Request start event will have it regardless but also only once. This is a breaking change as some people will have removed the `req` from the `childBindings` to get around this issue. Fixes #91
Any ideas why im getting req twice in logged json?
The text was updated successfully, but these errors were encountered: