Dir is not cleaned when I hit ctrl+c

[JanBednarik]

I'm using tmp package in unit tests with tmp.setGracefulCleanup();. I'm creating temp directory for tests with unsafeCleanup = true.

It works fine if I don't hit ctrl+c to interrupt tests. Then the temp dir is not deleted. How can I get it deleted automatically in this case?

[silkentrance]

@JanBednarik Please provide additional information: OS, tmp version, node version etc.

Could you also give us a link to your repository, so that we may look at the code directly?

[silkentrance]

@JanBednarik ping

[silkentrance]

@JanBednarik do you work under windows?

For reference:
https://stackoverflow.com/questions/10021373/what-is-the-windows-equivalent-of-process-onsigint-in-node-js
https://stackoverflow.com/questions/20165605/detecting-ctrlc-in-node-js

[JanBednarik]

Versions:
OS X Sierra 10.12.5
Node LTS 6.11.0
tmp 0.0.31
jest 20.0.3

Should cleanup work with ctrl+c? Maybe it's somehow related to Jest test runner. I'll try to prepare some simple failing case.

[JanBednarik]

@silkentrance Here is an example:

File: package.json

{
  "name": "tmptest",
  "scripts": {
    "test": "jest"
  },
  "dependencies": {
    "jest": "20.0.4",
    "tmp": "0.0.31"
  }
}

File: main.test.js

'use strict';

const tmp = require('tmp');

tmp.setGracefulCleanup();

test('main', done =>
    tmp.dir({ template: 'tmp-XXXXXX' }, (err, path) => {
        console.log(`dir: ${path}\npress ctrl+c`);
        setTimeout(done, 3000);
    })
);

Run:

$ npm install
$ npm test

And interrupt the test with ctrl+c.

[silkentrance]

@JanBednarik thank your very much. I think that I have found the problem. There exists a SIGINT event and tmp should be listening on that, too. The only problem is that under Windows one must take a different approach. I will look into this.

[davidshepherd7]

This package might be helpful. It's supposed to allow you to run code no matter how the process exits. It has Windows tests so presumably it works on Windows too.

[silkentrance]

@davidshepherd7 the package looks good. I will try that.

[silkentrance]

@davidshepherd7 I tried signal-exit, but to no avail so far. In addition, it also installs listeners for SIGHUP which I believe is not what we want as most user code uses this to implement some way of applying changes to the configuration etc. And we do not want to clean up existing tmp files or directories prematurely.

https://stackoverflow.com/questions/10021373/what-is-the-windows-equivalent-of-process-onsigint-in-node-js