Subscribing to SIGINT events etc. handling CTRL+C in terminal

[AlexGustafsson]

The code

index.js:

module.exports = botpress => {
...
function gracefulShutdown() {
    console.log('Initiating graceful shutdown');

    broadcast(botpress, 'message')
    .then(() => {
      console.error('Users have been notified. Will now exit');
      process.exit();
    })
    .catch(error => {
      console.error('Could not broadcast message', error);
    });
  }

  // I.e. CTRL+C
  process.on('SIGINT', gracefulShutdown);
  // I.e. kill -p
  process.on('SIGTERM', gracefulShutdown);
  // I.e. keyboard
  process.on('SIGQUIT', gracefulShutdown);
};

The setup

Botpress: latest
Node: v7.7.4
OS: macOS 10.12.4-beta
Other: Using the Terminal app (default macOS command prompt)

The problem

When starting the project with botpress start and then trying to interrupt it with CTRL+C the SIGINT event is correctly thrown. However, the program terminates right after 'Initiating graceful shutdown' has been written to the screen. I've read about a dozen of examples on how to deal with CTRL+C and the code I've written doesn't seem to be wrong. Is there something I should know about how Botpress handles SIGINT, etc.? (I could not find any such event handlers in the source).

Note: debugging shows that broadcast() is never called

[epaminond]

@AlexGustafsson , where is broadcast coming from? Are you using some package like https://github.com/WebReflection/broadcast?

[AlexGustafsson]

@epaminond no, it's a function written by me.

// Send a message to all subscribed parties
function broadcast(botpress, message) {
  return botpress.db.kvs.get('subscriptions')
  .then(subscriptions => {
    if (!subscriptions)
      return;
      // ...
  });
}

[epaminond]

@AlexGustafsson , I've tried to reproduce it locally with node 8.9.3 and it seems to work fine (e.g. broadcast function gets called and shows console.log statements). node 7.x and 9.x are considered as unstable - could it be an issue? Are you getting same error with node 8.x?

[epaminond]

@AlexGustafsson , feel free to reopen it if you still face this issue.

[AlexGustafsson]

@epaminond Thank you for your help. I’ll see if it works for me in the coming days.