[ARROW-14473] [JS][Release] Ensure can use nohup with the release script

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 7.0.0
• Component/s: JavaScript
• External issue URL: https://github.com/apache/arrow/issues/30032
• Assignee: Unassigned
• Reporter: Benson Muite
• Created: 26/Oct/21 13:54
• Updated: 11/Jan/23 08:40

Description

Node may have problems reading and writing files when called using nohup. Directly running

env "TEST_DEFAULT=0" env "TEST_JS=1"  bash dev/release/verify-release-candidate.sh source 6.0.0 3

seems to work, but

nohup env "TEST_DEFAULT=0" env "TEST_JS=1"  bash dev/release/verify-release-candidate.sh source 6.0.0 3 > log.out &

may not work [1]. Either document that one can use

(nohup env "TEST_DEFAULT=0" env "TEST_JS=1"  bash dev/release/verify-release-candidate.sh source 6.0.0 3 > log.out & )

or modify the javascript implementation so that it can run as a background process and still find files so that the error:

yarn run v1.22.17
$ /tmp/arrow-6.0.0.BDnN3/apache-arrow-6.0.0/js/node_modules/.bin/run-s
clean:all lint build
events.js:377
        throw er; // Unhandled 'error' event
        ^

Error: EBADF: bad file descriptor, read
Emitted 'error' event on ReadStream instance at:
      at internal/fs/streams.js:173:14
      at FSReqCallback.wrapper [as oncomplete] (fs.js:562:5) {
    errno: -9,
    code: 'EBADF',
    syscall: 'read'
}
error Command failed with exit code 1.

is not obtained.

[1] https://stackoverflow.com/questions/16604176/error-ebadf-bad-file-descriptor-when-running-node-using-nohup-of-forever