Will DuanandGitHub e54aeec8ca Fix migration back and forth local event handler (#5774) ...

- Fix migration back and forth usecase and add more tests
- fix lint

## What changed?
<!-- Describe what has changed in this PR -->
1. Fix a bug on handling replication back and forth case
2. Add more integration test to test the ^ scenario
## Why?
<!-- Tell your future self why have you made these changes -->
LocalGeneratedEventHandler cannot properly handle force replication
case.
## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
Integration test
## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->
Feature is gated by a feature flag
## 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/`? -->
n/a
## 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-04-25 18:33:41 +00:00

..

testevents

Fix migration back and forth local event handler (#5774)

2024-04-25 18:33:41 +00:00

ndc_test.go

enable streaming replication by default (#5737)

2024-04-17 09:37:06 -07:00

replication_migration_back_test.go

Fix migration back and forth local event handler (#5774)

2024-04-25 18:33:41 +00:00

replication_task_batching_test.go

Add replication back test case (#5746)

2024-04-19 14:30:49 -07:00

replication_test.go

Remove history queue reader registration logic (#5420)

2024-02-20 14:44:38 -08:00

test_data.go

Fix migration back and forth local event handler (#5774)

2024-04-25 18:33:41 +00:00