. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Two-Phase Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . inconsistencies in indentation. ∗ Use 2 spaces in everything except Go. ∗ In Go, just use goimports. • Commit message format: 22 – : This is a short description of the change. If necessary , more Source The Vitess code is hosted on GitHub. This repository is called upstream. You develop and commit your changes in a clone of our upstream repository (shown as local in the image above). Then you

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Two-Phase Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . inconsistencies in indentation. ∗ Use 2 spaces in everything except Go. ∗ In Go, just use goimports. • Commit message format: – : This is a short description of the change. If necessary , more GitHub (https://github.com/vitessio/vitess). This repository is called upstream. You develop and commit your changes in a clone of our upstream repository (shown as local in the image above). Then you

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Two-Phase Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . inconsistencies in indentation. – Use 2 spaces in everything except Go. – In Go, just use goimports. • Commit message format: 40 – – : This is a short description of the change. If necessary Source The Vitess code is hosted on GitHub. This repository is called upstream. You develop and commit your changes in a clone of our upstream repository (shown as local in the image above). Then you

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Two-Phase Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . inconsistencies in indentation. – Use 2 spaces in everything except Go. – In Go, just use goimports. • Commit message format: – : This is a short description of the change. If necessary , more Source The Vitess code is hosted on GitHub. This repository is called upstream. You develop and commit your changes in a clone of our upstream repository (shown as local in the image above). Then you

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Two-Phase Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . inconsistencies in indentation. – Use 2 spaces in everything except Go. – In Go, just use goimports. • Commit message format: – : This is a short description of the change. If necessary , more Source The Vitess code is hosted on GitHub. This repository is called upstream. You develop and commit your changes in a clone of our upstream repository (shown as local in the image above). Then you

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Two-Phase Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . inconsistencies in indentation. – Use 2 spaces in everything except Go. – In Go, just use goimports. • Commit message format: – : This is a short description of the change. If necessary , more Source The Vitess code is hosted on GitHub. This repository is called upstream. You develop and commit your changes in a clone of our upstream repository (shown as local in the image above). Then you

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Two-Phase Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . inconsistencies in indentation. ∗ Use 2 spaces in everything except Go. ∗ In Go, just use goimports. • Commit message format: – : This is a short description of the change. If necessary , more Source The Vitess code is hosted on GitHub. This repository is called upstream. You develop and commit your changes in a clone of our upstream repository (shown as local in the image above). Then you

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Two-Phase Commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . inconsistencies in indentation. – Use 2 spaces in everything except Go. – In Go, just use goimports. • Commit message format: – : This is a short description of the change. If necessary , more Source The Vitess code is hosted on GitHub. This repository is called upstream. You develop and commit your changes in a clone of our upstream repository (shown as local in the image above). Then you

repository at https://github.com/vitessio/vitess was used as the codebase to be verified. ▪ branch master commit 092479406b27ae61a8fcd146a0e08af2d51a7245 ◦ Furthermore, the minimal reference client https://github https://github.com/vitessio/messages was used as additional illustration of use-cases. ▪ branch master commit 7d2ac2189573a7d26cf0f42e17df749673e3d16f ◦ The testers received unencumbered access to a Kubernetes

fuzzers against the cloned Vitess code. As such, the fuzzers are always run against the latest Vitess commit. This build cycle happens daily and OSS-Fuzz will verify if any existing bugs have been fixed. If Vitess manages its source code on Github which makes it version controlled and possible to verify the commit history. The source code is retained indefinitely and all commits are verified by two different maintainers