Fail 'Get Diff' requests for file sizes that exceed 50Mb

We add a new DiffValidator extension point with one implementation that
checks the file size and fails the diff if the file size or size delta
exceeded 50Mb.

The validation is performed in PatchScriptFactory after the file diff is
computed through DiffOperations. This codepath is executed on the 'Get
Diff' request path, but not on 'List Files'.

The validation is done after the diff computation and not before it for
two reasons:
1) 'List Files' and 'Get Diff' both use the exact same logic in
   DiffOperations. This was designed that way because some of the fields
   that we return with the 'List Files' response require performing the
   file diff (e.g. lines_inserted/deleted). If we fail the request
   before the diff computation, this will mean that both 'List Files'
   and 'Get Diff' will be affected. We don't want to do that so that
   existing changes with large file sizes can continue to load and show
   the files in the web UI, but only expanding diffs to fail.  Though
   this can be solved with some refactoring of the code to separate both
   code paths and only fail 'Get Diff' requests "before" the diff
   computation, doing that will duplicate the code that's already
   encapsulated and executed inside the diff cache (reading the tree,
   getting file size).

2) Doing the validation after the diff computation is still beneficial,
   since we'll fail and skip the remaining code that formats the entire
   two sides of the diff (requires loading the file). Also we fail
   instead of returning a response of very large size. Note that the
   diff computation in DiffOperations only returns the list of edits
   (start/end lines and positions at both sides as integers).

Google-Bug-Id: b/288895561
Release-Notes: Fail 'Get Diff' requests for file sizes that exceed 50Mb
Change-Id: I174b58239b67abc8891f5b1c914dca86e10cdb93
8 files changed
tree: 070ce2cdd315f8bb1fc7f7f2c6f38705e9647672
  1. .settings/
  2. .ts-out/
  3. antlr3/
  4. contrib/
  5. Documentation/
  6. e2e-tests/
  7. java/
  8. javatests/
  9. lib/
  10. modules/
  11. plugins/
  12. polygerrit-ui/
  13. prolog/
  14. prologtests/
  15. proto/
  16. resources/
  17. tools/
  18. webapp/
  19. .bazelignore
  20. .bazelproject
  21. .bazelrc
  22. .bazelversion
  23. .editorconfig
  24. .git-blame-ignore-revs
  25. .gitignore
  26. .gitmodules
  27. .gitreview
  28. .mailmap
  29. .pydevproject
  30. .zuul.yaml
  31. BUILD
  32. COPYING
  33. INSTALL
  34. Jenkinsfile
  35. package.json
  36. README.md
  37. SUBMITTING_PATCHES
  38. version.bzl
  39. web-dev-server.config.mjs
  40. WORKSPACE
  41. yarn.lock
README.md

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status Maven Central

Objective

Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.

Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.

Documentation

For information about how to install and use Gerrit, refer to the documentation.

Source

Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.

Reporting bugs

Please report bugs on the issue tracker.

Contribute

Gerrit is the work of hundreds of contributors. We appreciate your help!

Please read the contribution guidelines.

Note that we do not accept Pull Requests via the Github mirror.

Getting in contact

The Developer Mailing list is repo-discuss on Google Groups.

License

Gerrit is provided under the Apache License 2.0.

Build

Install Bazel and run the following:

    git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
    cd gerrit && bazel build release

Install binary packages (Deb/Rpm)

The instruction how to configure GerritForge/BinTray repositories is here

On Debian/Ubuntu run:

    apt-get update && apt-get install gerrit=<version>-<release>

NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.

On CentOS/RedHat run:

    yum clean all && yum install gerrit-<version>[-<release>]

On Fedora run:

    dnf clean all && dnf install gerrit-<version>[-<release>]

Use pre-built Gerrit images on Docker

Docker images of Gerrit are available on DockerHub

To run a CentOS 8 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8

To run a Ubuntu 20.04 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20

NOTE: release is optional. Last released package of the version is installed if the release number is omitted.