-
Notifications
You must be signed in to change notification settings - Fork 23
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
work around mpconfig dropping support for empty array #198
work around mpconfig dropping support for empty array #198
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay, was on PTO.
This is fine with me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but should we forbid ThreadContextProvider
with the name None
to be extra sure we'll never run into issues? I guess MP config will always filter them out, but still…
It seems extremely unlikely that anyone would name their ThreadContextProvider "None", but it's easy enough to explicitly forbid that so we might as well. I'll add it in a separate pull, #199 , under the same issue given that there are already 3 approvals on this one. |
contains most of the fix for #160