~maas-committers/maas/+git/temporal:haifengh/v1.22.2-rc3-forward

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

ebf8f50... by Haifeng He <email address hidden> on 2023-11-30

Append xdc-redirection-api header to redirect request

37da275... by Rodrigo Zhou <email address hidden> on 2023-11-03

Allow list of keywords in dual visibility setting (#5065)

<!-- Describe what has changed in this PR -->
**What changed?**
Allow list of keywords in dual visibility setting

<!-- Tell your future self why have you made these changes -->
**Why?**
Let dual visibility with Elasticsearch work with list of keywords for
backwards compatibility.

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

<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
**Potential risks**
No. Any setting involving standard visibility will work as usual: custom
search attributes are just ignored and not persisted.

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

26114d7... by Roey Berman <email address hidden> on 2023-10-31

Hopefully avoid panic in DescribeWorkflowExecution (#5057)

**What changed?**

Clone suspected mutating fields after a returning from
DescribeWorkflowExecution.

**Why?**

Noticed panics in serialization of the
`DescribeWorkflowExecutionResponse` object.

**How did you test it?**

No tests added, assuming that normal test coverage is enough.
Haven't reproduced the issue, this is based on a hunch.

**Potential risks**

None that I can foresee.

**Is hotfix candidate?**

Yes.

ddf9799... by Rodrigo Zhou <email address hidden> on 2023-10-31

Bump server version to 1.22.2 (#5056)

<!-- Describe what has changed in this PR -->
**What changed?**
Bump server version to 1.22.2

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

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

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

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

ef3b92b... by David Reiss <email address hidden> on 2023-10-31

Fix schedule workflow unit test (#5052)

**What changed?**
Fix unit tests on release branch

**Why?**
The tests assumed that the change to not track ALLOW_ALL workflows was
already active, but it's not on the release branch. So we just need
mocks for WatchWorkflow.

**How did you test it?**
is tests

2320fc1... by David Reiss <email address hidden> on 2023-10-30

Add force-continue-as-new signal to schedule workflow (#5034)

**What changed?**
Add `force-continue-as-new` signal to schedule workflow, to force it to
continue-as-new immediately.

**Why?**
This could be used to force all running schedules onto the newest
version of the workflow code, to allow retiring older code paths.

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

b8163ce... by David Reiss <email address hidden> on 2023-10-24

Use ContinueAsNewSuggested in scheduler workflow (#4990)

**What changed?**
Scheduler workflow uses server-sent suggestion for when to
continue-as-new instead of fixed iteration count.

Note this is not enabled in this PR yet.

**Why?**
Automatically handle history size/event count too large conditions (or
any future conditions added by the server), which we might get if we do
more work than expected per iteration.

**How did you test it?**
new unit tests, also replaced for loop with previous version to verify
actual iteration count didn't change

**Potential risks**
The default history size suggestion is at 4MB, which we could hit after
just a few large payload responses, and then we'd do continue-as-new
more often than we might like.

88f8f11... by Quinn on 2023-10-17

Update Go SDK to v1.25.1 (#4955)

Update Go SDK to v1.25.1

cba2ce7... by David Reiss <email address hidden> on 2023-10-13

Improve scheduler workflow unit test (#4962)

**What changed?**
The end of each test is signaled by time instead of iteration count,
which was really confusing.

**Why?**
Easier to write and maintain tests.
They now stop at exactly the right time and avoid spurious calls that
would trigger panics.

**How did you test it?**
is tests

53a4979... by Shahab Tajik <email address hidden> on 2023-09-06

Expose buffer size and # dropped actions in ScheduleInfo (#4839)

<!-- Describe what has changed in this PR -->
**What changed?**
Expose buffer size and number of dropped actions due to buffer limit in
ScheduleInfo
Related API change: https://github.com/temporalio/api/pull/311

<!-- Tell your future self why have you made these changes -->
**Why?**
Give more visibility into schedule state to the clients.

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

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

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