runtime —— 产品本体(组合根共享层)
发行名 gherkai-runtime / import 名 gherkai_runtime(ADR 0037 决策 2a「三名分离」;发行名 gherkai 归 CLI 包)。
cli / lambdas / 未来 WebUI 的共同地基(ADR 0016「演进」节):这里知道产品的一切(有哪两个引擎、
云资源怎么命名、run 怎么装配推进),各入口只是它的皮。依赖方向:皮 → gherkai_runtime → gherkai_core(窄腰红线不变)。
compose.py—— 组合根/引擎注册表:resolve_worker_cmd(worker 四级定位链,ADR 0037 决策 3——env 覆写 > 同 venv-m> PATH bin > uvx/npx 兜底;全 miss 抛WorkerNotFoundError交调用点分叉)/build_engines/build_fargate_engines(cloud 档,吃显式 task-def revision ARN 的映射,ADR 0038)/build_local_stores/build_cloud_stores/resolve_cloud_target(云资源终名 + region/profile 一处解析)/ 版本 skew 三态 (check_backend_skew,ADR 0037 决策 7)/ worker variant 解析(resolve_worker_variant供提交侧 preflight、resolve_default_worker_task_defs供宿主兼容路径,ADR 0038)/ 确定性能力自述(query_deterministic/match_deterministic,ADR 0036)/ grace 推导 / run_id·时钟detached.py—— local 无状态跑批宿主(ADR 0034):SubprocessLauncher + per-run reconcile loopnames.py—— 资源命名真源(零依赖;deploy_aws/gherkai_deploy_aws/names.py直接 re-export,消复刻): 资源名 / SSM 路径 / worker 镜像 tag(image_tag是 PEP 440 → docker tag 字符集的唯一归一化与校验点,ADR 0038)tunnel.py—— 隧道 provider(ADR 0035):--expose-local起/拆 ngrok(basic-auth 凭据每 run 一换、按 pid 跨进程收尾)+ job 文本里的 origin 替换(map_origin_in_jobs,worker/core 对隧道无知)tunnel_host.py—— 隧道宿主编排(ADR 0035 决策 3):起隧道 + 映射 definition + 恒注入的额外请求头; cloud submit 守护进程的轮询循环与其 TTL 算法(按 definition 算,不是拍常数)
uv sync # 仓库根:一次装齐五个 workspace 成员 core/runtime/cli/engines/novaact/deploy_aws(editable)
cd runtime && uv run pytest -q # 只跑本包单测(根目录 `uv run pytest` 跑三成员全部)
Metadata
Release files for gherkai-runtime 1.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| gherkai_runtime-1.4.0.tar.gz | 82.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gherkai_runtime-1.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 135.2 kB
Release files / gherkai_runtime-1.4.0.tar.gz
| Download URL | gherkai_runtime-1.4.0.tar.gz |
|---|---|
| Size | 82.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
92c520974c4dd3f8183f33ce5fa1af9d7bf4cd5ea31e4ea9e7e7fc2941199369
|
|
BLAKE2b-256 checksum How to use checksums |
f7b52fca2420d01c8f27859685f46c56b44434681e56b377bbb8f55c7f1702e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.3 {"installer":{"name":"uv","version":"0.12.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logRelease files / gherkai_runtime-1.4.0-py3-none-any.whl
| Download URL | gherkai_runtime-1.4.0-py3-none-any.whl |
|---|---|
| Size | 53.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
007557ddc8722636144039ac56df2ea8a1e3b3f7e1f7f2dc2f8439a1d4b9ce8f
|
|
BLAKE2b-256 checksum How to use checksums |
3b8d676748ad654c34185928281c9098504a8508d156506164c5bca64c77b43b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.3 {"installer":{"name":"uv","version":"0.12.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency log