Releases: photostructure/batch-cluster.js
Releases · photostructure/batch-cluster.js
v5.6.8
v5.6.7
v5.6.3
- 📦 Moved to photostructure github org
- 📦 updated dependencies
v5.6.1
v5.6.0
- 🐛 / ✨
BatchProcess.end()
didn't correctly implementgracefully
(which resulted in spuriousend(): called while not idle
errors), and allowed for multiple calls to destroy and disconnect from the child process, which may or may not have been ill-advised. - 📦 attempts were made to make CI less flaky.
Commits
- remove node 6 tests, which tend to be flaky. Node 6 is EOL end of the month, anyway. 6f1db33
- mac ci is really slow. a66e061
- bump up timeout for CI 9cb0180
- moar deflaking b641f95
- one more effort to deflake CI 6c85066
- current task handling on end. lots of notes. a8af744
- deflake onIdle cab97e4
- fix shutdown 5dedd38
- await until c98331d
- test cleanup 82d4a0d
- require source-map-support so CI test jobs have line numbers 74aa02d
- prep 5.6.0. rebuild docs and run prettier. c096cc2
- Fix BatchProcess.end(graceful) to be graceful. Replace BatchProcess.end with a promise-based latch. c8bd169
v5.5.0
v5.5.0
- ✨ Added
BatchCluster.isIdle
. Updated deps. Deflaked CI by embiggening - ✨ Added
BatchClusterOptions.cleanupChildProcs
, in case you want to handle process cleanup yourself. - 📦 Updated deps. Deflaked CI by embiggening timeouts.
- Happy 🥧 day.
Commits
v5.4.0
- ✨ "wear-leveling" for processes. Previously, only the first-spawned child
process would service most task requests, but that caused issues with (very)
long-running tasks where the other child processes would be spooled off ram,
and could time out when requested later. - 🐞
maxProcs
is respected again. In prior builds, if tasks were enqueued all
at once, prior dispatch code would only spin 1 concurrent task at a time. - 🐞 Multiple calls to
BatchProcess.end
would result in different promise
resolution targets: the second call to.end()
would resolve before the
first. This was fixed. - ✨ BatchProcessOptions's
minDelayBetweenSpawnMillis
was added, to help relieve undue system load on
startup. It defaults to 1.5 seconds and can be disabled by setting it to 0.
Commits:
- deflake 0f24527
- moar tests and better concurrency! 50c0548
- yarn docs 280858f
- enable downlevelIteration 8863da7
- salita -u ; yarn install fd9202d
- round-robin find 99bd8db
- run more iterations to reduce test flake ed97cc9
- more rigorous test serial tests 199454d
- validate maxProcs actually exercises all child pids a0ffd6a