Attention is currently required from: Hoernchen, laforge.
1 comment:
Commit Message:
Patch Set #1, Line 11: some fallout expected
If we revert the revert, we end up with the same problem: old code (mostly tests, but who knows) using improper API to manipulate the logging configuration may suddenly stop logging because the cache if not properly maintained. I don't have a strong opinion here, but to me it looks like a substantial side effect, which can be avoided. A potential solution would be not enabling the cache by default and requiring the API user to explicitly enable it, by calling `osmo_log_cache_enable()` for instance.
To view, visit change 35525. To unsubscribe, or for help writing mail filters, visit settings.