Branch: refs/heads/master
Home:
https://github.com/Checkmk/checkmk
Commit: fadc51d346ded181259298e09a0f1dd9cf6841a6
https://github.com/Checkmk/checkmk/commit/fadc51d346ded181259298e09a0f1dd9c…
Author: Sven Panne <sven.panne(a)checkmk.com>
Date: 2024-06-14 (Fri, 14 Jun 2024)
Changed paths:
M packages/livestatus/include/livestatus/LogCache.h
M packages/livestatus/src/LogCache.cc
Log Message:
-----------
Refactoring: Move pathsSince to its single use site
In the end, LogCache should have a nice & simple API with something like
"give me all log entries for this given range", without any abstraction
violations like seeing individual log files, etc.
Currently we have to go into the opposite direction: Move everything beyond
a minimal, abstraction-breaking API to its use sites, make the use sites
more similar, and then do the right abstraction.
Change-Id: Ic6afd3a731c4732e4c26c3780baad0c51d8f07fc
Commit: af6e46242bb1ff4c210489fca9921fabae84c3c4
https://github.com/Checkmk/checkmk/commit/af6e46242bb1ff4c210489fca9921faba…
Author: Sven Panne <sven.panne(a)checkmk.com>
Date: 2024-06-14 (Fri, 14 Jun 2024)
Changed paths:
M packages/livestatus/include/livestatus/LogCache.h
M packages/livestatus/src/LogCache.cc
M packages/livestatus/src/TableLog.cc
Log Message:
-----------
Refactoring: Move LogCache::for_each() to its single use site
Same reason for this change as the previous one for LogCache::pathsSince():
Minimize LogCache API first => unify usages => rework API
Change-Id: I69b7c55d8db509828e3d163367f1de78e8708242
Compare:
https://github.com/Checkmk/checkmk/compare/c26f5941b2b8...af6e46242bb1
To unsubscribe from these emails, change your notification settings at
https://github.com/Checkmk/checkmk/settings/notifications