aboutsummaryrefslogtreecommitdiff
path: root/test/compress/issue-637.js
diff options
context:
space:
mode:
authorAlex Lam S.L <alexlamsl@gmail.com>2018-02-08 03:31:51 +0800
committerGitHub <noreply@github.com>2018-02-08 03:31:51 +0800
commitd66d86f20bc231bd8d305ee5ba05efa77aa8b6be (patch)
tree1eae73edc0f4fab7d3dbffc5dd94736953ac6dbf /test/compress/issue-637.js
parent905325d3e21a5dc3d3f5835f609f30055c25bf2b (diff)
downloadtracifyjs-d66d86f20bc231bd8d305ee5ba05efa77aa8b6be.tar.gz
tracifyjs-d66d86f20bc231bd8d305ee5ba05efa77aa8b6be.zip
account for exceptions in `AST_Assign.left` (#2892)
fixes #2891
Diffstat (limited to 'test/compress/issue-637.js')
0 files changed, 0 insertions, 0 deletions
3 +0200'>2020-09-02installer: Run the installation inside a container....When the store overlay is mounted, other processes such as kmscon, udev and guix-daemon may open files from the store, preventing the underlying install support from being umounted. See: https://lists.gnu.org/archive/html/guix-devel/2018-12/msg00161.html. To avoid this situation, mount the store overlay inside a container, and run the installation from within that container. * gnu/build/shepherd.scm (fork+exec-command/container): New procedure. * gnu/services/base.scm (guix-shepherd-service): Support an optional PID argument passed to the "start" method. If that argument is passed, ensure that guix-daemon enters the given PID MNT namespace by using fork+exec-command/container procedure. * gnu/installer/final.scm (umount-cow-store): Remove it, (install-system): run the installation from within a container. * gnu/installer/newt/final.scm (run-install-shell): Remove the display hack. Mathieu Othacehe 2020-06-12shepherd: 'read-pid-file/container' terminates the whole process group....This mirrors a change made in the Shepherd 0.8.0. Previously, upon startup failure, we could have left processes behind. * gnu/build/shepherd.scm (read-pid-file/container): Kill (- PID) instead of PID. Ludovic Courtès 2020-06-12shepherd: Unblock signals in the child process....Fixes <https://bugs.gnu.org/41791>. Reported by Tobias Geerinckx-Rice <me@tobias.gr>. This change mirrors changes made in the Shepherd 0.8.1, where signals are blocked in the shepherd process in support of 'signalfd'. The regression was introduced with the switch to 0.8.1 in 3f9c62d1a8b345909adaeb22f454ad22554c55a1: child processes would not receive SIGTERM upon 'herd stop SERVICE'. * gnu/build/shepherd.scm <top level>: Autoload (shepherd system). (make-forkexec-constructor/container): Call call to 'sigaction' and 'unblock-signals'. Ludovic Courtès