epriestley 69bff489d4 Generate a random unique "Request ID" for SSH requests so processes can coordinate better ... Summary: Depends on D19247. Ref T13109. When we receive an SSH request, generate a random unique ID for the request. Then thread it down through the process tree. The immediate goal is to let the `ssh-exec` process coordinate with `commit-hook` process and log information about read and write lock wait times. Today, there's no way for `ssh-exec` to interact with the `PushEvent`, but this is the most helpful place to store this data for users. Test Plan: Made pushes, saw the `PushEvent` table populate with a random request ID. Exported data and saw the ID preserved in the export. Maniphest Tasks: T13109 Differential Revision: https://secure.phabricator.com/D19249		2018-03-22 13:44:30 -07:00
..
almanac
cache
celerity
daemon
diviner
drydock	When bin/drydock lease is interrupted, release leases	2018-02-13 13:14:21 -08:00
fact
files
fpm
init	When bin/drydock lease is interrupted, release leases	2018-02-13 13:14:21 -08:00
install	Issue setup guidance recommending MySQLi and MySQL Native Driver	2018-03-13 12:38:09 -07:00
lipsum
mail
people
repository	Generate a random unique "Request ID" for SSH requests so processes can coordinate better	2018-03-22 13:44:30 -07:00
search
setup	Add a "lock log" for debugging where locks are being held	2018-03-05 17:55:34 -08:00
sms
sql
ssh	Generate a random unique "Request ID" for SSH requests so processes can coordinate better	2018-03-22 13:44:30 -07:00
symbols
user	Remove "set password" from bin/accountadmin and let bin/auth recover recover anyone	2018-01-23 10:58:11 -08:00
util
__init_script__.php
manage_bulk.php