Skip to content

Cluster exitedAfterDisconnect default value fix

The documentation mention for the flag worker.exitedAfterDisconnect as Set by calling .kill() or .disconnect(). Until then, it is undefined. worker.exitedAfterDisconnect can be false too incase the worker exited on its own. So this kinda created three states for the flag, default undefined, false and true.

To fix this I have changed the default value of the flag to false. So it will only be set in case the worker has exited after disconnect.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Merge request reports

Loading