• epriestley's avatar
    Add a "lock log" for debugging where locks are being held · 44f0664d
    epriestley authored
    Summary: Depends on D19173. Ref T13096. Adds an optional, disabled-by-default lock log to make it easier to figure out what is acquiring and holding locks.
    
    Test Plan: Ran `bin/lock log --enable`, `--disable`, `--name`, etc. Saw sensible-looking output with log enabled and daemons restarted. Saw no additional output with log disabled and daemons restarted.
    
    Maniphest Tasks: T13096
    
    Differential Revision: https://secure.phabricator.com/D19174
    44f0664d
Name
Last commit
Last update
..
accountadmin Loading commit data...
almanac Loading commit data...
aphlict Loading commit data...
audit Loading commit data...
auth Loading commit data...
bulk Loading commit data...
cache Loading commit data...
calendar Loading commit data...
celerity Loading commit data...
commit-hook Loading commit data...
conduit Loading commit data...
config Loading commit data...
differential Loading commit data...
diviner Loading commit data...
drydock Loading commit data...
fact Loading commit data...
feed Loading commit data...
files Loading commit data...
garbage Loading commit data...
harbormaster Loading commit data...
i18n Loading commit data...
lipsum Loading commit data...
lock Loading commit data...
mail Loading commit data...
nuance Loading commit data...
people Loading commit data...
phd Loading commit data...
phortune Loading commit data...
policy Loading commit data...
remove Loading commit data...
repository Loading commit data...
search Loading commit data...
sms Loading commit data...
ssh-auth Loading commit data...
ssh-auth-key Loading commit data...
ssh-connect Loading commit data...
ssh-exec Loading commit data...
storage Loading commit data...
trigger Loading commit data...
webhook Loading commit data...
worker Loading commit data...