Only use the user's home directory for host web shells
## Problem
Container, app and VM web shells opened by a non-root user got that user's host home directory as HOME, and the shell child started in it. Inside containers this pointed $HOME and ~ at a host path, so the image's root dotfiles were not used.
## Solution
Pass the shell type to the worker thread and use it for both the command and the environment. Host shells keep the user's home as HOME; container, app and VM shells get /root. The shell child always starts in /root, since login changes into HOME itself for host shells.
NAS-144864 / 28.0.0-BETA.1 / Only use the user's home directory for host web shells (#20068)
## Problem
Container, app and VM web shells opened by a non-root user got that
user's host home directory as HOME, and the shell child started in it.
Inside containers this pointed $HOME and ~ at a host path, so the
image's root dotfiles were not used.
## Solution
Pass the shell type to the worker thread and use it for both the command
and the environment. Host shells keep the user's home as HOME;
container, app and VM shells get /root. The shell child always starts in
/root, since login changes into HOME itself for host shells.
[mlir] Optimize `isOpTriviallyDead` greedy rewriter checks for deeply nested IR (#231423)
See the discussion
https://github.com/llvm/llvm-project/pull/230961#issuecomment-6130021318
Driver checks `isOpTriviallyDead` after each IR modifications and
`isOpTriviallyDead` walked the entire nested chain for
`HasRecursiveMemoryEffects`.
Cache op deadness in driver and invalidate on IR change.
Also, `Operation *dumpRootOp = getDumpRootOp(op);` only needed for debug
printing was called unconditionally and was also noticeable in profiler.
Call it only if debug printing is actually enabled.
Added synthetic 1000-nested IR test, generated by python. Test doesn't
actually check execution times, but I hope someone will notice if it
suddenly start to take 30s.
[9 lines not shown]
[flang] Undefine HUGE after including cmath (#236221)
Older glibc versions expose HUGE through <cmath> after Flang's headers
have undefined it. This breaks the RealValueImpl::HUGE definition and
calls, as well as the RealValue unit tests and their HUGE test name.
The glibc version I could reproduce the issue on was 2.26.
java/openjdk21: Version 21.0.13.0.3 more cert fixes
Update to latest upstream patch version to address more issues with the
eMudhra certificate incident.
See also: https://openjdk.org/emudhra
MFH: 2026Q4
Security: CVE 2026-114820
Security: JDK-8395690
Sponsored by: The FreeBSD Foundation
(cherry picked from commit a952ceac5d3c19984214bdbf9daaf49b97f9c25e)
