Clark Boylan b058ab447e Don't exit zuul-web when signals are received ... One of the last things the primary thread in zuul-web does after configuring and starting the service is to call signal.pause(). This causes it to wait for any signal to arrive and once a signal has arrived and been handled we stopped zuul-web and killed the process. This is a problem because SIGUSR2 is expected to toggle preformance and debug tooling in the process. But since we exit after signal.pause() returns we can't do that properly. Fix this by removing the signal.pause() loop entirely and instead wait for the web command thread to die. This command thread is the last thing stopped by ZuulWeb.stop() so we can join() on it to wait for a complete stop of the ZuulWeb service. Change-Id: I66fbb86c25479823faeded8ede9c6204846c35c1		2020-05-04 10:07:28 -07:00
..
__init__.py	Deprecate -d switch for running in foreground	2020-02-22 18:02:30 +01:00
client.py	Add client_id to RPC client	2020-01-28 10:16:19 +01:00
executor.py	Change default job_dir location	2019-06-13 13:43:16 -07:00
fingergw.py	Remove default user for fingergw	2019-02-07 12:33:25 -08:00
manage_ansible.py	zuul-manage-ansible: add validate option	2020-01-28 23:15:49 +01:00
merger.py	Import Zuul modules at top of files	2018-03-05 11:23:32 +01:00
migrate.py	dict_object.keys() is not required for *in* operator	2018-12-03 12:04:55 +05:30
scheduler.py	Merge "Add TLS support for ZooKeeper"	2020-04-14 21:35:33 +00:00
web.py	Don't exit zuul-web when signals are received	2020-05-04 10:07:28 -07:00