David Reissandrodrigozhou 845afbf8e0 Build id scavenger shouldn't look at recent build ids (#4846) ...

**What changed?**
Build id scavenger shouldn't look at build ids that were added since
retention time.

**Why?**
In the scavenger, we can assume that build ids are used soon after being
registered. With that assumption, we can avoid the build id scavenger
doing a lot of visibility queries that will likely return workflows.

**How did you test it?**
unit test

**Potential risks**
If a build id is created and not used, or if it was used but workflows
manually deleted, it previously could have been scavenged fairly soon,
but now we'll wait at least the retention time.

2023-10-06 10:34:53 -05:00

..

hybrid_logical_clock

Build id scavenger shouldn't look at recent build ids (#4846)

2023-10-06 10:34:53 -05:00

event_time_source_test.go

Add clock.TimeSource.AfterFunc (#4611)

2023-07-22 01:24:46 +00:00

event_time_source.go

Add clock.TimeSource.AfterFunc (#4611)

2023-07-22 01:24:46 +00:00

time_source_test.go

Add clock.TimeSource.AfterFunc (#4611)

2023-07-22 01:24:46 +00:00

time_source.go

Add clock.TimeSource.AfterFunc (#4611)

2023-07-22 01:24:46 +00:00