@thermai/flightdeck-cli 0.1.0-pilot.6 → 0.1.0-pilot.7
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/README.md +56 -15
- package/dist/index.js +1706 -27
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -15,8 +15,8 @@ versioned GitHub Release workflow, not merely by merging a version change. The
|
|
|
15
15
|
installation command below follows the published `next` channel without
|
|
16
16
|
tracking an unpublished candidate version.
|
|
17
17
|
Proprietary terms in `LICENSE` permit redistribution of unchanged official
|
|
18
|
-
releases.
|
|
19
|
-
|
|
18
|
+
releases. Service access still requires an invitation, configured credits and
|
|
19
|
+
the agreed pilot limits; installing the package alone does not grant access.
|
|
20
20
|
|
|
21
21
|
**`0.1.0-pilot.3`** was published through GitHub Actions on 8 September 2026,
|
|
22
22
|
including complete log pagination and concise authentication errors. Its
|
|
@@ -35,10 +35,29 @@ storage ([#157](https://github.com/ThermAI-Group/thermai_flightdeck/issues/157))
|
|
|
35
35
|
and includes the merged GPU-recovery status display. Downloads validate the
|
|
36
36
|
accounting contract on Flightdeck's response, then fetch the authorized storage
|
|
37
37
|
object without forwarding the CLI credential. Anonymous Node 22 installation
|
|
38
|
-
and a live result download passed
|
|
38
|
+
and a live result download passed. Upgrade from
|
|
39
39
|
pilot.4 before downloading results. Future releases still require an approved
|
|
40
40
|
versioned GitHub Release; merging alone does not publish.
|
|
41
41
|
|
|
42
|
+
**`0.1.0-pilot.6`**, published on 21 September 2026, adds
|
|
43
|
+
offline-first logout and explicit suspension messages. Release CI, registry
|
|
44
|
+
integrity and anonymous Node 22 installation passed; grouped live acceptance
|
|
45
|
+
was confirmed by the operator on 24 September. These are historical pilot.6
|
|
46
|
+
results, not pilot.7 publication evidence. This update does not modify the
|
|
47
|
+
README inside the already-published immutable tarball.
|
|
48
|
+
|
|
49
|
+
**`0.1.0-pilot.7`** adds the read-only `flightdeck atc` terminal view (alias
|
|
50
|
+
`tui`), flight details/events/logs, name filtering and local sbatch-array tracking
|
|
51
|
+
from [PR #206](https://github.com/ThermAI-Group/thermai_flightdeck/pull/206).
|
|
52
|
+
It requires no backend refresh or new runtime dependencies. Publication still
|
|
53
|
+
requires the approved `cli-v0.1.0-pilot.7` GitHub prerelease and successful release
|
|
54
|
+
workflow; a version bump or merge alone does not publish. After publication, use
|
|
55
|
+
the generated `@next` command below, or pin `@thermai/flightdeck-cli@0.1.0-pilot.7`
|
|
56
|
+
for a reproducible pilot install. Confirm `flightdeck --version` reports
|
|
57
|
+
`0.1.0-pilot.7`. Existing saved credentials remain usable; no logout is required
|
|
58
|
+
just to upgrade. Downloads/cancellation inside ATC remain deferred to #205;
|
|
59
|
+
stale fallback-status indication is tracked in #207.
|
|
60
|
+
|
|
42
61
|
Members and organization administrators receive whole-credit balances,
|
|
43
62
|
estimates and actual customer charges, without provider-cost information.
|
|
44
63
|
Platform administrators retain their authorized monetary API fields. Credits
|
|
@@ -85,14 +104,14 @@ Logging out removes the saved credential; it does not delete the account or its
|
|
|
85
104
|
roles. A later login creates a new credential. Check the separate revocation
|
|
86
105
|
result: other copies may remain valid if server revocation was not confirmed.
|
|
87
106
|
|
|
88
|
-
|
|
107
|
+
Pilot.6 explains `account_suspended`, `membership_suspended`
|
|
89
108
|
and `organization_suspended` denials during device login and authenticated
|
|
90
109
|
commands. Contact your organization administrator; organization suspension may
|
|
91
110
|
need ThermAI support. These are access restrictions, not a missing local login
|
|
92
111
|
or a request for additional credential scopes. Other 403 responses retain
|
|
93
112
|
generic permissions guidance. Commands still exit nonzero and do not print
|
|
94
|
-
server-supplied messages or stack traces.
|
|
95
|
-
|
|
113
|
+
server-supplied messages or stack traces. Older pilot.5 installations need an
|
|
114
|
+
explicit upgrade to receive these messages.
|
|
96
115
|
|
|
97
116
|
## Pilot quick-start
|
|
98
117
|
|
|
@@ -100,7 +119,7 @@ Before live use, your ThermAI operator must provision your organization/account,
|
|
|
100
119
|
provide a single-use portal invitation, and approve your policy and credit.
|
|
101
120
|
Activate through the portal, then follow the installation/login commands above.
|
|
102
121
|
Confirm the expected account with `whoami` and the available credit with
|
|
103
|
-
`balance`.
|
|
122
|
+
`balance`. ThermAI will guide the first partner submission under the agreed limits.
|
|
104
123
|
|
|
105
124
|
For a **local-only** readiness check, save the following as `readiness.sbatch`
|
|
106
125
|
in a new empty directory. Run the dry run from that directory; no account,
|
|
@@ -138,7 +157,7 @@ the current directory. Never include credentials or private workstation files.
|
|
|
138
157
|
|
|
139
158
|
## Workload commands
|
|
140
159
|
|
|
141
|
-
After
|
|
160
|
+
After your account's policy/credit setup and agreed first-run approval:
|
|
142
161
|
|
|
143
162
|
```sh
|
|
144
163
|
flightdeck sbatch workload.sbatch
|
|
@@ -155,7 +174,8 @@ supports a subset of single-node Slurm directives, not an arbitrary HPC cluster.
|
|
|
155
174
|
Workload images must satisfy the Flightdeck runner contract.
|
|
156
175
|
|
|
157
176
|
An array prints a separate Flightdeck ID for each accepted task. Record them
|
|
158
|
-
all: inspect, download and cancel each flight individually
|
|
177
|
+
all: inspect, download and cancel each flight individually (`flightdeck atc
|
|
178
|
+
<job-id>` shows them together). Partial submission
|
|
159
179
|
can leave accepted flights running even if the command exits unsuccessfully;
|
|
160
180
|
do not blindly resubmit the whole array. Choose a fresh download directory for
|
|
161
181
|
each flight: downloads use filename basenames and refuse to overwrite existing
|
|
@@ -196,13 +216,35 @@ partial read. Older `0.1.0-pilot.2` installations do not contain this fix;
|
|
|
196
216
|
merging source alone neither replaces that immutable package nor publishes a
|
|
197
217
|
new version. Older non-following clients still need upgrading for full paging.
|
|
198
218
|
|
|
219
|
+
### Watching flights live
|
|
220
|
+
|
|
221
|
+
`flightdeck atc` (alias `flightdeck tui`) opens a read-only, full-screen view in
|
|
222
|
+
the current terminal. Arrow keys select, Enter shows a flight's details and
|
|
223
|
+
events, `l` opens its logs (scroll, `f` to follow), `r` refreshes, Esc goes back
|
|
224
|
+
and `q` quits. It never cancels, submits or downloads anything.
|
|
225
|
+
|
|
226
|
+
```sh
|
|
227
|
+
flightdeck atc # your recent flights (last 50)
|
|
228
|
+
flightdeck atc <flight-id> # one flight
|
|
229
|
+
flightdeck atc <job-id> # an sbatch array submitted from this machine
|
|
230
|
+
flightdeck atc --name 'molsim*' # flights whose name matches, among your last 200
|
|
231
|
+
flightdeck atc --demo # a simulated array; no account or credits needed
|
|
232
|
+
```
|
|
233
|
+
|
|
234
|
+
`flightdeck sbatch` records each array's flight IDs under
|
|
235
|
+
`~/.flightdeck/batches/` and ends with `Watch live: flightdeck atc <job-id>`;
|
|
236
|
+
that job ID is the one to pass. The record exists only on the machine that
|
|
237
|
+
submitted it (if it could not be written, sbatch says so; use `--name`). Name
|
|
238
|
+
patterns are case-sensitive. Leaving the view does not stop any job. In
|
|
239
|
+
scripts, keep using `status` and `logs`.
|
|
240
|
+
|
|
199
241
|
### Error handling and support
|
|
200
242
|
|
|
201
243
|
The CLI exits with status 1 on command failure. Expected authentication,
|
|
202
244
|
network and HTTP failures have concise diagnostics instead of a Node stack.
|
|
203
245
|
An already-configured login leaves the saved credential unchanged.
|
|
204
246
|
|
|
205
|
-
**
|
|
247
|
+
**Pilot.6 logout behavior (#143):** remove the local file first, then make
|
|
206
248
|
one best-effort server revocation request with a three-second deadline, including
|
|
207
249
|
the response body. Offline, suspended, failed or malformed API responses cannot
|
|
208
250
|
retain or restore the local login. Local success exits 0; a warning separately
|
|
@@ -213,11 +255,10 @@ Missing local login is a successful no-op; malformed config is removed without
|
|
|
213
255
|
trusting its contents for a request. No credential recovery/retry file is saved.
|
|
214
256
|
`logout --local` removes only the local copy and makes no network request.
|
|
215
257
|
|
|
216
|
-
|
|
217
|
-
|
|
218
|
-
|
|
219
|
-
|
|
220
|
-
suspended. These changes do not permit ordinary access under suspension.
|
|
258
|
+
Older pilot.5 does not include this change; use `flightdeck logout --local`
|
|
259
|
+
as a local-removal workaround before upgrading. It does not revoke remote
|
|
260
|
+
access. The current production backend permits narrowly authenticated
|
|
261
|
+
self-revocation under suspension; ordinary access remains blocked.
|
|
221
262
|
|
|
222
263
|
For unexpected faults, `flightdeck --debug <command>` adds allowlisted error
|
|
223
264
|
types/codes and bundled CLI line locations, not raw stacks or error bodies.
|