David ReissandYichao Yang 60dd7fa065 Fix schedule workflow to CAN after signals (#5799) ...

## What changed and why?
If a schedule was paused and received a large number of signals
(trigger, backfill, etc.), it wouldn't be able to continue-as-new and
history size could grow past the suggested limit.

For various reasons the main loop receives and processes signals across
iterations, with checking for CAN in between, so a wakeup due to a
signal (instead of a timer) would prevent CAN. Refactoring is hard due
to the determinism requirement, so the simplest fix is to do a second
check.

## How did you test it?
New unit test

2024-04-26 14:03:36 -07:00

..

frontend

Dynamic config to suppress error when setting system search attributes (#5561)

2024-03-21 10:15:28 -05:00

history

Handle data corruption in history resend (#5398)

2024-04-26 13:53:54 -07:00

matching

Ensure PollActivityTaskQueueResponse.ScheduleToCloseTimeout is not nil (#5444)

2024-02-21 13:17:35 -08:00

worker

Fix schedule workflow to CAN after signals (#5799)

2024-04-26 14:03:36 -07:00

fx.go

Persistence global rate limit (#4803)

2023-09-11 11:15:23 -07:00