@conarium-ai/core 0.1.1 → 0.1.2
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 +21 -1
- package/bin/conarium-doctor.mjs +13 -2
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,7 +2,27 @@
|
|
|
2
2
|
|
|
3
3
|
## Unreleased
|
|
4
4
|
|
|
5
|
-
Nothing yet — 0.1.
|
|
5
|
+
Nothing yet — 0.1.2 is the current cut.
|
|
6
|
+
|
|
7
|
+
## 0.1.2 — 2026-08-13
|
|
8
|
+
|
|
9
|
+
Patch. `conarium-doctor` aborted instead of exiting when a connector was
|
|
10
|
+
unreachable.
|
|
11
|
+
|
|
12
|
+
### Fixed
|
|
13
|
+
|
|
14
|
+
- **The documented exit contract (`0` clean / `1` problems / `2` could not run)
|
|
15
|
+
was not honoured on the network path.** The TCP probe resolved on the socket's
|
|
16
|
+
`error` event and the process then exited while the handle was still closing;
|
|
17
|
+
on Windows libuv asserted (`UV_HANDLE_CLOSING`) and the run ended with **127**
|
|
18
|
+
— a code this tool does not define, printed under an assertion trace. Anything
|
|
19
|
+
gating a deployment on the exit status could not read it. Reproduced 3/3 with
|
|
20
|
+
a refused connection; `--no-net` was never affected.
|
|
21
|
+
|
|
22
|
+
The probe now resolves after the socket has actually closed, and the tool sets
|
|
23
|
+
`process.exitCode` instead of calling `process.exit()`, so the loop drains on
|
|
24
|
+
its own. A regression test pins it: an unreachable connector must exit `1` and
|
|
25
|
+
the output must not contain an assertion.
|
|
6
26
|
|
|
7
27
|
## 0.1.1 — 2026-08-13
|
|
8
28
|
|
package/bin/conarium-doctor.mjs
CHANGED
|
@@ -86,11 +86,19 @@ function tcpProbe(host, port, timeoutMs = 4000) {
|
|
|
86
86
|
return new Promise((done) => {
|
|
87
87
|
const sock = new net.Socket()
|
|
88
88
|
let settled = false
|
|
89
|
+
// Resolve only once the socket is fully closed. Resolving on the error
|
|
90
|
+
// event and exiting immediately used to abort the process on Windows —
|
|
91
|
+
// libuv asserts when the handle is still closing (UV_HANDLE_CLOSING) —
|
|
92
|
+
// and the run ended with 127 instead of the documented 0/1/2.
|
|
89
93
|
const finish = (r) => {
|
|
90
94
|
if (settled) return
|
|
91
95
|
settled = true
|
|
96
|
+
if (sock.destroyed) {
|
|
97
|
+
done(r)
|
|
98
|
+
return
|
|
99
|
+
}
|
|
100
|
+
sock.once('close', () => done(r))
|
|
92
101
|
sock.destroy()
|
|
93
|
-
done(r)
|
|
94
102
|
}
|
|
95
103
|
sock.setTimeout(timeoutMs)
|
|
96
104
|
sock.once('connect', () => finish({ reachable: true }))
|
|
@@ -477,4 +485,7 @@ console.log(`${results.length} checks · ${fails} failed · ${warns} warning(s)`
|
|
|
477
485
|
if (fails === 0 && warns === 0) console.log('This install is ready.')
|
|
478
486
|
if (fails > 0) console.log('Fix the FAIL lines above; the gateway will not govern correctly until you do.')
|
|
479
487
|
console.log('')
|
|
480
|
-
process.exit(
|
|
488
|
+
// Set the code and let the loop drain. process.exit() here raced the closing
|
|
489
|
+
// probe sockets and aborted the process on Windows, which surfaced as 127 —
|
|
490
|
+
// a code this tool does not define, and one a deployment gate cannot read.
|
|
491
|
+
process.exitCode = fails > 0 ? 1 : 0
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@conarium-ai/core",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2",
|
|
4
4
|
"//files": "Pakete NE gireceginin izin listesi. Liste olmadan npm her seyi gonderiyordu: 296 dosya / 1.5 MB — CI workflowlari, gitleaks ayari, 137 KB pazarlama gorseli, sitenin api/chat.js dosyasi. Bir bankanin guvenlik ekibi tarball'i acip bunlari gorur. scripts/ BILEREK var: conarium-reconcile calisirken scripts/pg-snapshot.sql'e atif yapiyor, olmazsa kullanici destek maili yazar.",
|
|
5
5
|
"files": [
|
|
6
6
|
"dist",
|