joeduffy a5a6c79925 Keep RPC connections alive for as long as we need them ... The change to tear down RPC connections after the program exits -- to fix problems on Linux presumably due to the way libuv is implemented -- unfortunately introduces nondeterminism and overzealous termination that can happen at inopportune times. Instead, we need to wait for the current RPC queue to drain. To fix this, we'll maintain a list of currently active RPC calls and, only once they have completed, will we close the clients.		2017-09-07 14:50:17 -07:00
..
native	Move environment entry serialization into JavaScript	2017-09-05 16:57:23 -07:00
closure.ts	Add Promises leak and hang detection	2017-09-06 18:35:20 -07:00
config.ts
debuggable.ts	Add Promises leak and hang detection	2017-09-06 18:35:20 -07:00
index.ts
langhost.ts	Properly report closes due to signals	2017-09-05 12:01:55 -07:00
log.ts	Keep RPC connections alive for as long as we need them	2017-09-07 14:50:17 -07:00
property.ts	Add Promises leak and hang detection	2017-09-06 18:35:20 -07:00
resource.ts	Keep RPC connections alive for as long as we need them	2017-09-07 14:50:17 -07:00
settings.ts	Keep RPC connections alive for as long as we need them	2017-09-07 14:50:17 -07:00