@deepdockai/cli 1.0.17 → 1.0.18
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/CHANGELOG.md +4 -0
- package/dist/deepdock.js +2 -1
- package/package.json +1 -1
- package/skill/references/errors.md +2 -0
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.0.18
|
|
4
|
+
|
|
5
|
+
- A read or write on a record the customer's system restricts (for example a locked chart) answers `422 record_restricted`: a read returns no data instead of an empty answer, and a write writes nothing. The skill's error reference lists it, and the CLI exits with 2 for it.
|
|
6
|
+
|
|
3
7
|
## 1.0.17
|
|
4
8
|
|
|
5
9
|
- A device whose identity is held by two PCs (a copied PC or VM snapshot) answers every call with `409 device_connected_twice`; nothing runs and the `Idempotency-Key` is free. The skill's error reference lists it, and the CLI exits with 2 for it.
|
package/dist/deepdock.js
CHANGED
|
@@ -10873,6 +10873,7 @@ var EXIT_CODES = {
|
|
|
10873
10873
|
unknown_provider: 2,
|
|
10874
10874
|
record_locked: 2,
|
|
10875
10875
|
record_not_editable: 2,
|
|
10876
|
+
record_restricted: 2,
|
|
10876
10877
|
payload_too_large: 2,
|
|
10877
10878
|
device_offline: 3,
|
|
10878
10879
|
device_syncing: 3,
|
|
@@ -11430,7 +11431,7 @@ import { spawn } from "node:child_process";
|
|
|
11430
11431
|
import { homedir, hostname } from "node:os";
|
|
11431
11432
|
|
|
11432
11433
|
// src/version.ts
|
|
11433
|
-
var VERSION = "1.0.
|
|
11434
|
+
var VERSION = "1.0.18";
|
|
11434
11435
|
|
|
11435
11436
|
// src/runtime.ts
|
|
11436
11437
|
var DEFAULT_BASE_URL = "https://api.deepdock.ai";
|
package/package.json
CHANGED
|
@@ -50,6 +50,7 @@ dashboard-only.
|
|
|
50
50
|
| `no_open_case` | 422 | the customer has no open case and the action never opens one. Nothing was written | no; open a case in the system, or name one with `caseId` | "open a case first" |
|
|
51
51
|
| `record_locked` | 422 | the customer's system locks the record the write would change (for example one already billed on a case). Nothing was written | no | "this record is locked in the customer's system" |
|
|
52
52
|
| `record_not_editable` | 422 | the record is not locked but is stored in a form this action cannot edit (for example a note it cannot add to without rewriting it). Nothing was written | no | "this record cannot be edited through Deepdock" |
|
|
53
|
+
| `record_restricted` | 422 | the customer's system restricts access to the record (for example a locked chart): a read returned no data, so an empty answer would be wrong, and a write wrote nothing | no; the practice lifts the restriction in its system | "access to this record is restricted in the customer's system" |
|
|
53
54
|
| Other action-specific refusals | 422 | the action's OpenAPI description names each such code and when it fires. Nothing was written | no; fix the reference or input | the missing precondition in the user's words |
|
|
54
55
|
|
|
55
56
|
## Device and system availability
|
|
@@ -99,6 +100,7 @@ const REACTION: Record<string, Reaction> = {
|
|
|
99
100
|
unknown_provider: 'fix-input',
|
|
100
101
|
record_locked: 'stop',
|
|
101
102
|
record_not_editable: 'stop',
|
|
103
|
+
record_restricted: 'stop',
|
|
102
104
|
payload_too_large: 'fix-code',
|
|
103
105
|
access_outdated: 'wait-setup',
|
|
104
106
|
access_missing: 'wait-setup',
|