Files
meteor/tools
David Glasser 58a27d123c Fix and test some runner error handling issues
- Exit with failure if proxy starts to listen. Previously, we got stuck
  inside ProxyRunner.start(), and since we weren't waiting on any IO
  we'd exit 0!  (The existence of a yielded fiber is not sufficient to
  block Node exit.)

- Don't print various bits of startup text if we are stopped midway.

- Stop main Runner immediately if proxy or mongo runners invoke
  onFailure, rather than waiting for wait to be called and return.

- Ensure that a few Futures don't get return called on them multiple
  times.

- Ensure we don't try to call close() on the proxy's TCP server if it
  failed to listen in the first place.
2014-02-11 00:17:22 -08:00
..
2014-01-27 14:17:31 -08:00
2014-02-10 19:25:45 -08:00
2014-02-04 14:04:30 -08:00
2014-02-07 11:59:21 -08:00
2014-01-03 18:20:07 -08:00
2014-02-07 17:55:46 -08:00
2014-02-10 19:12:52 -08:00
2014-02-05 15:52:05 -08:00
2014-02-04 11:23:56 -08:00
2014-01-07 14:46:39 -08:00
2014-02-04 17:46:19 -08:00
2013-12-30 05:39:14 -08:00
2014-01-27 02:31:39 -08:00
2014-02-04 14:04:30 -08:00