@sjawhar/pi-legion 19.35.0 → 19.37.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/legion.js CHANGED
@@ -29916,7 +29916,7 @@ import { logger as logger3 } from "@oh-my-pi/pi-utils";
29916
29916
  // package.json
29917
29917
  var package_default = {
29918
29918
  name: "@sjawhar/pi-legion",
29919
- version: "19.35.0",
29919
+ version: "19.37.0",
29920
29920
  license: "Apache-2.0",
29921
29921
  type: "module",
29922
29922
  omp: {
@@ -29928,7 +29928,7 @@ var package_default = {
29928
29928
  ]
29929
29929
  },
29930
29930
  legion: {
29931
- daemonApiVersion: 146
29931
+ daemonApiVersion: 151
29932
29932
  },
29933
29933
  repository: {
29934
29934
  type: "git",
@@ -12,9 +12,12 @@ An issue pod runs no heavy build and no whole test suite. The pod's six roles sh
12
12
  limit. Near that limit the launcher's memory guard, where the deployment runs it (it is on by
13
13
  default), stops, with SIGKILL, the largest process that is neither Legion's own nor an agent's own,
14
14
  which in practice is a command an agent ran: a build, a test binary, a Python or JavaScript kernel.
15
- It then tells that process's role why, in a message on the role's topic. The command fails and the
16
- turn goes on. A command that fills the memory faster than the guard can stop it still takes the pod
17
- past its limit, and that ends every role's turn, not only yours.
15
+ It then tells that process's role why, in a message on the role's topic. In a pod that runs in a
16
+ microVM, the pod's own kernel stops such a command in place of the guard where each of the pod's
17
+ requests equals its limit, and the role is told the same way; in a pod that requests less, it can
18
+ stop an agent instead. The command fails and the turn goes on. In a gVisor pod, a command that
19
+ fills the memory faster than the guard can stop it still takes the pod past its limit, and that
20
+ ends every role's turn, not only yours.
18
21
 
19
22
  In the pod you compile the packages your change touches, run by name the tests you added or
20
23
  changed (`go test -run '<TestName>' ./internal/<package>/`, or `bun test` with their files), build
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/pi-legion",
3
- "version": "19.35.0",
3
+ "version": "19.37.0",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "omp": {
@@ -12,7 +12,7 @@
12
12
  ]
13
13
  },
14
14
  "legion": {
15
- "daemonApiVersion": 146
15
+ "daemonApiVersion": 151
16
16
  },
17
17
  "repository": {
18
18
  "type": "git",