~maas-committers/maas/+git/temporal:cloud/v1.24.0-m3

Last commit made on 2024-05-07
Get this branch:
git clone -b cloud/v1.24.0-m3 https://git.launchpad.net/~maas-committers/maas/+git/temporal

Branch merges

Branch information

Name:
cloud/v1.24.0-m3
Repository:
lp:~maas-committers/maas/+git/temporal

Recent commits

c1a7dcd... by Temporal Data <email address hidden>

Bump Server version to 1.24.0-m3.5

10cf4f1... by David Reiss <email address hidden>

Handle incompatible proto change in frontend (#5876)

## What changed?
Handle proto compatibility mistake by checking unknown fields.

## Why?
Compatibility during deployments.

## How did you test it?
manually

8ceec26... by Temporal Data <email address hidden>

Bump Server version to 1.24.0-m3.4

8166abb... by Shahab Tajik <email address hidden>

Add missing null check when unloading partition manager (#5817)

## What changed?
<!-- Describe what has changed in this PR -->
Fix panic when the partition being unloaded is not found in the map.

## Why?
<!-- Tell your future self why have you made these changes -->

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->

5709cbf... by Temporal Data <email address hidden>

Bump Server version to 1.24.0-m3.3

6bc5f75... by Norbert Hu <email address hidden>

Enable FE>history for reading history (#5798)

## What changed?
This enables frontend+matching reading history through history service

## Why?
This is the prereq for https://github.com/temporalio/temporal/pull/5797

f6ab055... by David Reiss <email address hidden>

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

e93982e... by Norbert Hu <email address hidden>

Revert "Enable FE proxying history reads to history service as default (#5736)" (#5797)

## What changed?
This reverts commit 3f1bdfba23cf15a6e711ada89308fb39e60ae635.

## Why?
This cleanup of deprecated code must wait until v1.25+

4a5f144... by Temporal Data <email address hidden>

Bump Server version to 1.24.0-m3.2

f261a4e... by Temporal Data <email address hidden>

Bump Server version to v1.24.0-m3.1