On Linux, a tool already inside another tool's memory group is reported as nested instead of double-limited.
tengu_tool_memory_cgroup Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.239: on
Read once, for one account on one subscription tier, against v2.1.239. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
On Linux, setting up the memory limit for a tool now notices when the process is already inside another tool's memory group, clears the directory, logs it and reports the setup as nested rather than trying to nest a second limit.
- Setup is still guarded by
tengu_tool_memory_cgroupwhen no explicit limit has been set. - Whether the system uses cgroup v2 is now recorded on the setup state.
tool cgroup: covered by an outer tool cgroup
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
macOS sandbox re-applies read and delete denials inside writable folders
Both mention sandbox
-
v2.1.236
Sandbox proxy no longer writes to sockets that have gone away
Both mention sandbox
-
v2.1.236
IPv6 hosts through the proxy
Both mention sandbox