documentation is required if the feature changes or adds to existing behavior. Bug fixes If you are creating a PR to fix a bug, make sure to create an end-to-end test that fails without your change. This reproduction case that will make sure this particular bug does not show up again, and that clearly shows on your PR what bug you are fixing. While you are fixing the bug, it’s valuable if you take the time to step prevented. Some additional points to keep in mind: • Does this change match an existing design / bug? • Is this change going to log too much? (Error logs should only happen when the component is in bad

documentation is required if the feature changes or adds to existing behavior. Bug fixes If you are creating a PR to fix a bug, make sure to create an end-to-end test that fails without your change. This reproduction case that will make sure this particular bug does not show up again, and that clearly shows on your PR what bug you are fixing. While you are fixing the bug, it’s valuable if you take the time to step prevented. Some additional points to keep in mind: • Does this change match an existing design / bug? 37 • Is this change going to log too much? (Error logs should only happen when the component is

documentation is required if the feature changes or adds to existing behavior. Bug fixes If you are creating a PR to fix a bug, make sure to create an end-to-end test that fails without your change. This reproduction case that will make sure this particular bug does not show up again, and that clearly shows on your PR what bug you are fixing. While you are fixing the bug, it’s valuable if you take the time to step prevented. Some additional points to keep in mind: • Does this change match an existing design / bug? 36 • Is this change going to log too much? (Error logs should only happen when the component is

documentation is required if the feature changes or adds to existing behavior. Bug fixes If you are creating a PR to fix a bug, make sure to create an end-to-end test that fails without your change. This reproduction case that will make sure this particular bug does not show up again, and that clearly shows on your PR what bug you are fixing. While you are fixing the bug, it’s valuable if you take the time to step prevented. Some additional points to keep in mind: * Does this change match an existing design / bug? * Is this change going to log too much? (Error logs should only happen when the component is in bad

documentation is required if the feature changes or adds to existing behavior. Bug fixes If you are creating a PR to fix a bug, make sure to create an end-to-end test that fails without your change. This reproduction case that will make sure this particular bug does not show up again, and that clearly shows on your PR what bug you are fixing. While you are fixing the bug, it’s valuable if you take the time to step prevented. Some additional points to keep in mind: 35 • Does this change match an existing design / bug? • Is this change going to log too much? (Error logs should only happen when the component is in bad

and reviewers need to answer these general questions: • Does this change match an existing design / bug? • Is there proper unit test coverage for this change? All changes should increase coverage. We need SetKeyspaceServedFrom Changes the ServedFromMap manually. This command is intended for emergency fixes. This field is automatically set when you call the MigrateServedFrom command. This command does not called with exactly 2 arguments. ShardReplicationFix Walks through a ShardReplication object and fixes the first error that it encounters. Example Arguments • – Required. A cell is a location

and reviewers need to answer these general questions: • Does this change match an existing design / bug? • Is there proper unit test coverage for this change? All changes should increase coverage. We need SetKeyspaceServedFrom Changes the ServedFromMap manually. This command is intended for emergency fixes. This field is automatically set when you call the MigrateServedFrom command. This command does not called with exactly 2 arguments. ShardReplicationFix Walks through a ShardReplication object and fixes the first error that it encounters. Example Arguments • – Required. A cell is a location

and reviewers need to answer these general questions: • Does this change match an existing design / bug? • Is there proper unit test coverage for this change? All changes should increase coverage. We need SetKeyspaceServedFrom Changes the ServedFromMap manually. This command is intended for emergency fixes. This field is automatically set when you call the MigrateServedFrom command. This command does not called with exactly 3 arguments. ShardReplicationFix Walks through a ShardReplication object and fixes the first error that it encounters. Example Arguments • – Required. A cell is a location

If OSS-fuzz finds that any bugs have been fixed OSS-Fuzz marks the crashes as fixed in the Monorail bug tracker and notifies maintainers. In each fuzzing iteration, OSS-Fuzz uses its corpus accumulated Monorail bug tracker is created. 3. An email is sent to maintainers with links to the report and relevant entry in the bug tracker. OSS-Fuzz has a 90 day disclosure policy, meaning that a bug becomes becomes public in the bug tracker if it has not been fixed. The detailed report is never made public. The Vitess maintainers will fix issues upstream, and OSS-Fuzz will pull the latest Vitess master branch the