diff options
| author | Stefan Boberg <[email protected]> | 2026-03-14 23:00:59 +0100 |
|---|---|---|
| committer | Stefan Boberg <[email protected]> | 2026-03-14 23:00:59 +0100 |
| commit | 88c7eb801006525db54f3c99f1195908e31f0d74 (patch) | |
| tree | 9fa5406dfa4200b0615cb3267691448085aed628 /src | |
| parent | Fix GC never triggering when gc_state has mismatched clock resolution (diff) | |
| download | zen-sb/core-http-functions.tar.xz zen-sb/core-http-functions.zip | |
Reset m_LastGcExpireTime when gc_state timestamps are bogussb/core-http-functions
When the stored gc_state has mismatched clock resolution,
m_LastGcExpireTime suffers the same issue as m_LastGcTime. Reset it
back to TimePoint::min() so the disk usage log replay does not
incorrectly filter out entries.
Diffstat (limited to 'src')
| -rw-r--r-- | src/zenstore/gc.cpp | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/zenstore/gc.cpp b/src/zenstore/gc.cpp index f4bb80b69..f3edf804d 100644 --- a/src/zenstore/gc.cpp +++ b/src/zenstore/gc.cpp @@ -1782,6 +1782,7 @@ GcScheduler::Initialize(const GcSchedulerConfig& Config) // between the build that wrote gc_state and this build) or too far in the past. m_LastGcTime = GcClock::Now(); m_LastLightweightGcTime = m_LastGcTime; + m_LastGcExpireTime = GcClock::TimePoint::min(); } m_AttachmentPassIndex = SchedulerState["AttachmentPassIndex"sv].AsUInt8(); } |