Bug 1340401 - add back definition of FILESIZE_LIMIT; r=obvious-bustage

This commit is contained in:
Nathan Froyd 2017-02-17 10:18:48 -05:00
Родитель 7d4bd52fae
Коммит 6bf34c2a33
1 изменённых файлов: 2 добавлений и 0 удалений

Просмотреть файл

@ -118,6 +118,8 @@ Please commit or stash these changes before vendoring, or re-run with `--ignore-
self._run_command_in_srcdir(args=[cargo, 'vendor', '--sync', mozpath.join(path, 'Cargo.lock'), vendor_dir]) self._run_command_in_srcdir(args=[cargo, 'vendor', '--sync', mozpath.join(path, 'Cargo.lock'), vendor_dir])
self.repository.add_remove_files(vendor_dir) self.repository.add_remove_files(vendor_dir)
# 100k is a reasonable upper bound on source file size.
FILESIZE_LIMIT = 100 * 1024
large_files = set() large_files = set()
cumulative_added_size = 0 cumulative_added_size = 0
for f in self.repository.get_added_files(): for f in self.repository.get_added_files():