@genroc/eval-node 0.0.0-edge.00cdd64d
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/LICENSE +202 -0
- package/README.md +145 -0
- package/dist/eval.js +77 -0
- package/dist/import.js +361 -0
- package/dist/realm.js +108 -0
- package/dist/worker.js +286 -0
- package/eval.ts +114 -0
- package/import.ts +472 -0
- package/package.json +42 -0
- package/realm.ts +111 -0
- package/tsconfig.json +23 -0
- package/worker.ts +313 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,145 @@
|
|
|
1
|
+
# @genroc/eval-node
|
|
2
|
+
|
|
3
|
+
TypeScript script tasks for [genroc](https://genroc.org). The package provides two binaries:
|
|
4
|
+
|
|
5
|
+
* **`genroc-import`**: the bundler. `genctl` runs it on every `apply` and `generate` to turn
|
|
6
|
+
`$import: ./script.ts` into one typechecked, self-contained module string.
|
|
7
|
+
* **`genroc-eval-node`**: the worker. It claims script tasks from genroc's queue and runs each
|
|
8
|
+
one in a fresh worker thread.
|
|
9
|
+
|
|
10
|
+
Requires **Node 24+**. Full guide:
|
|
11
|
+
[TypeScript evaluation](https://genroc.org/guides/process-definition/typescript-evaluation/).
|
|
12
|
+
|
|
13
|
+
## Quick start
|
|
14
|
+
|
|
15
|
+
genctl init --eval-node
|
|
16
|
+
|
|
17
|
+
This scaffolds a project with everything set up: the package, a `.genroc` that registers the
|
|
18
|
+
resolver, a `tsconfig.json`, a reusable `script-node` child process, and a `compose.yaml` that
|
|
19
|
+
runs the worker.
|
|
20
|
+
|
|
21
|
+
## Adding it to an existing project
|
|
22
|
+
|
|
23
|
+
npm i -D @genroc/eval-node
|
|
24
|
+
|
|
25
|
+
Register the resolver in the `.genroc` beside your definitions:
|
|
26
|
+
|
|
27
|
+
```yaml
|
|
28
|
+
resolvers:
|
|
29
|
+
- name: import
|
|
30
|
+
phase: typed
|
|
31
|
+
ext: [.ts]
|
|
32
|
+
command: [npx, genroc-import]
|
|
33
|
+
types:
|
|
34
|
+
Input: task.action.input.input
|
|
35
|
+
Output: task.action.result
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
Then reference a script from a task. The simplest way is to spread the `script-node` child that
|
|
39
|
+
`genctl init --eval-node` generates:
|
|
40
|
+
|
|
41
|
+
```yaml
|
|
42
|
+
- id: greet
|
|
43
|
+
action:
|
|
44
|
+
type: child
|
|
45
|
+
<<: "$process: ./script-node.genroc.yaml"
|
|
46
|
+
input:
|
|
47
|
+
code: "$import: ./greet.ts"
|
|
48
|
+
input: { who: "$: input.who" }
|
|
49
|
+
result_schema:
|
|
50
|
+
type: object
|
|
51
|
+
properties: { greeting: { type: string } }
|
|
52
|
+
required: [greeting]
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
## Writing a script
|
|
56
|
+
|
|
57
|
+
A script is an ES module. Its default export receives `input`, and its return value becomes the
|
|
58
|
+
task result. The function may be async.
|
|
59
|
+
|
|
60
|
+
```ts
|
|
61
|
+
import type { Input, Output } from "./greet.genroc";
|
|
62
|
+
|
|
63
|
+
export default function (input: Input): Output {
|
|
64
|
+
return { greeting: `hello, ${input.who}` };
|
|
65
|
+
}
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
* `genctl generate` writes `greet.genroc.d.ts` beside the script. `Input` and `Output` come from
|
|
69
|
+
the definition, so a mismatch fails the typecheck.
|
|
70
|
+
* `genctl apply` typechecks and bundles. **A type error or a missing default export fails the
|
|
71
|
+
apply.**
|
|
72
|
+
* Imported files and npm packages are inlined into the bundle, so a stored definition never
|
|
73
|
+
depends on what is installed later. Node builtins (`node:fs`, …) stay as imports and resolve
|
|
74
|
+
on the worker.
|
|
75
|
+
* The generated config extends your nearest `tsconfig.json`. To use Node globals and
|
|
76
|
+
builtins, add `"types": ["node"]` to it.
|
|
77
|
+
|
|
78
|
+
## Running the worker
|
|
79
|
+
|
|
80
|
+
```sh
|
|
81
|
+
docker run -e GENROC_SERVER=http://host:8448 ghcr.io/genroc/eval-node:latest
|
|
82
|
+
# or
|
|
83
|
+
GENROC_SERVER=http://localhost:8448 npx genroc-eval-node
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
The worker connects to genroc, not the other way round, so it only needs outbound access.
|
|
87
|
+
|
|
88
|
+
| env | default | |
|
|
89
|
+
|---|---|---|
|
|
90
|
+
| `GENROC_SERVER` | `http://localhost:8448` | the genroc server |
|
|
91
|
+
| `GENROC_TOKEN` / `GENROC_TOKEN_FILE` | *(none)* | token, or a file holding it, when the server uses `--auth token` |
|
|
92
|
+
| `PROCESS` / `TASK` | `script-node` / `eval_node` | claim only this process / task id; the defaults are script-node's. Set `PROCESS` for a renamed copy, or `""` to drop a filter; **with both `""`, the worker claims every external task.** |
|
|
93
|
+
| `CONCURRENCY` | `4` | scripts run at once |
|
|
94
|
+
| `LEASE_MS` | `30000` | claim lease, renewed every third of it |
|
|
95
|
+
| `POLL_MS` | `250` | idle poll interval |
|
|
96
|
+
| `WORKER_ID` | `evaluator-<pid>` | the claim holder's name |
|
|
97
|
+
|
|
98
|
+
With auth enabled, create a token that has only the `worker` permission:
|
|
99
|
+
|
|
100
|
+
genctl token create --perms worker --label evaluator -q
|
|
101
|
+
|
|
102
|
+
If the token is rejected, the worker exits instead of retrying.
|
|
103
|
+
|
|
104
|
+
## Errors
|
|
105
|
+
|
|
106
|
+
When a script fails, the worker reports one of five error codes for your `on_error` rules to
|
|
107
|
+
match. Retrying does not help with any of them, because the same code fails the same way:
|
|
108
|
+
|
|
109
|
+
| code | when |
|
|
110
|
+
|---|---|
|
|
111
|
+
| `threw` | the script threw or rejected |
|
|
112
|
+
| `timeout` | it ran past the task's `timeout` (5000 ms when the task has none) |
|
|
113
|
+
| `compile_error` | the module does not parse, or has no default-export function |
|
|
114
|
+
| `nonserializable` | the return value cannot be serialized to JSON (a cycle, a `BigInt`) |
|
|
115
|
+
| `exited` | the script called `process.exit()` |
|
|
116
|
+
|
|
117
|
+
`error.data` is `{name, stack?}`. `name` is the error's class name, so throwing your own
|
|
118
|
+
`class LimitExceeded extends Error {}` tells your failures apart; setting `e.name` overrides it,
|
|
119
|
+
and a thrown non-`Error` is `Thrown`. The stack is mapped back to your source lines.
|
|
120
|
+
|
|
121
|
+
If the worker itself faults, it releases the task for another worker and reports no error.
|
|
122
|
+
|
|
123
|
+
The task's `timeout` is the script's budget, waiting in the queue included. The worker stops
|
|
124
|
+
the script just before it and answers `timeout`, so `external.timeout` means no worker answered
|
|
125
|
+
at all. With `script-node`, set it through the `timeout_ms` input.
|
|
126
|
+
|
|
127
|
+
## Limits
|
|
128
|
+
|
|
129
|
+
* **Not a sandbox.** Scripts have the worker host's filesystem, network and environment.
|
|
130
|
+
Run only code you trust.
|
|
131
|
+
* **Not deterministic.** On a retry the script runs again with the real clock and random
|
|
132
|
+
numbers. Pass any value that must stay stable through `input`.
|
|
133
|
+
* **Memory is not isolated.** A script that runs out of memory takes down the whole worker.
|
|
134
|
+
* **Run-once is opt-in.** If a worker dies mid-script, the task is claimed again and the script
|
|
135
|
+
runs again. Mark the task `only_once` if your script has side effects.
|
|
136
|
+
* **Inline code needs escaping.** When you write `code` directly in YAML rather than
|
|
137
|
+
`$import`, write `${` as `$${`, because genroc reads `${` as interpolation. Scripts in `.ts`
|
|
138
|
+
files need no escaping.
|
|
139
|
+
|
|
140
|
+
## Links
|
|
141
|
+
|
|
142
|
+
* [TypeScript evaluation guide](https://genroc.org/guides/process-definition/typescript-evaluation/)
|
|
143
|
+
* [External tasks and the queue](https://genroc.org/guides/process-definition/external-tasks/)
|
|
144
|
+
* [Error handling](https://genroc.org/guides/process-definition/error-handling/)
|
|
145
|
+
* [Source on GitHub](https://github.com/genroc/genroc/tree/main/eval-node)
|
package/dist/eval.js
ADDED
|
@@ -0,0 +1,77 @@
|
|
|
1
|
+
// Imports a script module in its own realm (a Worker per execution, realm.ts), calls its default
|
|
2
|
+
// export, and classifies every outcome (README.md). Only a killable thread bounds a synchronous
|
|
3
|
+
// busy loop, which is what makes the budget real. Knows nothing of genroc; worker.ts does.
|
|
4
|
+
import { Worker } from "node:worker_threads";
|
|
5
|
+
const DEFAULT_TIMEOUT_MS = 5_000;
|
|
6
|
+
// Resolved from THIS file's own extension: run from a checkout it is `.ts`, and from the
|
|
7
|
+
// published package `.js`, because Node will not strip types under node_modules.
|
|
8
|
+
const REALM_URL = new URL(import.meta.url.endsWith(".ts") ? "./realm.ts" : "./realm.js", import.meta.url);
|
|
9
|
+
/** Thrown, not returned: a realm that fails to start is the runner faulting, which worker.ts
|
|
10
|
+
* answers by releasing the claim. */
|
|
11
|
+
class RealmFault extends Error {
|
|
12
|
+
constructor(message) {
|
|
13
|
+
super(message);
|
|
14
|
+
this.name = "RealmFault";
|
|
15
|
+
}
|
|
16
|
+
}
|
|
17
|
+
/** Thrown when `signal` aborts: the answer is no longer wanted, so worker.ts releases rather
|
|
18
|
+
* than answers. Not a RealmFault: nothing is wrong. */
|
|
19
|
+
export class Cancelled extends Error {
|
|
20
|
+
constructor() {
|
|
21
|
+
super("cancelled");
|
|
22
|
+
this.name = "Cancelled";
|
|
23
|
+
}
|
|
24
|
+
}
|
|
25
|
+
export async function evaluate(req, signal) {
|
|
26
|
+
const budget = typeof req.timeout_ms === "number" ? req.timeout_ms : DEFAULT_TIMEOUT_MS;
|
|
27
|
+
const worker = new Worker(REALM_URL);
|
|
28
|
+
let timer;
|
|
29
|
+
let onAbort;
|
|
30
|
+
try {
|
|
31
|
+
return await new Promise((resolve, reject) => {
|
|
32
|
+
timer = setTimeout(() => resolve(timedOut(budget)), budget);
|
|
33
|
+
// The abort is wired to the same promise as the budget, so both settle through the one
|
|
34
|
+
// finally below -- which is what guarantees the thread is gone before either returns.
|
|
35
|
+
if (signal) {
|
|
36
|
+
if (signal.aborted)
|
|
37
|
+
reject(new Cancelled());
|
|
38
|
+
onAbort = () => reject(new Cancelled());
|
|
39
|
+
signal.addEventListener("abort", onAbort, { once: true });
|
|
40
|
+
}
|
|
41
|
+
worker.once("message", (reply) => resolve(reply));
|
|
42
|
+
// A script may `process.exit()`, which would otherwise look like a hang until the budget.
|
|
43
|
+
// Our own terminate() fires this too, after the promise has settled.
|
|
44
|
+
worker.once("exit", (code) => resolve(exited(code)));
|
|
45
|
+
worker.once("error", (err) => reject(new RealmFault(errorText(err))));
|
|
46
|
+
worker.postMessage({ code: req.code, input: req.input });
|
|
47
|
+
});
|
|
48
|
+
}
|
|
49
|
+
finally {
|
|
50
|
+
clearTimeout(timer);
|
|
51
|
+
if (signal && onAbort)
|
|
52
|
+
signal.removeEventListener("abort", onAbort);
|
|
53
|
+
// Awaited, and the whole point: on the timeout path a thread is still burning a core, and
|
|
54
|
+
// resolving before it is gone would report an evaluation the machine is still running.
|
|
55
|
+
await worker.terminate();
|
|
56
|
+
}
|
|
57
|
+
}
|
|
58
|
+
function timedOut(ms) {
|
|
59
|
+
return {
|
|
60
|
+
ok: false,
|
|
61
|
+
failure: { kind: "timeout", name: "TimeoutError", message: `script exceeded its ${ms}ms budget` },
|
|
62
|
+
};
|
|
63
|
+
}
|
|
64
|
+
function exited(code) {
|
|
65
|
+
return {
|
|
66
|
+
ok: false,
|
|
67
|
+
failure: {
|
|
68
|
+
kind: "exited",
|
|
69
|
+
name: "RealmExited",
|
|
70
|
+
message: `the script ended its own realm with code ${code} instead of returning`,
|
|
71
|
+
},
|
|
72
|
+
};
|
|
73
|
+
}
|
|
74
|
+
function errorText(e) {
|
|
75
|
+
const message = e?.message;
|
|
76
|
+
return typeof message === "string" && message !== "" ? message : "the evaluation realm failed to start";
|
|
77
|
+
}
|