@foggy-projects/deepseek-harness-plugin 0.4.5-rc.2 → 0.4.5-rc.3
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 +8 -8
- package/docs/RELEASE-CANDIDATE-0.4.5-DSH-0.2.2-RC.3.md +36 -0
- package/experience/linux/prepare.sh +1 -1
- package/lib/network-errors.js +9 -2
- package/package.json +3 -2
- package/skills/foggy-deepseek-onboarding/assets/versions.json +1 -1
- package/skills/foggy-deepseek-onboarding/scripts/onboarding.py +17 -1
package/README.md
CHANGED
|
@@ -10,7 +10,7 @@ when the plugin package is upgraded.
|
|
|
10
10
|
The Foggy settings tab includes a **Tutorial** entry linking to
|
|
11
11
|
[Foggy AI Data tutorials](https://ai-data.qlfloor.com/).
|
|
12
12
|
|
|
13
|
-
The `0.4.5-rc.
|
|
13
|
+
The `0.4.5-rc.3` compatibility candidate targets DeepSeek Harness `0.2.2-rc.3`
|
|
14
14
|
and requires a system Node.js `>=24.9.0`. Foggy's Java Launcher uses a system
|
|
15
15
|
Java 17+. Foggy manages its own pinned Python 3.12 runtime
|
|
16
16
|
inside the per-user component directory; it does not require a system Python,
|
|
@@ -20,7 +20,7 @@ modify `PATH`, or register Python globally. Advanced users may explicitly set
|
|
|
20
20
|
## Local release-candidate installation
|
|
21
21
|
|
|
22
22
|
```powershell
|
|
23
|
-
dsh plugin --profile web add --workspace-root ./foggy-projects-deepseek-harness-plugin-0.4.5-rc.
|
|
23
|
+
dsh plugin --profile web add --workspace-root ./foggy-projects-deepseek-harness-plugin-0.4.5-rc.3.tgz
|
|
24
24
|
```
|
|
25
25
|
|
|
26
26
|
Restart `dsh web`, use the browser it opens (or the complete printed URL,
|
|
@@ -31,7 +31,7 @@ After the version is available on npm, install the exact DSH 0.2.2-rc.3
|
|
|
31
31
|
compatibility candidate so the stable `beta` channel is not changed:
|
|
32
32
|
|
|
33
33
|
```powershell
|
|
34
|
-
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.5-rc.
|
|
34
|
+
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.5-rc.3
|
|
35
35
|
```
|
|
36
36
|
|
|
37
37
|
DSH 0.2.2 candidates use the `dsh022` npm dist-tag. Check that the tag resolves
|
|
@@ -197,13 +197,13 @@ rollback plan.
|
|
|
197
197
|
See [`docs/PUBLIC-BETA-READINESS.md`](./docs/PUBLIC-BETA-READINESS.md) for the
|
|
198
198
|
tested public Beta scope, release gates, and stable-release blockers.
|
|
199
199
|
Initialization downloads the pinned private Python archive before the CLI,
|
|
200
|
-
Launcher, and Skills.
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
|
|
200
|
+
Launcher, and Skills. Download diagnostics show the sanitized URL, available
|
|
201
|
+
failing-host and network-code details, and specific guidance for HTTPS
|
|
202
|
+
certificate verification failures. They distinguish certificate trust errors
|
|
203
|
+
from blocked connections and HTTP error responses.
|
|
204
204
|
|
|
205
205
|
The current DSH 0.2.2-rc.3 compatibility candidate is documented in
|
|
206
|
-
[`docs/RELEASE-CANDIDATE-0.4.5-DSH-0.2.2-RC.
|
|
206
|
+
[`docs/RELEASE-CANDIDATE-0.4.5-DSH-0.2.2-RC.3.md`](./docs/RELEASE-CANDIDATE-0.4.5-DSH-0.2.2-RC.3.md).
|
|
207
207
|
The previous DSH 0.2.1-rc.2 compatibility candidate is documented in
|
|
208
208
|
[`docs/RELEASE-CANDIDATE-0.4.4-DSH-0.2.1-RC.1.md`](./docs/RELEASE-CANDIDATE-0.4.4-DSH-0.2.1-RC.1.md).
|
|
209
209
|
The previous DSH 0.1.7-rc.2 candidate is documented in
|
|
@@ -0,0 +1,36 @@
|
|
|
1
|
+
# Foggy DeepSeek Harness plugin 0.4.5-rc.3
|
|
2
|
+
|
|
3
|
+
This candidate keeps the DeepSeek Harness `0.2.2-rc.3` compatibility target and
|
|
4
|
+
clarifies TLS certificate errors reported during component downloads.
|
|
5
|
+
|
|
6
|
+
An `SSLCertVerificationError` is now described as a certificate trust failure,
|
|
7
|
+
not a generic network connection failure. The message identifies the download
|
|
8
|
+
URL and advises checking the system clock, HTTPS inspection by proxies or
|
|
9
|
+
security software, and the trusted CA chain. For Python downloads it explains
|
|
10
|
+
that `SSL_CERT_FILE` can point to an organization-provided PEM certificate; for
|
|
11
|
+
Node.js downloads it mentions `NODE_EXTRA_CA_CERTS`. It explicitly says that
|
|
12
|
+
changing networks or using a VPN only helps when it avoids the problematic TLS
|
|
13
|
+
inspection, and that certificate verification should not be disabled.
|
|
14
|
+
|
|
15
|
+
Other DNS, timeout, and connection errors continue to show the sanitized
|
|
16
|
+
request URL, available failing host, and network error code. HTTP responses
|
|
17
|
+
continue to display their status separately.
|
|
18
|
+
|
|
19
|
+
The compatibility target remains DeepSeek Harness `0.2.2-rc.3`, with system
|
|
20
|
+
Node.js `>=24.9.0`, Java 17+, managed Python `3.12.13`, Launcher `0.1.46`, CLI
|
|
21
|
+
`0.1.25`, and Foggy Skills `0.1.18`.
|
|
22
|
+
|
|
23
|
+
Install the exact candidate in a clean Harness profile:
|
|
24
|
+
|
|
25
|
+
```powershell
|
|
26
|
+
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.5-rc.3
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
For the DSH `0.2.2-rc.3` channel, `@dsh022` points to this candidate after
|
|
30
|
+
publication.
|
|
31
|
+
|
|
32
|
+
## Verification
|
|
33
|
+
|
|
34
|
+
This document records the source change only. Do not treat the candidate as
|
|
35
|
+
accepted until package and compatibility checks are run on the target Harness
|
|
36
|
+
version and a clean Windows initialization confirms the diagnostic text.
|
package/lib/network-errors.js
CHANGED
|
@@ -21,12 +21,16 @@ function networkDetails(error) {
|
|
|
21
21
|
let current = error
|
|
22
22
|
let code = null
|
|
23
23
|
let host = null
|
|
24
|
+
let certificateVerification = false
|
|
24
25
|
while (current && typeof current === 'object' && !seen.has(current)) {
|
|
25
26
|
seen.add(current)
|
|
26
27
|
const candidateCode = current.code ?? current.errno
|
|
27
28
|
if (!code && (typeof candidateCode === 'string' || typeof candidateCode === 'number')) {
|
|
28
29
|
code = String(candidateCode).slice(0, 80)
|
|
29
30
|
}
|
|
31
|
+
if (/SSLCertVerificationError|CERTIFICATE_VERIFY|CERT_HAS_EXPIRED|SELF_SIGNED_CERT|UNABLE_TO_VERIFY|ERR_TLS_CERT_ALTNAME_INVALID|self[- ]signed|certificate.*(?:verify|chain|expired|authority|altname)|unable to verify/i.test(`${current.name ?? ''} ${current.code ?? ''} ${current.message ?? ''}`)) {
|
|
32
|
+
certificateVerification = true
|
|
33
|
+
}
|
|
30
34
|
if (!host) host = parsedHost(current.hostname) ?? parsedHost(current.host)
|
|
31
35
|
if (!host && typeof current.message === 'string') {
|
|
32
36
|
host = current.message.match(/(?:ENOTFOUND|getaddrinfo|name or service not known)\s+([a-z0-9.-]+\.[a-z]{2,})/i)?.[1] ?? null
|
|
@@ -34,17 +38,20 @@ function networkDetails(error) {
|
|
|
34
38
|
current = current.cause
|
|
35
39
|
}
|
|
36
40
|
if (!code && error?.name === 'AbortError') code = 'TIMEOUT'
|
|
37
|
-
return { code: code ?? 'FETCH_FAILED', host }
|
|
41
|
+
return { code: code ?? 'FETCH_FAILED', host, certificateVerification }
|
|
38
42
|
}
|
|
39
43
|
|
|
40
44
|
export function networkFailureMessage(action, value, error) {
|
|
41
45
|
const target = safeNetworkUrl(value)
|
|
42
46
|
const targetHost = parsedHost(target)
|
|
43
|
-
const { code, host } = networkDetails(error)
|
|
47
|
+
const { code, host, certificateVerification } = networkDetails(error)
|
|
44
48
|
const failedHost = host ?? targetHost ?? 'the requested host'
|
|
45
49
|
const redirect = host && targetHost && host !== targetHost
|
|
46
50
|
? `检测到连接失败主机:${host}。`
|
|
47
51
|
: ''
|
|
52
|
+
if (certificateVerification) {
|
|
53
|
+
return `${action}失败。请求地址:${target}。${redirect}HTTPS 证书校验失败(${code}):客户端收到了证书,但无法验证证书链。请检查系统日期/时间,以及代理或杀毒软件是否在检查 HTTPS;需要时将可信根证书正确加入系统证书库,Node.js 也可用 NODE_EXTRA_CA_CERTS 指定 PEM 证书。只有切换网络/VPN 能避开错误的 HTTPS 检查时才有帮助;不要关闭证书校验。`
|
|
54
|
+
}
|
|
48
55
|
return `${action}失败。请求地址:${target}。${redirect}网络错误码:${code}。请检查网络、代理和防火墙是否允许访问 ${failedHost};如果当前网络限制 GitHub,可能需要配置代理/VPN 或切换到可访问该域名的网络。`
|
|
49
56
|
}
|
|
50
57
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@foggy-projects/deepseek-harness-plugin",
|
|
3
|
-
"version": "0.4.5-rc.
|
|
3
|
+
"version": "0.4.5-rc.3",
|
|
4
4
|
"description": "Foggy Java data analysis engine integration for DeepSeek Harness",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"deepseek-harness",
|
|
@@ -52,7 +52,8 @@
|
|
|
52
52
|
"docs/RELEASE-CANDIDATE-0.4.3-DSH-0.2.0-RC.1.md",
|
|
53
53
|
"docs/RELEASE-CANDIDATE-0.4.4-DSH-0.2.1-RC.1.md",
|
|
54
54
|
"docs/RELEASE-CANDIDATE-0.4.5-DSH-0.2.2-RC.1.md",
|
|
55
|
-
"docs/RELEASE-CANDIDATE-0.4.5-DSH-0.2.2-RC.2.md"
|
|
55
|
+
"docs/RELEASE-CANDIDATE-0.4.5-DSH-0.2.2-RC.2.md",
|
|
56
|
+
"docs/RELEASE-CANDIDATE-0.4.5-DSH-0.2.2-RC.3.md"
|
|
56
57
|
],
|
|
57
58
|
"license": "Apache-2.0",
|
|
58
59
|
"engines": {
|
|
@@ -15,6 +15,7 @@ import re
|
|
|
15
15
|
import shutil
|
|
16
16
|
import signal
|
|
17
17
|
import socket
|
|
18
|
+
import ssl
|
|
18
19
|
import subprocess
|
|
19
20
|
import sys
|
|
20
21
|
import tempfile
|
|
@@ -534,6 +535,21 @@ def download_network_error(asset: dict, url: str, error: BaseException) -> str:
|
|
|
534
535
|
error_kind += f" ({code})"
|
|
535
536
|
redirect = f" 实际失败地址(跳转后):{failed_url}。" if failed_url != original_url else ""
|
|
536
537
|
host = urlsplit(failed_url).hostname or urlsplit(original_url).hostname or "目标域名"
|
|
538
|
+
certificate_failure = (
|
|
539
|
+
isinstance(reason, ssl.SSLCertVerificationError)
|
|
540
|
+
or getattr(reason, "verify_code", None) is not None
|
|
541
|
+
or "CERTIFICATE_VERIFY_FAILED" in str(reason).upper()
|
|
542
|
+
)
|
|
543
|
+
if certificate_failure:
|
|
544
|
+
verify_code = getattr(reason, "verify_code", None)
|
|
545
|
+
verify_detail = f"(verify code {verify_code})" if verify_code is not None else ""
|
|
546
|
+
return (
|
|
547
|
+
f"下载组件文件 {asset.get('file', 'asset')} 失败:HTTPS 证书校验失败。"
|
|
548
|
+
f"下载地址:{original_url}。{redirect}错误:SSLCertVerificationError{verify_detail}。"
|
|
549
|
+
f"客户端收到了 {host} 提供的证书,但无法验证其证书链。这通常与 DNS 或网络不通不同。"
|
|
550
|
+
"请检查系统日期/时间,以及代理或杀毒软件是否检查 HTTPS;必要时将可信根证书加入 Windows 受信任根证书,"
|
|
551
|
+
"或设置 SSL_CERT_FILE 指向该 CA 的 PEM 文件。代理/VPN 只有在能避开有问题的 HTTPS 检查时才可能有帮助;请勿关闭证书校验。"
|
|
552
|
+
)
|
|
537
553
|
return (
|
|
538
554
|
f"下载组件文件 {asset.get('file', 'asset')} 失败,无法连接下载服务。"
|
|
539
555
|
f"下载地址:{original_url}。{redirect}连接错误:{error_kind}。"
|
|
@@ -605,7 +621,7 @@ def materialize(
|
|
|
605
621
|
urllib.request.urlretrieve(asset["url"], temporary, reporthook=reporthook)
|
|
606
622
|
except urllib.error.HTTPError as exc:
|
|
607
623
|
raise OnboardingError(download_http_error(asset, asset["url"], exc)) from exc
|
|
608
|
-
except (urllib.error.URLError, TimeoutError, ConnectionError, http.client.HTTPException) as exc:
|
|
624
|
+
except (urllib.error.URLError, ssl.SSLError, TimeoutError, ConnectionError, http.client.HTTPException) as exc:
|
|
609
625
|
raise OnboardingError(download_network_error(asset, asset["url"], exc)) from exc
|
|
610
626
|
source = "network"
|
|
611
627
|
verify_asset(temporary, asset["sha256"])
|