lp:~maas-committers/maas/+git/temporal

Author: Hai Zhao
Author Date: 2024-04-30 07:35:36 UTC

test

Author: Carly de Frondeville
Author Date: 2024-04-30 06:52:36 UTC

use dynamic config for open and closed wf ttl

Author: ShahabT
Author Date: 2024-04-29 23:57:27 UTC

Improve DLQ Logs

Author: Shivs11
Author Date: 2024-04-29 18:29:06 UTC

removed build error

Author: Stephan Behnke
Author Date: 2024-04-29 15:41:31 UTC

UpdateWorkflow action metric on accept/reject (#5782)

## What changed?
<!-- Describe what has changed in this PR -->

The `action` metric gives OSS users an estimate for the expected cost
when moving to Cloud.

The metric is now tracking Update Workflow actions when receiving an
accepted/rejected protocol message from the Worker - instead of the RPC
request from the client.

_Additional context: When a Worker accepts or rejects an Update request,
it sends back an Acceptance, Rejection or Outcome message._

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

Reflects upcoming Cloud bill change.

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

Added test cases.

## 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) -->

Author: Dan Davison
Author Date: 2024-04-28 20:08:40 UTC

Example update test

Author: Dan Davison
Author Date: 2024-04-28 18:10:39 UTC

reapply updates: test should fail

Author: Dan Davison
Author Date: 2024-04-26 18:26:01 UTC

Honor reset reapply exclusions in batch reset API

Author: David Reiss
Author Date: 2024-04-25 23:25:07 UTC

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

Author: Kevin Kyyro
Author Date: 2024-04-26 19:53:13 UTC

allow idempotency overrides

Author: Dan Davison
Author Date: 2024-04-26 18:29:07 UTC

Extend instructions in CONTRIBUTING.md

Author: Temporal Data
Author Date: 2024-04-26 00:48:37 UTC

Bump Server version to 1.24.0-m3.3

Author: Dan Davison
Author Date: 2024-04-25 16:08:58 UTC

Clean up buffered signal test

Author: Dan Davison
Author Date: 2024-04-25 17:42:15 UTC

Don't deduplicate when resetting

Author: Carly de Frondeville
Author Date: 2024-04-25 07:53:04 UTC

merge with main

Author: Shivam
Author Date: 2024-04-23 18:11:26 UTC

Added GetBacklogInfo to allow frontend to view the Backlog counts. (#5767)

## What changed?
- Added `GetBacklogInfo` to allow backlog count to be present for each
partition when `DescribeTaskQueue` is called.
- Added logic to aggregate backlog counts from different partitions of
the same task queue.
- Added functional test for `DescribeTaskQueue` to verify if backlog
values are being returned.

- **Note**: The base feature PR for `approximateBacklogCounter`, prior
to this PR, was
[shivam/backlog-count](https://github.com/temporalio/temporal/tree/shivam/backlog-count).
However, after the most recent push of `versioning-2` to `main`, a lot
of conflicts exist between itself and `main`. Moreover, the current
branch in consideration is branched of the latest changes in main. Thus,
in the interest of time, conflicts were resolved by creating a new base
feature branch (now called `shivam/backlog-count-updated`) which is
branched off the latest main and consists of all the changes that were
present in the previous feature branch (shivam/backlog-count).

- **NOTE**: The functional tests for `sql` are expected to fail since
this feature will not currently work for `sql` databases as the backlog
counter is not persisted when tasks are created in sql. Work for that
will follow.

## Why?
Previous PR's went over the addition of the `approximateBacklogCounter`
as an in-memory variable. While unit and integration tests are present
to check its functionality, functional tests are required to check if it
is present accurately in request/response structures.

## How did you test it?
Functional tests were added.

Author: ShahabT
Author Date: 2024-04-23 02:48:13 UTC

fix test timeout

Author: ShahabT
Author Date: 2024-04-22 18:07:21 UTC

regenerate proto

Author: David Reiss
Author Date: 2024-04-19 17:01:35 UTC

Bump server version to 1.24.0-m2.6

Author: Carly de Frondeville
Author Date: 2024-04-18 23:18:09 UTC

Merge branch 'main' into cdf/minor-test-nit

Author: Norbert Hu
Author Date: 2024-04-18 22:38:39 UTC

Merge branch 'main' into norbert/tests-populate-history

Author: Carly de Frondeville
Author Date: 2024-04-12 18:03:27 UTC

Define versioning rule errors and improve unit test coverage (#5707)

## What changed?
- Define named version rule errors
- Add unit tests for errors that were previously untested

## Why?
So that the error messages can be standardized when they are used
repeatedly, and so that it is easier to tell whether all errors are
covered by the unit tests

## How did you test it?
Unit tests

Author: ShahabT
Author Date: 2024-04-11 23:59:24 UTC

fix lint

Author: Shivam
Author Date: 2024-04-11 22:34:46 UTC

Adding support for approximateBacklogCounter (#5593)

## What changed?
This PR intends on adding an in-memory variable, called
`approximateBacklogCounter`, which shall be used to approximate the size
of the backlog at a given moment.

The `approximateBacklogCounter` follows a tasks-to-be-read semantics, in
the sense that if a task exists in the db it is counted as part of the
backlog.

As of now, it does not take care about fanning out this variable to
child partitions.

**NOTE**: This PR shall ensure that the `approximateBacklogCounter` will
be an overestimate of the backlog **only** in the case of Cassandra.
This is because creation of tasks in Cassandra results in updating the
`taskQueueInfo` which in turn updates the backlog counter. More work has
to be done in the case of `SQL` and shall be addressed in a later PR.

## How did you test it?
Unit testing with more to come.
Functional testing in the near future.

## Is hotfix candidate?
No.

---------

Co-authored-by: ShahabT <shahab.tajik@temporal.io>

Author: Dan Davison
Author Date: 2024-04-11 13:49:07 UTC

WIP: handle conflicting update IDs during conflict resolution

Author: Tim Deeb-Swihart
Author Date: 2024-03-13 19:22:37 UTC

Initial helpers to investigate scylla

Author: Kevin Kyyro
Author Date: 2024-04-09 03:41:17 UTC

support configuring gocql timeout and writetimeout

Author: Prathyush PV
Author Date: 2024-04-05 15:47:45 UTC

Fixing admin handler test

Author: xwduan
Author Date: 2024-04-04 22:13:59 UTC

Fix DLQ serializer usage

Author: Carly de Frondeville
Author Date: 2024-04-03 21:28:51 UTC

call e.getBuildIdTaskReachability stub

Author: Tim Deeb-Swihart
Author Date: 2024-04-03 18:14:54 UTC

Fix summary cover profile target

You can't use @ like that within a makefile foreach

Author: rodrigozhou
Author Date: 2024-03-29 17:20:12 UTC

Util function to get SearchAttributeKey inferred from the payload metadata

Author: Tim Deeb-Swihart
Author Date: 2024-03-28 19:33:38 UTC

Update server version

Author: Tim Deeb-Swihart
Author Date: 2024-03-28 19:33:09 UTC

Update server version

Author: Temporal Data
Author Date: 2024-03-28 19:02:06 UTC

Bump Server version to 1.22.7

Author: Dan Davison
Author Date: 2024-03-26 14:13:38 UTC

Functional test of update reapply during conflict resolution

Author: Yichao Yang
Author Date: 2024-03-25 23:34:44 UTC

panic

Author: Chetan Gowda
Author Date: 2024-03-22 18:00:30 UTC

Tests - Fix how matching service client is accessed in functional tests

Author: Rodrigo Zhou
Author Date: 2024-03-20 23:17:53 UTC

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

## What changed?
<!-- Describe what has changed in this PR -->
Dynamic config to suppress error when setting system search attributes

## Why?
<!-- Tell your future self why have you made these changes -->
Create a way to prevent errors when new system search attributes are
added, but there is already a custom search attribute registered with
the same name.

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

## 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) -->

Author: Dan Davison
Author Date: 2024-03-21 02:37:54 UTC

WIP

Author: Prathyush PV
Author Date: 2024-03-20 19:02:32 UTC

Adding debug code

Author: Prathyush PV
Author Date: 2024-03-20 19:02:32 UTC

Adding debug code

Author: Chetan Gowda
Author Date: 2024-03-15 07:04:18 UTC

Fix sequence diagram rendering

Author: Yichao Yang
Author Date: 2024-03-12 17:23:24 UTC

rename to outbound

Author: Haifeng EC2
Author Date: 2024-03-12 13:51:34 UTC

set self tls

Author: Dan Davison
Author Date: 2024-01-22 23:32:06 UTC

Introduce ResetReapplyExcludeTypes

Author: Norbert Hu
Author Date: 2024-03-08 01:08:44 UTC

Prototyping passing shard id to branch token creation

Author: Tim Deeb-Swihart
Author Date: 2024-03-05 19:23:42 UTC

Remove debugging code

Author: Yichao Yang
Author Date: 2023-10-09 22:01:17 UTC

ASM Engine and top level activity

Author: Prathyush PV
Author Date: 2024-02-17 01:01:49 UTC

Refactor

Author: Carly de Frondeville
Author Date: 2023-12-19 23:11:54 UTC

populate CancelRequested in more places

Author: Carly de Frondeville
Author Date: 2023-12-19 05:03:10 UTC

first pass at new tdbg cmd

Author: Stephan Behnke
Author Date: 2023-12-07 23:00:45 UTC

wip

Author: Prathyush PV
Author Date: 2023-12-05 17:12:01 UTC

Fixing test

Author: Haifeng He
Author Date: 2023-11-30 21:43:28 UTC

Append xdc-redirection-api header to redirect request

Author: Yichao Yang
Author Date: 2023-11-22 23:11:11 UTC

Merge branch 'main' into remove-shard-lock-v2

Author: Norbert Hu
Author Date: 2023-11-22 21:54:49 UTC

Include WorkflowID & RunID when initializing branch tokens (#5152)

<!-- Describe what has changed in this PR -->
**What changed?**

<!-- 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?**

Author: Prathyush PV
Author Date: 2023-11-18 00:25:16 UTC

Minor refactor

Author: Prathyush PV
Author Date: 2023-11-20 22:01:13 UTC

Fixing test

Author: Dan Davison
Author Date: 2023-11-13 22:11:21 UTC

Update proto/api submodule

Author: Stephan Behnke
Author Date: 2023-10-27 19:53:16 UTC

Merge branch 'main' into history-service-interceptor

Author: Michael
Author Date: 2023-10-18 21:50:01 UTC

Get rid of persistence/client.Bean

Author: Yu Xia
Author Date: 2023-01-26 23:49:21 UTC

Change deadline too short to failedPrecondition error (#3856)

Author: Alex Shtin
Author Date: 2022-11-15 23:13:23 UTC

Update version to 1.18.5

Author: Alex Shtin
Author Date: 2022-09-13 17:21:14 UTC

Prepare 1.17.6 patch

Author: Matt McShane
Author Date: 2022-08-17 23:12:40 UTC

Use default TracerProvider if no config is given

Even less resource utilization in the common case plus
Span.IsRecording() will work.

Author: Alex Shtin
Author Date: 2022-07-08 19:47:22 UTC

Prepare 1.16.3 patch

Author: Liang Mei
Author Date: 2022-03-08 23:46:46 UTC

Add dynamic config for per instance visibility API rate limit and burst (#2585)

Author: Yu Xia
Author Date: 2022-03-04 22:28:50 UTC

Prepare v1.14.6 patch (#2573)

Author: Alex Shtin
Author Date: 2022-02-14 21:07:24 UTC

Update go version of goreleaser to to 1.17.6 (#2506)

Author: Alex Shtin
Author Date: 2021-10-29 17:31:33 UTC

Fix merge error

Author: Yimin Chen
Author Date: 2021-08-18 23:05:41 UTC

Release 1.11.4

Author: wenquan xing
Author Date: 2021-06-24 22:22:06 UTC

Release v1.10.5

Author: wenquan xing
Author Date: 2021-06-23 19:55:42 UTC

Release v1.9.3

Author: Alex Shtin
Author Date: 2021-04-15 16:21:57 UTC

Release v1.8.2

Author: Alex Shtin
Author Date: 2021-04-15 15:47:27 UTC

Release v1.7.3

Author: Alex Shtin
Author Date: 2021-04-15 15:11:14 UTC

Release v1.6.7

Author: wenquan xing
Author Date: 2021-04-07 21:14:32 UTC

Release v1.5.8

Author: wenquan xing
Author Date: 2021-02-18 22:57:51 UTC

Try fix buildkite docker

Author: wenquan xing
Author Date: 2021-02-18 22:57:51 UTC

Try fix buildkite docker

Author: wenquan xing
Author Date: 2021-02-18 22:57:51 UTC

Try fix buildkite docker

Author: wenquan xing
Author Date: 2021-02-18 22:57:51 UTC

Try fix buildkite docker

Author: wenquan xing
Author Date: 2021-02-18 21:48:57 UTC

Try fix buildkite docker