Error Injection Pr
Goals:
- find the minimum set of shard assignments that must have resilient behavior for shard assignments callsites to work end to end.
- guard against regressions for CRUD requests that are known to work correctly given current resiliency protocols.
- Make slight augmentations to our resiliency job to allow verifying resiliency for only a subset of all MySQL main queries.
TODOs:
- figure out how to make the shard assignments runner a variant of the existing runner.
PR chain -> live shard helper refactoring — withCompositeConnectionAsMainConnectionAsync becoming object, and scanShardsForObjectAsync having a callsite -> resiliency runner with:
- new queryHashesToForceInject field
- New beforeEach and afterEach, where we’re doing only shard assignments setup
- New crud requests that will run in all environments — do this first, make sure that existing tests work.
- Uncomment out the “only some processes tests”
- Add comments about the weirdness for certain things — Need to add a new crud request end-point for helper
Things to talk about with Keunwoo –
- Things like row comment notification renderer
uid: 202208291247 tags: #airtable