Alex ShtinandGitHub 1abbb1754d Apply effects immediately after mutable state is persisted (#5349) ...

## What changed?
<!-- Describe what has changed in this PR -->
Apply effects immediately after mutable state is persisted.

## Why?
<!-- Tell your future self why have you made these changes -->
Bug fix. Previously, if error happens after mutable state is persisted,
`defer` block rolled back accumulated effects changes and left update
registry in inconsistent state.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
Run different load test scenarios with fault injection enabled.

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

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

2024-01-24 17:40:34 -08:00

..

buffer_test.go

Refactor the Update type to a state machine (#4297)

2023-05-10 12:14:02 -07:00

buffer.go

Apply effects immediately after mutable state is persisted (#5349)

2024-01-24 17:40:34 -08:00

controller.go

Refactor the Update type to a state machine (#4297)

2023-05-10 12:14:02 -07:00

immediate_test.go

Refactor the Update type to a state machine (#4297)

2023-05-10 12:14:02 -07:00

immediate.go

🧹 Update Workflow nits (#4964)

2023-10-13 14:08:28 -07:00