Keith Mashinter
Keith Mashinter
We encountered this as well, with JMeter 5.6.2, and just using HttpClient4 in the Http Request Defaults didn't help, but also setting time_to_live as below in the jmeter.properties or similar...
I've had similar problems with more recent node-gyp as used through @parcel/watcher. I had to use "@parcel/watcher": "~2.1.0" in my project devDependencies to avoid problems with 'gyp: binding.gyp not found'...
I'm also interested in this fix to avoid potential global and inflight issues.
I have Windows 10, so I'll give try the branch tonight.
From a first pass on Windows 10 these look like platform-dependent differences. Maybe they should be skipped for Windows. I'll check again in some more detail tomorrow. ``` npm run...
I've created fixes for Windows with this pull-request, thanks! `npm run test` is clean on Windows 10. https://github.com/shelljs/shelljs/pull/1165
@nfischer I'll close this messy one and opened a simpler one here against shelljs/shelljs:master. Hmm, maybe I can't close it myself. https://github.com/shelljs/shelljs/pull/1166
I had to use "@parcel/watcher": "~2.1.0" in my project devDependencies to avoid problems with 'gyp: binding.gyp not found' on both Windows 10 with Python 3.11 and MacOS 12.6.5 with Python...