mirror of https://github.com/zulip/zulip.git
51f74a7fd8
We now have two functions related to digests
for processes:
is_digest_obsolete
write_digest_file
In most cases we now **wait** to write the
digest file until after we've successfully
run a process with its new inputs.
In one place, for database migrations, we
continue to write the digest optimistically.
We'll want to fix this, but it requires a
little more code cleanup.
Here is the typical sequence of events:
NEVER RUN -
is_digest_obsolete returns True
quickly (we don't compute a hash)
write_digest_file does a write (duh)
AFTER NO CHANGES -
is_digest_obsolete returns False
after reading one file for old
hash and multiple files to compute
hash
most callers skip write_digest_file
(no files are changed)
AFTER SOME CHANGES -
is_digest_obsolete returns False
after doing full checks
most callers call write_digest_file
*after* running a process
|
||
|---|---|---|
| .. | ||
| __init__.py | ||
| capitalization.py | ||
| git-tools.bash | ||
| gitlint-rules.py | ||
| graph.py | ||
| html_branches.py | ||
| html_grep.py | ||
| pretty_print.py | ||
| provision.py | ||
| provision_inner.py | ||
| sanity_check.py | ||
| template_parser.py | ||
| test_script.py | ||
| test_server.py | ||