Setting up some lightweight automation for publishing docker images #1

* Fill domainID for backwards compatibility * Added unit test

* Log error fields as tags * Update common/log/loggerimpl/logger.go Co-authored-by: Steven L <stevenl@uber.com> * Fix syntax error * Use zap ObjectMarshaler for nested fields Co-authored-by: Steven L <stevenl@uber.com>

…er#4806)

* Add logs for domain failover (uber#2359) * Add operation name tag for domain update (uber#2359) * Add error logs for domain update (uber#2359) * Update logs to reuse the logger (uber#2359)

) We have a user desiring this, and in general it seems like a good idea. Activities are generally assumed to be "high cost" to lose, or at least potentially. Longer term, we should probably consider making this a per-domain config, rather than something that is hardcoded for a whole cluster. Nothing about this seems like it would be cluster-bound.

The suspicion is that this is not actually a transient and retriable error, so this should be handled differently

* Simplify history builder * Removed unused methods

)

* Removing target-domain-not-active special-case handling The suspicion is that this is not actually a transient and retriable error, so this should be handled differently * Fixing remaining non-retriable error * Fix test

…tion (uber#4792)

* Decouple domain cache entry from cluster metadata * Addressing comments * Fixing test

* Add new empty response metric for persistence operations (uber#2360) * Add empty response metric for more persistence operations (uber#2360) * Reuse the scopes and tags (uber#2360)

…r#4860)

* CDNC-1746: cadence-history does not emit continue-as-new metrics - Emit metric when completing via ContinueAsNew - Emit metric and logs when completing via unknown type, so that we'll know in the future if there are more types we should emit metrics for * PR requests * Revert "PR requests" This reverts commit 832bcfe. * PR requests try2

…onfig (uber#4858)

* Adds cross-cluster canary * updating readme

* Add support for changing the gocql connect timout * Fix comment typo

* Refactor dynamic config * Change dynamic client interface

…ber#4885) This allows an easy workflow for building/running a custom cadence server: docker-compose up, docker stop cadence, cadence-server start. Also add documentation of this workflow.

Delete 3 lines -> cut test suite time significantly! I feel productive. At this point, the biggest time cost seems to be coming from installing cqlsh, which is a bit longer than other portions of "build stuff so we can run stuff".

…ber#4881)

* Removed replication mocks * Ensure fakeTaskExecutor was called

uber#4891) Co-authored-by: David Porter <david.porter@uber.com>

) * upgrade go version in buildkite * go mod tidy * fix unit test * go mod version * fix SPACE in makefile * address comment to add suggested comment on SPACE

…r#4896) * Minor makefile cleanup, verbose CI, fmt with a recent Go version Due to some unnecessary complexity troubleshooting a buildkite failure recently, I'm declaring "no more @ use", period. Knowing the full command that has failed is extremely useful, and this is an easy way to achieve it. Also: - made some vars slightly more readable? - make the Makefile verbose in all buildkite jobs - `make fmt` with Go 1.18 because it apparently changes goimports' behavior. older Go versions do not undo this, so it should be stable.

Adding gowrap in uber#4879 pulled in an additional *30MB* of dependencies, which is pretty ridiculous. It's happening because, while gowrap uses a tools-tagged `tools.go`, it's in the same module as everything else, so its dependencies are pulled in too, because Go has no way to tell that it's not needed by callers (it needs to consider ALL tags). We're doing the same thing. Granted, we're an application and not a library, but it still seems kinda unnecessary. And it forces upgrades we may not want to force (yet). So this moves tools.go to a new package, sets up a new go.mod file just for it, and adds a bit of automation to prevent it from drifting too far from the main module. With this, `go mod tidy` in the top level does not consider tools-dependencies any more, so we actually *remove* some, and do not add tons more for gowrap/etc in the future. --- internal/tools is just because it needs to be in a separate package, and "tools" was taken. plus nobody should ever import it, so it should be a clear "dependency dead-end" for tools.

* introduce gowrap for decorator generation * go mod tidy -go=1.16 && go mod tidy -go=1.17

* Add JitterDelay option when creating workflows. * Update idls * getting jitter to work with cron * Update IDL Co-authored-by: David Porter <david.porter@uber.com>

* Add new es record for uninitialized workflow (uber#2386) * Add nil check for visibility manager when adding uninitialized wf execution record (uber#2386) * Update TestProcessRecordWorkflowStartedTask to include unit test for record wf execution uninitialized method * Fix the test add method of es processor (uber#2386) * Disable the feature by default (uber#2386) * Fix the unit test when feature is disabled * Fix the unit test when feature is disabled (uber#2386)

Capture DB Unavailable errors and log/bump metrics for it.

* fix lint error * add new CI step for lint * commit change after lint * add missing dependency of makefile rule * address comments: remove excessive artifact paths

* Fix flaky retry tests. - Use random seed in test suite to hit the flakiness easier. - Adjust 2 tests to use the correct remaining times (which I found by instrumenting the code to print out the actual remaining time for the expiration interval.)

…omain name (uber#4904) * Update EnableRecordWorkflowExecutionUninitialized flag to filter by domain name (uber#2386) * Update EnableRecordWorkflowExecutionUninitialized flag to filter by domain name (uber#2386)

…#4901)

… a new run (uber#4898) # Summary for busy people Workflow cancellation was kinda weird and confusing, and left some awful, unrecoverable, and un-*preventable* edge cases (particularly with child workflows). It also left users with no way to reliably stop work, aside from termination. Termination is inherently "unclean" and risky, so it should not be required to achieve something outside exceptional circumstances where recovery is not possible. This commit changes that: cancellation is now "sticky", and a canceled workflow does not ever trigger a new run after it completes, regardless of how it completes, so it can be used as a reliable "stop processing after cleanup" tool. The final state of a canceled workflow's run is now *always* a successful completion with a value, canceled, or timed out. (termination remains always "terminated") A canceled workflow can still start and abandon child workflows, so all current behavior with retries / continue as new / etc can be replicated with child workflows if desired. A fair bit of (not very complex) additional work here and in nearly all other repos is required to truly complete this, but it is *functional* and non-optional with this commit alone. In particular, adding a dynamic config to (temporarily!) restore old behavior should be fairly easy if it proves to be needed. # More details and motivation Part 1 of [many, tbd, in multiple repos] involved in changing workflow cancellation to reliably end workflows. Tests will be coming soon, for now I'm using a fairly simple set of workflows and checking the resulting histories exhaustively by hand. The primary motivation for these changes is to address some impossible-to-recover-from scenarios when canceling child workflows. After further exploration and discussion we've realized that, without these changes, there is *no reliable way* to stop a sequence of workflows without relying on termination, which we consistently treat as a fallback / impure-but-necessary ultimate hammer. Workflows should not *need* to rely on termination to achieve a desired behavior. With these changes, cancellation becomes capable of *guaranteeing* that workflows end within some finite time, which is a unique ability and makes it much more consistent and reliable. Turning this into a "complete" change will require quite a few tests, documentation changes, client-side changes (to allow recording more info, and likely changing test suites), and some smallish database and maybe RPC changes (to hold/return more data in cancellation errors). We are also not currently planning on making this configurable. It's seen as a correction of an under-specified and somewhat flawed chunk of behavior, more than "a change". Existing workflows will not experience replay errors, but it is still a substantial *semantic* change, though from what we have seen cancellation is relatively rarely used (partly due to its complex behavior). If issues are encountered / if users end up needing it, it should be fairly easy to add a per-domain/tasklist/workflow type configuration value, but it will be opt-*out*, not opt-*in*. # What was happening Previously, workflow behavior on cancellation was pretty frequently surprising to our users, arguably inconsistent, and not very well documented: | **PREVIOUS** | **simple** | **retry** | **cron** | **retry+cron** | |--------------:|--------------------------|-------------------------------------------|-----------------------------------------|---------------------------------------------------| | **success** | success | success | success continue cron cron | success continue cron cron retry | | **cancel** | canceled | canceled | canceled | canceled | | **retryable** | (n/a, fatal) | continue retry retry recorded error | (n/a, fatal) | continue retry cron retry recorded error | | **fatal** | failed recorded error | failed recorded error | continue cron cron recorded error | continue cron cron retry recorded error | | **continue** | continue immediately | continue immediately retry | continue immediately | continue immediately retry | | **timeout** | timeout | continue retry retry recorded error | continue cron cron recorded error | continue retry cron retry recorded error | A legend is: - success / etc shows the final state of the canceled run (success = completed with a value that can be retrieved) - "continue X" covers what source is used to compute the next run's starting delay (cron, retry, or no delay) - "cron" / "retry" shows whether or not cron/retry configuration is carried over to the new run - note that cron is lost by default with continue-as-new - and "recorded error" is whether or not the returned error is saved in its entirety (type + reason + details) This largely summarizes as "cancellation works when you end with the canceled-context error", say from `ctx.Err()`, otherwise it behaves like normal (or nearly) and many scenarios will start a new run. That's somewhat reasonable, but it's fairly "fragile" (it depends on what you return, and there are *many* ways for code to return some other error), and most importantly it means *there is no reliable way to stop a workflow* except to terminate it. That has severe consequences in at least two scenarios: 1. When termination is *unsafe* 2. When a parent workflow cancels a child by canceling its context For 1, for manual cancellations it's potentially reasonable to just terminate a run that begins after a successful cancel... but in principle if you're using cancellation it implies that termination is *not* desired, and potentially not safe to do. Canceling may result in a brand new run that immediately starts new behavior, leaving you with no safe window to terminate and not leave bad state lingering. So users wanting a safe way to stop a sequence of workflows have no reliable way to do so. For 2, it puts parent+child workflows in an extremely awkward, and essentially unrecoverable scenario. Cancellation is a *one time event*, and as far as the parent is concerned, if the child/its context is canceled, the child is canceled... ...but if the child then starts a new run for *any* reason (retry, cron, reset, etc), that new run is no longer canceled. The parent has no way to know this has happened, and has no way to *re*-cancel the new child, so it can easily lead to the collection of workflows getting into an impossible state that it never recovers from. Both cases are able to lead to unreliable behavior which can only use termination to stop, and for which no "safe" option exists. After reviewing some customer issues and desires and thinking about things, we've settled on "cancel should guarantee that things stop". Not necessarily in a timely manner, but that's fine. And if a workflow wants to run behavior longer or larger than its current run can achieve, it has a workaround: start a new (likely child) workflow to do the cleanup. # What happens now So that's what this PR does, in a minimal / to-be-polished way so we can start running it for our stuck users while we flesh out tests and change other behaviors. Currently that means our cancellation behavior is now: | **CURRENT** | **simple** | **retry** | **cron** | **retry+cron** | |--------------:|-------------------------------------------|-------------------------------------------|-------------------------------------------|-------------------------------------------| | **success** | success | success | success | success | | **cancel** | canceled | canceled | canceled | canceled | | **retryable** | (n/a, fatal) | canceled recorded error (details only) | (n/a, fatal) | canceled recorded error (details only) | | **fatal** | canceled recorded error (details only) | canceled recorded error (details only) | canceled recorded error (details only) | canceled recorded error (details only) | | **continue** | canceled (no details) | canceled (no details) | canceled (no details) | canceled (no details) | | **timeout** | timeout | timeout | timeout | timeout | And the new "details" entries cover whether or not an error's "details" (the custom encoded data, not reason or type) are saved. Unfortunately the current cancellation event (and clients' API) does not allow recording all data, or any in some cases, so the original reason/message and error type are lost and are replaced with a canceled error. Now, cancellation *always* ends workflows with the current run. Returning a value will return that value, including in cron scenarios, timeouts are still timeouts (and they imply a possibly un-clean termination), and _all_ errors or attempts to continue-as-new will instead result in a canceled state. # Future changes to make to finish this effort With further changes to the clients and RPC/storage models, canceled errors will store more details about what was returned. E.g. continue-as-new does not record what was *attempted* to be started, and other error types lose their "reason" (i.e. the message) and type but not details. Pretty clearly this is sub-par, and we should be capable of reporting the actual return in full so it can be retrieved if needed. This is also why returning a value now always ends in a completed state, so successful completions do not lose those values. Prior to merging into master / a release, we may end up making this configurable (likely with a default of opt-out), to address both the sub-par information recording and the semantically-breaking behavior change. Docs changes are also due, as well as some integration tests, client library changes (e.g. to make sure the test suite reflects the new behavior), etc. Another gap to plug is that resetting a workflow does not "forward" the canceled state to the new run. We should probably be treating cancellation like we do signals: cancel the new run if the current run is canceled. This will ensure that you can reset a child and retain the parent's cancellation, so it'll very likely become the default behavior, but we'll allow overriding it. Resets are manual actions, they can break the rules if desired. And they can just manually cancel later if they decide they do want it. And last and perhaps least: it's quite strange that continue-as-new does not retain cron config. At least from the Go client. I suspect it's just not adding to / pulling from the context correctly.

* Fix minor lint issue: [indent-error-flow] if block ends with a return statement, so drop this else and outdent its block * Fix lint warning: [var-naming] struct field WorkflowId should be WorkflowID * Fix lint warning: [receiver-naming] receiver name m should be consistent with previous receiver name n for noopClientImpl * Fix lint warning: [range-val-address] suspicious assignment of 't'. range-loop variables always have the same address For this one, I created a Go playground test to ensure the right values are being appended. Because we're appending the address of t.TransferTask (instead of just t), this is safe. * Make it an error to disable a revive warning without specifying a reason * Ignore '[defer] recover must be called inside a deferred function': callers are being called using defer and I don't see a better way to do it.

…cs required for Domain Cost Attribution (uber#4908) * Update RecordWorkflowExecutionStarted method to create a metrics by adding a domain tag * add domaing tag to the metrics file recordworkflowexecutionstarted method * Updated all functions in esVisibilityMetricClients.go with additon of domainId to create metrics * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added the change to map domainName to domainID in DeleteWorkflowExecution in esVisibilityMetricClients.go file * Added the change to map domainName to domainID in DeleteWorkflowExecution in esVisibilityMetricClients.go file * Added the change to map domainName to domainID in DeleteWorkflowExecution in esVisibilityMetricClients.go file * Added domain to the VisibilityDeleteWorkflowExecutionRequest to all the implementing and in definition * Added domain to the VisibilityDeleteWorkflowExecutionRequest to all the implementing and in definition * Added domain to the VisibilityDeleteWorkflowExecutionRequest to all the implementing and in definition * Removed Domain field from serialization file : empty data field * Removed Domain field from thrift_mapper_test.go : added unknown field,not used * Remove Domain tag from newTimerTaskFromInfo : extra field,not used * Added mock behaviour to match with real behaviour in time_task_executor_base_test.go * Ran linter and removed a comment

…ber#4911) * Minor text changes while reading this file * Ignore lint warning: [defer] recover must be called inside a deferred function * Fix lint warning: [var-naming] func parameter startedShardId should be startedShardID * Fix lint warnings: [context-as-argument] context.Context should be the first parameter of a function * Fix lint warning: [receiver-naming] receiver name mdb should be consistent with previous receiver name pdb for db * Fix lint warning: [indent-error-flow] if block ends with a return statement, so drop this else and outdent its block * Fix lint warning: [context-as-argument] context.Context should be the first parameter of a function * Fix lint warning: [unexported-return] exported func NewDNSPeerChooserFactory returns unexported type *rpc.dnsPeerChooserFactory, which can be annoying to use - Return interface instead of impl - Remove small piece of test that was testing impl. * Make lint (revive) error by default. - Use stylish formatter which looks cool (let me know if this is going to break something in CI) - Don't exclude canary because there doesn't seem to be a good reason to. - Don't sort at the end, because we shouldn't have a huge list and we need the error code. * Fix build error - move ctx to new position

We decided that our usage of helper functions when using defer/recover was too brittle, since one too many functions causes recover() not to do the right thing in Go. Switching to this idiom, where the defer caller also calls recover() ensures that we will get the right result from recover(), but also lets us continue to use the helper functions to deduplicate the code that runs after recover().

* Update to latest version of revive that includes Steven's change to find more defer/recover badness. mgechev/revive#719 * Ignore 158 new warnings about package-comments. * Add Steven's new immediate-recover linter. - Verified this would have caught the previous mistakes I made (woohoo!)

downgrade testify to fix monorepo

* Fix query workflow high latency after a long inactive time * Add new client integration test

CDNC-1781 restart cli command

* Update RecordWorkflowExecutionStarted method to create a metrics by adding a domain tag * added domain tag to the metrics file recordworkflowexecutionstarted method * Updated all functions in esVisibilityMetricClients.go with addition of domainId to create metrics * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added the change to map domainName to domainID in DeleteWorkflowExecution in esVisibilityMetricClients.go file * Added the change to map domainName to domainID in DeleteWorkflowExecution in esVisibilityMetricClients.go file * Added the change to map domainName to domainID in DeleteWorkflowExecution in esVisibilityMetricClients.go file * Added domain to the VisibilityDeleteWorkflowExecutionRequest to all the implementing and in definition * Added domain to the VisibilityDeleteWorkflowExecutionRequest to all the implementing and in definition * Added domain to the VisibilityDeleteWorkflowExecutionRequest to all the implementing and in definition * Removed Domain field from serialization file : empty data field * Removed Domain field from thrift_mapper_test.go : added unknown field: not used * Remove Domain tag from newTimerTaskFromInfo : extra field :not used * Added mock behavior to match with real behavior in time_task_executor_base_test.go * Ran linter and removed a comment * Changed ReadHistoryBranch,AppendHistoryNodes,call and the previous flows from persistenceMetricClients.go w/o mocks change * Removed else statement as there was an return statement in if * removed unnecessary comments * Removed extra spaces * removed space * Changes in persistenceMetricClients.go * Added Domain Name in Mock * Added DomainName to testing file changes * Changes after review : before mocks * After linting * linter change * Added mock for domainCache in historyExist_test * Added metrics.Tag type to call instead of generic string type * return 0 instead of -1 as per suggestion in context.go * Changed call, and added mocks correct implementation * Changed call, and added mocks correct implementation: With linter * Added mock to task_ac_manager_test.go * Added mock to task_ac_manager_test.go: with linter * Remove redundant mocks from adminHandler_test.go

…eadHistoryBranchByBatch (uber#4926) * ada * Update RecordWorkflowExecutionStarted method to create a metrics by adding a domain tag * add domaing tag to the metrics file recordworkflowexecutionstarted method * Updated all functions in esVisibilityMetricClients.go with additon of domainId to create metrics * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added the change to map domainName to domainID in DeleteWorkflowExecution in esVisibilityMetricClients.go file * Added the change to map domainName to domainID in DeleteWorkflowExecution in esVisibilityMetricClients.go file * Added the change to map domainName to domainID in DeleteWorkflowExecution in esVisibilityMetricClients.go file * Added domain to the VisibilityDeleteWorkflowExecutionRequest to all the implementing and in definition * Added domain to the VisibilityDeleteWorkflowExecutionRequest to all the implementing and in definition * Added domain to the VisibilityDeleteWorkflowExecutionRequest to all the implementing and in definition * Removed Domain field from serialization file : empty data field * Removed Domain field from thrift_mapper_test.go : added unknown field,not used * Remove Domain tag from newTimerTaskFromInfo : extra field,not used * Added mock behaviour to match with real behaviour in time_task_executor_base_test.go * Ran linter and removed a comment * Changed ReadHistoryBranch,AppendHistoryNodes,call and the previous flows from persistenceMetricClients.go w/o mocks change * Removed else statement as there was an return statement in if * removed unnecessary comments * Removed extra spaces * removed space * Changes in persistenceMetricClients.go * Added Domain Name in Mock * Added DomainName to testing file changes * Changes after review : before mocks * After linting * linter change * Added mock for domainCache in historyExist_test * Added metrics.Tag type to call instead of generic string type * return 0 instead of -1 as per suggestion in context.go * Changed call, and added mocks correct implementation * Changed call, and added mocks correct implementation: With linter * Added mock to task_ac_manager_test.go * Added mock to task_ac_manager_test.go: with linter * Remove redundant mocks from adminHandler_test.go * Changes from central master * Changed call method in ReadHistoryBranchByBatch and ReadRawHistoryBranch * Added changes to forkHistory mocks and backtracked methods * Added changes to forkHistory mocks and backtracked methods * Module files update automatic

…ith mocks (uber#4928) * ada * Update RecordWorkflowExecutionStarted method to create a metrics by adding a domain tag * add domaing tag to the metrics file recordworkflowexecutionstarted method * Updated all functions in esVisibilityMetricClients.go with additon of domainId to create metrics * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added DomainId changes in the functions of esVisibilityMetricClient.go file * Added the change to map domainName to domainID in DeleteWorkflowExecution in esVisibilityMetricClients.go file * Added the change to map domainName to domainID in DeleteWorkflowExecution in esVisibilityMetricClients.go file * Added the change to map domainName to domainID in DeleteWorkflowExecution in esVisibilityMetricClients.go file * Added domain to the VisibilityDeleteWorkflowExecutionRequest to all the implementing and in definition * Added domain to the VisibilityDeleteWorkflowExecutionRequest to all the implementing and in definition * Added domain to the VisibilityDeleteWorkflowExecutionRequest to all the implementing and in definition * Removed Domain field from serialization file : empty data field * Removed Domain field from thrift_mapper_test.go : added unknown field,not used * Remove Domain tag from newTimerTaskFromInfo : extra field,not used * Added mock behaviour to match with real behaviour in time_task_executor_base_test.go * Ran linter and removed a comment * Changed ReadHistoryBranch,AppendHistoryNodes,call and the previous flows from persistenceMetricClients.go w/o mocks change * Removed else statement as there was an return statement in if * removed unnecessary comments * Removed extra spaces * removed space * Changes in persistenceMetricClients.go * Added Domain Name in Mock * Added DomainName to testing file changes * Changes after review : before mocks * After linting * linter change * Added mock for domainCache in historyExist_test * Added metrics.Tag type to call instead of generic string type * return 0 instead of -1 as per suggestion in context.go * Changed call, and added mocks correct implementation * Changed call, and added mocks correct implementation: With linter * Added mock to task_ac_manager_test.go * Added mock to task_ac_manager_test.go: with linter * Remove redundant mocks from adminHandler_test.go * Changes from central master * Changed call method in ReadHistoryBranchByBatch and ReadRawHistoryBranch * Added changes to forkHistory mocks and backtracked methods * Added changes to forkHistory mocks and backtracked methods * Module files update automatic * Changed DeleteHistoryBranch by adding Domain Tag with mocks * Added anyTimes to mock of timer_task_executor_base_test.go * Added changes to GetHistoryTree * Added changes to GetHistoryTree

The current output is not particularly useful for some types: ``` ❯ cadence admin db decode_thrift -i '590f000a0c000000010a000a00000000000000560a00141704bf217393afac08001e000000030a002300000000000000010a0024000000000dd674990c004608000a00000000000000' =======Decode into type shared.History ======== {Events:[len=1]} ``` Now it's much better: ``` ❯ cadence admin db decode_thrift -i '590f000a0c000000010a000a00000000000000560a00141708a948a26a263f08001e000000030a002300000000000000010a0024000000000d985dab0c004608000a00000000000000' ======= Decode into type shared.History ======== (*shared.History)(0xc0003fc588)(History{Events: [HistoryEvent{EventId: 86, Timestamp: 1659762592113632831, EventType: WorkflowExecutionTimedOut, Version: 1, TaskId: 228089259, WorkflowExecutionTimedOutEventAttributes: WorkflowExecutionTimedOutEventAttributes{TimeoutType: START_TO_CLOSE}}]}) ======= As JSON ======== {"events":[{"eventId":86,"timestamp":1659762592113632831,"eventType":"WorkflowExecutionTimedOut","version":1,"taskId":228089259,"workflowExecutionTimedOutEventAttributes":{"timeoutType":"START_TO_CLOSE"}}]} ```

… CreateWorkflowRequest + added DomainCacheNoOp file (uber#4930) Why this change? - To add domain tag to persistenceMetricClients.go methods: ReadHistoryBranch, CreateWorkflowExecution What are the changes? - Added domainCacheNoOp file for no implementation of domainCache. Reason: Needed for tools/cli/adminDBCleanCommand.go and adminDBScanCommand.go and cli commands are not required for Cadence UI - Added mock in data_corruption_test - Added DomainName tag to readHistoryRequest - Added domainCache to ExecutionFixerActivity as it was needed for InvariantFactory Other alternatives: - Why not added cache to persistence.Retryer without adding another parameter for cache explicitly? Reason: There were so many calls for persistence.Retryer and and multiple assignments as well. Hence, it will increase the load on the system to have one more parameter added to the call and hence, might reduce speed. And, will increase time as well to make the change.

This is a re-implementation of uber#4916 that's compatible with the new dynamic config refactor, as there are enough changes that it wasn't worth trying to merge or cherry-pick. I've also made some minor improvements, e.g. added some more descriptions and used private types, but there is no behavior change from that PR. --- ES (and in general any kind of "bulk query" API) is a different resource and has quite different ratelimiting needs than other kinds of requests, so this separates the APIs and adds a new ratelimiter dynamic config. Since it kinda looked like we had something for this before, but it wasn't working, I dug around in the code and discovered that the existing limits are pretty wildly incorrectly used, or were actually completely unused. Those variables are now marked as deprecated for visibility, future changes should probably just remove them entirely (and/or correct them).

* Simplified FindFirstVersionHistoryByItem * Refactored unit tests for TaskAckManager * Set SourceTaskID within each replication type * Remove getVersionHistoryItems helper function * Removed processReplication helper * Stop using getters * Minor renames and styling * Moved out hydration logic to separate task_hydrator.go * Moved hydrator tests out * Minor constructor changes * Simple Ptr() usage * Added timeToUnixNano helper * Simplify setting of time fieds * Added comments for exported names * Drop pointer for persistence.ReplicationTaskInfo * Added protection against nil mutable state * No need for copies within HydrateSyncActivityTask * Release workflow lock early when hydrating history * Minor code rearrangement * Move out logging without version histories * Separated HistoryLoader for loading history event blobs from db * Drop ReplicationTaskProcessorReadHistoryBatchSize config. We only page size of 2 ot most * Added MutableStateProvider * Do not expose internal interfaces * Remove toReplicationTask helper * No need for readTasksWithBatchSize helper and useless conversion to task.Info * Added fakeHistoryProvider * Added unit tests for history loader * Added unit tests for mutable state loader * Added TaskHydrator struct * Added DynamicTaskReader * Use DynamicTaskReader in TaskAckManager * Initialize metrics scope once in constructor * Move out domainCache to struct * Minor renaming * Added ackLevelStore interface * Stop accepting shard.Context in TaskAckManager * New unit tests for TaskAckManager * Minor styling * Fix test * Removed TaskAckManager interface * Moved variable * Removed unused struct field * Update licence years * Unit test for unknown replication task * Move out GetTask function to historyEngine itself * More test coverage * Regenerate mocks * Removed ReplicationTaskProcessorReadHistoryBatchSize from constants.go * Make sure workflow context is always released * Pass domainName

Debugging timeout failures in replication is presently quite annoying. Let's get more visibliity here. Co-authored-by: Steven L <stevenl@uber.com>

…er#4938) What Changes? - Added changes to GetWorkflowExecution and UpdateWorkflowExecution - Removed DomainName from persistenceTestBase.go as it is not required : when did the changes it was showing error: over usage of Cassandra service error

* adding reason to cancel workflow.

uber#4943) What changes? - Added changes to ConflictWorkflowExecution and DeleteWorkflowExecution present in persistenceMetricsClients.go - Changed domainName references: previously pointing to nil. (Reason: error coming in integration NDC tests)

…on (uber#4944) What Changes? - Added changes to DeleteCurrentWorkflowExecution and GetCurrentExecution

uber#4946) What Changes? - Added changes to PutReplicationTaskToDLQ and IsWorkflowExecutionExists

) * Partial response of GetReplicationMessages on history service * More generic name for max response size Co-authored-by: David Porter <david.porter@uber.com>

…eteTask and CompleteTaskLessThan (uber#4950) What Changes? - Added domain Tag to UpdateTaskList, DeleteTaskList, LeaseTaskList, CompleteTask and CompleteTaskLessThan

* fix funcorder linter * lint Co-authored-by: David Porter <david.porter@uber.com>

…quest and RecordWorkflowExecutionUninitializedRequest (uber#4968) * Added domainName to context (one remaining change)

…4959) * Adding limit for amount of pending activties in mutable state.

* Replication cache for sharing hydrated messages * Export ErrUnknownCluster * Tag shardID for TaskStore Co-authored-by: David Porter <david.porter@uber.com>

-- Added changes to readHistoryBranchRequest by adding to the persistence-utils

* Return persisted history events blob * Fix after merge

…4969) * Adding first scheduled time metadata field for cron workflows.

What Changed? -- Added changes to task_processor.go -- Added new metrics ReplicationTasksAppliedPerDomain

What changes? -- Added domain tag to replication task -- Added new metrics for replication task : replication_task_applied_per_domain

Fix docker image build, which has been broken since July 5th. Tested by building normally & via docker - both locally and in buildkite. - tcheck wasn't being found, but David and I agree that it seems unnecessary and doesn't seem to be used any more. - Bash wasn't found in the image, but is needed to run scripts/check-gomod-version.sh, so I added it to the alpine image. - During docker image build, the protoc binary had 644 permissions but needed to be executed so I added +x - During docker image build, the PROTO_OUT/uber/cadence directory doesn't exist, so we skip the cp/rm commands that fail otherwise.

… the future (uber#4978)

…cation lag in nanoseconds. (uber#4979)

…r#4983) Trying to run this failed: docker-compose -f docker-compose-mysql.yml up Pulling mysql (mysql:5.7)... 5.7: Pulling from library/mysql ERROR: no matching manifest for linux/arm64/v8 in the manifest list entries Solution found here: https://stackoverflow.com/questions/65456814/docker-apple-silicon-m1-preview-mysql-no-matching-manifest-for-linux-arm64-v8

What changes? -- Added logs for domainName if function returns an error while fetching domainName

Add test flags (controlled by environment variables) that are used to skip tests that have external dependencies. Tests call RequiresX() functions to mark that they depend on X to run. When tests cannot run because they require a dependency, they will be skipped and print out a message describing how to run that test (after starting your dependency.) In order to run tests marked with a dependency, you use the following environment variables: CASSANDRA, MYSQL, MONGODB, POSTGRES. So for example, to run tests that depend on Cassandra: CASSANDRA=1 make test

…er#4980) * Immediate replication task hydration after successful transaction * Regenerate mocks * Fixing tests * More test fixes * Test fixes * More comments and unit tests * Minor * Clean commit * Pass isRunning field to immediateMutableState * Addressing review comments

* Add domain_type tag * Add cluster_group tag

* Add support of update time for Cassandra, Mysql and Postgres (uber#2567) * Fix integration test * Fix one persistence test method * Fix mysql syntax error * Fix cassandra unit test * Add comment to explain unit of update timestamp

…r#4993)

…uber#4838)" (uber#4999) This reverts commit 48a157e.

…uber#5000)

Adds fix for domain replication by ensuring (non-transactionally) that replication messages are higher then ack levels

Co-authored-by: David Porter <david.porter@uber.com>

…lean, warning about different go versions (uber#5019) The .bin folder isn't cleaned and doesn't version itself based on all possible influences... ... so it's kinda just turning into too much of a headache when it misbehaves. In particular, Go versions sometimes change formatting, and that tends to be baked into formatting tools, rather than executing `go` externally. So when e.g. `goimports` is built with a different version of Go than you are currently using, things can get confusing. These are now in the .build folder, so `make clean` will force a rebuild. Downloaded bins like `buf` and `protoc` are pre-built and should generally be resistant to this kind of leakage... and forcing a re-download on every `make clean` seems like definitely a bad idea in some scenarios. So the .bin folder remains, but its use is now much smaller. --- For gofmt purposes, formatting with the latest go version _tends_ to be stable... but unfortunately 1.19 and 1.17 disagree on protoc's code block indentation in comments. As CI currently runs 1.17, we need to be stable with 1.17's output. So this commit does a 1.19 format, then a 1.17 format. This appears stable with our hand-crafted comments, and is likely an improvement over just 1.17. It does, unfortunately, mean that you truly must use <1.19 or your commits may not be stable. We will likely be upgrading to 1.19 soon, but that involves a number of changes, so it's not done here. Stability first, upgrades second. --- The warning is printed immediately for all commands, but does not stop you from using that version: ``` ❯ make Makefile:41: Caution: you are not using CI's go version. Expected: go1.17, current: go version go1.18 darwin/amd64 help Prints a help message showing any specially-commented targets ... ```

… automatically updates the version unless the user manually skips (uber#4994) Emitting version metrics also adding a githook that runs a script the automatically updates the version unless the user manually skips

…hen many workflows have finished at the same time. (uber#5020) * Enhance workflowDeletionTaskJitterRange to handle deletes piling up when many workflows have finished at the same time. * Fix panics when values < 1 are provided * Randomize the timestamp on a second granularity so that deletes are more spread out than before. * Default to 60 minutes. * Enhance workflowDeletionTaskJitterRange to handle deletes piling up when many workflows have finished at the same time. * Fix panics when values < 1 are provided * Randomize the timestamp on a second granularity so that deletes are more spread out than before. * Default to 60 minutes.

Adds a migration feature for failover version

…ix OpenSearch version in dev Docker config (uber#5004) * Fix Makefile rule name in Schema Install instructions of CONTRIBUTING.md * Opportunistic fix of Dependency software names surrounding Makefile rule name being fixed * Fix OpenSearch version pulled by Docker

* Decouple StateBuilder from TaskGenerator * Address comments

…logic to set the update time (uber#5014) * Add updateTime to uninitialized wf execution record * Update updateTime field to use shard time source now to make the logic consistent

* Update DSL query to allow filtering by missing start time and get count of uninitialized wf execution records

…e moved to closed source (uber#5026) Revert to a simple hard coded server version metric emission

This commit replaces `os.MkdirTemp` with `t.TempDir` in tests. The directory created by `t.TempDir` is automatically removed when the test and all its subtests complete. Prior to this commit, temporary directory created using `os.MkdirTemp` needs to be removed manually by calling `os.RemoveAll`, which is omitted in some tests. The error handling boilerplate e.g. defer func() { if err := os.RemoveAll(dir); err != nil { t.Fatal(err) } } is also tedious, but `t.TempDir` handles this for us nicely. Reference: https://pkg.go.dev/testing#T.TempDir Signed-off-by: Eng Zer Jun <engzerjun@gmail.com> Signed-off-by: Eng Zer Jun <engzerjun@gmail.com> Co-authored-by: David Porter <david.porter@uber.com> Co-authored-by: Mantas Šidlauskas <mantass@uber.com>

* Add TLS ServerName as CLI option for Cadence Cassandra Tool * Format with make fmt

…fter continue as new (uber#5032)

* introduce tls cert flag to CLI frontend, add logic for building tls CLIoutbound * remove explicit default value for cert flag for style consistency Co-authored-by: Shijie Sheng <shengs@uber.com> Co-authored-by: David Porter <david.porter@uber.com>

… ID (uber#5036)

* Making a concrete implementation of schema tool into an interface

Co-authored-by: David Porter <david.porter@uber.com>

* Exposing the ability to pull CQL changesets

Add workflow version metrics into a workflow that runs every 10m as a part of cadence-workers

* Introduce dyn. config flag for toggling attr. validation, implement flag check before performing validation * Toggle validation on attaching attr. in WF start, toggle indexProcessor level validation * Update construction of validation tests * Add new dynamic config property to unit test * Handle nil case for new config property in validation Co-authored-by: David Porter <david.porter@uber.com> Co-authored-by: Zack Kirsch <zackk@uber.com>

) Co-authored-by: David Porter <david.porter@uber.com>

…start (uber#5059) * Add method to verify uninitialized workflow execution record then delete from ES * Delete uninitialized workflow execution record if workflow failed to add start event

Update to use static path to the template for es v6 and v7

Add workflow type tag to workflow version metrics.

Updating some cadence dependencies.

* Add domain tag to unregistered field error to track which domain got that problem

…er#5071) * Fix docker image builds with an actually-reliable dependency skip Honestly this is so obvious in retrospect that I don't know why I tried to do the fake-codegen thing. The easiest way to skip dependencies is... to not declare that dependency in the first place.

Add shardId metrics to updateworkflow execution in persistence. Also created a reusable and explicitly named function if other operations require shardId metrics

Added new workflow to emit workflow count by workflow type metrics

Co-authored-by: Steven L <imgroxx@gmail.com>

* Add iWF link * Update README.md

* CDNC-2088 Add attempt-count to task processing logs in file service/history/task/task.go Also changed AttemptCount in tags.go to be type int. * delete comments that was used for self reminder * add attemptCount to log in file service/history/task/cross_cluster_task.go

We got some infinite (or near enough to infinite) hot loops in cron-schedule-Next-ing code today. While we don't yet have any concrete examples to investigate, I'm going to claim it's due to being 2 weeks away from the end of February, and February is weird. People are probably accidentally scheduling things for Feb 30 or 31. There does seem to be some invalid cron schedule parsing happening in robfig/cron, e.g. for `0 0 0 , 0`, but the bulk of the blame for this rests on our code: `.Next` returns a zero-valued time if there is no next time, and that's `.Before` other dates... by a very large margin. There's a decent chance the next `.Next` will return another zero value too, leading to a truly infinite loop. Since a lot of this code was kinda ridiculous about not returning errors, I've just changed that and all callers. In most cases there was a simple place "nearby" that already returned errors, so it just now returns another kind of error. --- Because these invalid schedules are likely *always* invalid (robfig/cron checks 5 years of values, e.g. to work around leap years), and this would *always* infinite loop on those values, I believe it's safe to assume that these invalid cron schedules have never been written to databases.

Added shardId to ES visiblity

* add 3 tags to support adding logs for every manual access * more comment explaining * correct a naming * correct a variable name * change caller tag function name to avoid conflict

…gs" (uber#5115) This reverts commit fbe72b3.

* CLI: print all available dynamic config keys * rename from describe to listall

Blindly forwarding all inbound headers to outbound requests is unambiguously wrong, and causing problems. This adds a semi-flexible system to allow controlling what headers are forwarded, via static and dynamic config. Dynamic config is currently only loaded at startup, but at least internally it's still quicker than changing static config. We should consider making this truly dynamic. As this has historically been copying ?? to outbounds, leading to ?? total headers: the current version does not change anything. We'll likely experiment internally to make sure our new sets of headers are safe with our setup, and will make a separate PR to tighten down the list somewhat when we've confirmed that it works + is likely to work in other clusters. --- Why this kind of add/remove/regex list structure? No strong reason, I've just used it in previous projects pretty happily. Only-inclusive or only-exclusive has been insufficient every time, but I've had this in a couple services for years without needing more. Longer-term we probably want this to be truly dynamically updatable and/or fully pluggable. If we're lucky we might not need more than this though, and driving it via config is pretty convenient and easily understood.

…rd detection (uber#5120) Add sample logging infra and sample logging for updateworkflowexecution hotshard detection

…at it will cover deadlock (uber#5122) * change both getAttempt function to a variale called attempt to avoid deadlock * lead the unit test go into the function where caused deadlock. The unit test will stuck if there is a deadlock * remove a mock in setup that will cause an error for GetTaskType function * update comments for more explaination

Add shard_Id into open source visibility solutions

add metrics for delete workflow execution on a shard level

* Indexer: refactor ES processor * fix kafka key variable, pass processor name

…dy into Attribute for auditing (uber#5124) * Revert "CDNC-2088 (uber#5094) Add attempt-count to task processing logs" This reverts commit fbe72b3. * experiment on adding audit info (has errorsgit status) * move AuditInfo into Attr * implement requestBody Struct, implement it using requests, add it into Attribute to use this field for auditing manual accesses * change struct name to be ManualRequestBody to avoid conflict * change any to interface to solve a compiling error * rerun make go-generate && make fmt && make lint && make copyright for auto generated code * change the PII-filtered request to still be a requset instead of a map * add a utility function to check if access is manual, add request body into Attribute * update with make go-generate && make fmt && make lint && make copyright * update comments and naming * change Sprintf to marshal * add error handling for json.marshal, pass it to the caller of SerializeForLogging function * add a new log tag for actor email address * update interface function error handling * pass in a pointer for serialization instead of a struct * delete the isManual checks when creating Attributes

…5129) move sample logger into persistence metric client for cleaness

add overall persistence count for shardid

* Added checks to look for deprecated flag in the domains and putting workflows up for deletion * code cleaning and minnor changes * Added the domain check to open executions * Cleaned up some code and added a new check for domain * Removed unused constants * updated documentation * Isolated the domain status check in a separate invariant * code cleanup

Fix prometheus frontend label inconsistencies (uber#5087)

What changed? add domain status check in taskAllocator verification Why? tasks in queues should drop for deprecated or deleted domains

…equestbody into Attribute for auditing (uber#5124)" (uber#5145) This reverts commit c462ec0.

* ES: do not set type for v7 * add buildkite job * disable os2 security

Service name should be `worker` not `workers` Co-authored-by: Zijian <Shaddoll@users.noreply.github.com>

…lds are filtered (uber#5151) * add unit test for filter PII functions to check bugs and error when cloning * handles when pointers are nil to avoid bugs and errors * resume the changes from previous reverted branch * use json tags to filter PII instead of hard copies * Create a new struct in unit test that only contains PII. Would be much more clearer to see filtered result. * some clean up

add remaining persistence stuff that goes to a shard

* added and update consistent query per shard metric * testing pershard metric * move sample logger into persistence metric client for cleaness * fix test * fix lint * fix test again * fix lint * sample logging with workflowid tag * added domain tag to logger * metric completed * addressing comments * fix lint * Revert "fix lint" This reverts commit 1e96944. * fix lint second attempt --------- Co-authored-by: Allen Chen <allenchen2244@uber.com>

* ES: single interface for different ES/OpenSearch versions * make fmt

* Elasticsearch: reduce code duplication * address comments --------- Co-authored-by: Zijian <Shaddoll@users.noreply.github.com>

* Set poll interval for filebased dynamic config if not set * update unit test

* Initial checkin for pinot config files

… dropping queued tasks (uber#5164) What changed? When domain cache returned entity not found error, don't drop queued tasks to be more conservative. Why? In cases when the cache is dubious, we shouldn't drop the queued tasks.

* add support for TLS connections by Canary, add development config for Canary with TLS * update README to include new config option * remove testing config --------- Co-authored-by: David Porter <david.porter@uber.com> Co-authored-by: Shijie Sheng <shengs@uber.com> Co-authored-by: Zijian <Shaddoll@users.noreply.github.com>

* Remove misleading type check, Add more detailed log message * removing debugging logging * Handle nil update edge case --------- Co-authored-by: allenchen2244 <102192478+allenchen2244@users.noreply.github.com> Co-authored-by: Zijian <Shaddoll@users.noreply.github.com>

Co-authored-by: David Porter <david.porter@uber.com>

* Adds a small test to catch issues with deadlocks

Metrics for large workflows

* Add thin ES clients

uber#5185) * remove validation & test for add search attribute with no advanced config - Remove validation for Advance Visibility Store - Add Advance Visibility Config check before update ElasticSearch/OpenSearch mapping - Remove co-related test for 'no advanced config' * Update CHANGELOG.md Update CHANGELOG.md * Add warn level message if skip updating OpenSearch/ElasticSearch mapping * Add warn level message and add validSearchAttributes in development.yaml --------- Co-authored-by: Quanzheng Long <prclqz@gmail.com>

* add shardid tag to log * remove counter for overall scope * fix lint

What changed? Added a sharding layer to the NoSQL persistence stack so that Cadence can use multiple Cassandra clusters at once in a physically sharded manner. Cadence is a heavily storage-bounded system, so the limits for the load per Cadence cluster is strictly limited by the underlying storage system. Given the massive adoption of Cadence at Uber, this scale limitation forces us to create more Cadence clusters than we want to operate. This capability will let us have one or two orders of magnitude larger Cadence clusters than we have today. Note that this feature only enables bootstrapping a brand-new cluster with multiple databases behind it. Resharding is designed but not implemented yet. Why? So that a Cadence cluster can be bootstrapped with multiple Cassandra clusters powering it. How did you test it? Added unit tests. Ran samples and tested bench tests in a staging environment. Potential risks Since this change significantly changes the low-level persistence logic, it can cause data loss if something goes terribly wrong. Release notes The change is backward compatible. Existing Cadence cluster configurations can be updated, if desired, to use the sharded NoSQL config format. However, they must continue having a single shard since Cadence still doesn't have the ability to reshard data. Documentation Changes There is a sample config file included in this PR that shows how to make use of the feature in a new cluster.

…ts (uber#5218) * add tasklist traffic metrics for decision task * add logger, remove tasklistID * add taskListCombined * add more fields * add forward metric and source * fix nil * add tlMgr metrics * add more metrics * remove tlMgr metric * only emit metrics if not sticky and not forwarded * create new metrics name for better distinction * add new emitted info * change nil to empty string * add domain and tasklist name tags * add metrics for forwarded tasklist * new metrics for activity task, rename metrics to allow aggregation of both type of tasks * clean up logging * clean up changes in emitInfoOrDebugLog() * resolve comments * improve some logic * fix small error

We have this in an internal wiki, but it's still quite manual, and there are a lot of steps. Some lightweight automation seems worth adopting.

Commits on Sep 6, 2022

Improve logs for task executor (uber#4989 )

Shaddoll authored Sep 6, 2022

Configuration menu

View commit details

Copy full SHA for c3beb64

Browse repository at this point

Copy the full SHA

c3beb64 View commit details

Browse the repository at this point in the history

Commits on Sep 16, 2022

Update idls (uber#4997 )

Shaddoll authored Sep 16, 2022

Configuration menu

View commit details

Copy full SHA for cdbcd02

Browse repository at this point

Copy the full SHA

cdbcd02 View commit details

Browse the repository at this point in the history

Commits on Sep 29, 2022

Fix Cadence CLI (uber#5005 )

Shaddoll authored Sep 29, 2022

Configuration menu

View commit details

Copy full SHA for 832f71a

Browse repository at this point

Copy the full SHA

832f71a View commit details

Browse the repository at this point in the history

Commits on Sep 30, 2022

Re-enable workflow test (uber#5007 )

Shaddoll authored Sep 30, 2022

Configuration menu

View commit details

Copy full SHA for ea49977

Browse repository at this point

Copy the full SHA

ea49977 View commit details

Browse the repository at this point in the history

Commits on Oct 3, 2022

Add new unit test (uber#5008 )

Shaddoll authored Oct 3, 2022

Configuration menu

View commit details

Copy full SHA for 0d35f18

Browse repository at this point

Copy the full SHA

0d35f18 View commit details

Browse the repository at this point in the history

Commits on Oct 12, 2022

Introduce per domain metrics (uber#5012 )

Shaddoll authored Oct 12, 2022

Configuration menu

View commit details

Copy full SHA for 4e67d91

Browse repository at this point

Copy the full SHA

4e67d91 View commit details

Browse the repository at this point in the history

Commits on Nov 15, 2022

Fix workflow cancellation (uber#5025 )

Shaddoll authored Nov 15, 2022

Configuration menu

View commit details

Copy full SHA for 3eb3254

Browse repository at this point

Copy the full SHA

3eb3254 View commit details

Browse the repository at this point in the history

Commits on Dec 9, 2022

Embed schema files (uber#5040 )

Shaddoll authored Dec 9, 2022

Configuration menu

View commit details

Copy full SHA for 0726498

Browse repository at this point

Copy the full SHA

0726498 View commit details

Browse the repository at this point in the history

Commits on Dec 10, 2022

Fix error message (uber#5045 )

ZackLK authored Dec 10, 2022

Configuration menu

View commit details

Copy full SHA for 8e9d827

Browse repository at this point

Copy the full SHA

8e9d827 View commit details

Browse the repository at this point in the history

Commits on Feb 4, 2023

adding a fix (uber#5074 )

davidporter-id-au authored Feb 4, 2023

Configuration menu

View commit details

Copy full SHA for 7670ab2

Browse repository at this point

Copy the full SHA

7670ab2 View commit details

Browse the repository at this point in the history

Setting up some lightweight automation for publishing docker images #1

Are you sure you want to change the base?

Setting up some lightweight automation for publishing docker images #1

Commits on May 10, 2022

Commits on May 11, 2022

Commits on May 16, 2022

Commits on May 17, 2022

Commits on May 18, 2022

Commits on May 19, 2022

Commits on May 20, 2022

Commits on May 23, 2022

Commits on May 24, 2022

Commits on May 25, 2022

Commits on May 26, 2022

Commits on May 27, 2022

Commits on May 30, 2022

Commits on Jun 1, 2022

Commits on Jun 7, 2022

Commits on Jun 9, 2022

Commits on Jun 10, 2022

Commits on Jun 14, 2022

Commits on Jun 15, 2022

Commits on Jun 16, 2022

Commits on Jun 17, 2022

Commits on Jun 21, 2022

Commits on Jun 22, 2022

Commits on Jun 24, 2022

Commits on Jun 27, 2022

Commits on Jun 28, 2022

Commits on Jun 29, 2022

Commits on Jun 30, 2022

Commits on Jul 2, 2022

Commits on Jul 3, 2022

Commits on Jul 5, 2022

Commits on Jul 6, 2022

Commits on Jul 16, 2022

Commits on Jul 18, 2022

Commits on Jul 21, 2022

Commits on Jul 23, 2022

Commits on Jul 26, 2022

Commits on Jul 27, 2022

Commits on Jul 28, 2022

Commits on Aug 2, 2022

Commits on Aug 3, 2022

Commits on Aug 5, 2022

Commits on Aug 9, 2022

Commits on Aug 10, 2022

Commits on Aug 11, 2022

Commits on Aug 12, 2022

Commits on Aug 15, 2022

Commits on Aug 16, 2022

Commits on Aug 18, 2022

Commits on Aug 19, 2022

Commits on Aug 22, 2022

Commits on Aug 23, 2022

Commits on Aug 24, 2022

Commits on Aug 25, 2022

Commits on Aug 26, 2022

Commits on Aug 27, 2022

Commits on Aug 29, 2022

Commits on Aug 31, 2022

Commits on Sep 1, 2022

Commits on Sep 2, 2022

Commits on Sep 6, 2022

Commits on Sep 8, 2022

Commits on Sep 9, 2022

Commits on Sep 16, 2022

Commits on Sep 22, 2022

Commits on Sep 26, 2022

Commits on Sep 27, 2022

Commits on Sep 29, 2022

Commits on Sep 30, 2022

Commits on Oct 3, 2022

Commits on Oct 12, 2022

Commits on Oct 31, 2022

Commits on Nov 2, 2022

Commits on Nov 3, 2022

Commits on Nov 7, 2022

Commits on Nov 9, 2022

Commits on Nov 10, 2022