@sjawhar/pi-legion 19.27.1 → 19.28.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
@@ -29195,6 +29195,7 @@ function truncateUtf8(text, max) {
29195
29195
  }
29196
29196
  return text.slice(0, end);
29197
29197
  }
29198
+ var LABELED_WORD = String.raw`(?:[^ "'\\)\]}>,;:.!?]|[\\)\]}>,;:.!?]+[^ "'\\)\]}>,;:.!?])+`;
29198
29199
  var CREDENTIAL_RULES = [
29199
29200
  [/(?<![a-z0-9+.-])([0-9+.-]*[a-z][a-z0-9+.-]*:\/\/)[^ /?#]+@/gi, "$1***@"],
29200
29201
  [
@@ -29210,17 +29211,14 @@ var CREDENTIAL_RULES = [
29210
29211
  "$1$2$3$4***"
29211
29212
  ],
29212
29213
  [
29213
- new RegExp(String.raw`((?:api-key|application-key|ocp-apim-subscription-key|x-subscription-token)\\?["']?[ \ufffe\uffff]*[:=][ \ufffe\uffff]*\\?["']?)(?:[A-Za-z0-9._~+/=*-]|${HELD_SEQUENCE})+`, "gi"),
29214
+ new RegExp(String.raw`((?:api-key|application-key|ocp-apim-subscription-key|x-subscription-token)\\?["']?[ \ufffe\uffff]*[:=][ \ufffe\uffff]*\\?["']?)${LABELED_WORD}`, "gi"),
29214
29215
  "$1***"
29215
29216
  ],
29216
29217
  [
29217
29218
  /(\\?["'](?:api_key|access_token)\\?["'][ \ufffe\uffff]*:[ \ufffe\uffff]*\\?["'])[^"'\\]+/gi,
29218
29219
  "$1***"
29219
29220
  ],
29220
- [
29221
- new RegExp(String.raw`\b(bearer[ \ufffe\uffff]+)(?:[A-Za-z0-9._~+/=*-]|${HELD_SEQUENCE})+`, "gi"),
29222
- "$1***"
29223
- ],
29221
+ [new RegExp(String.raw`\b(bearer[ \ufffe\uffff]+)${LABELED_WORD}`, "gi"), "$1***"],
29224
29222
  [
29225
29223
  new RegExp(String.raw`\b(gh[pousr]_|github_pat_)(?:[A-Za-z0-9._-]|${HELD_SEQUENCE}){20,}`, "g"),
29226
29224
  "$1***"
@@ -29722,7 +29720,7 @@ import { logger as logger3 } from "@oh-my-pi/pi-utils";
29722
29720
  // package.json
29723
29721
  var package_default = {
29724
29722
  name: "@sjawhar/pi-legion",
29725
- version: "19.27.1",
29723
+ version: "19.28.0",
29726
29724
  license: "Apache-2.0",
29727
29725
  type: "module",
29728
29726
  omp: {
@@ -29734,7 +29732,7 @@ var package_default = {
29734
29732
  ]
29735
29733
  },
29736
29734
  legion: {
29737
- daemonApiVersion: 141
29735
+ daemonApiVersion: 144
29738
29736
  },
29739
29737
  repository: {
29740
29738
  type: "git",
@@ -9,7 +9,12 @@ binary; and when a test fails in your pod. Every path it cites is in cybermonkla
9
9
  ## What runs in your pod, and what runs on the pull request
10
10
 
11
11
  An issue pod runs no heavy build and no whole test suite. The pod's six roles share one memory
12
- limit, and one command that fills it ends every role's turn, not only yours.
12
+ limit. Near that limit the launcher's memory guard, where the deployment runs it (it is on by
13
+ default), stops, with SIGKILL, the largest process that is neither Legion's own nor an agent's own,
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.
13
18
 
14
19
  In the pod you compile and test the packages your change touches, build the program a check of
15
20
  your issue drives (`go build ./cmd/legion`), vet the module you changed (`go vet -tags e2e ./...`,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/pi-legion",
3
- "version": "19.27.1",
3
+ "version": "19.28.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": 141
15
+ "daemonApiVersion": 144
16
16
  },
17
17
  "repository": {
18
18
  "type": "git",