anchor &<anchor> is aliased by *<anchor> inside its own content, so the document expands without end; point that alias at content declared outside &<anchor>, or write the content out in full(锚点在其自身内容中被别名引用,因此文档会无限展开;请将该别名指向在该锚点之外声明的内容,或完整写出该内容)
required parameter not supplied (Aggregate, at .spec.parameters.<parameter>, parameter "<parameter>" is required but not supplied by Release)(未提供必需参数:该参数为必需,但 Release 未提供)
parameter "<parameter>" value <value> not in enum [<members>](参数值不在枚举中)
parameter "<parameter>" value "<value>" does not match pattern "<pattern>"(参数值与模式不匹配)
parameter "<parameter>" value "<value>" is not a valid <format>: <reason>(参数值不是有效的格式)
parameter "<parameter>" value <value> above max <max>(参数值超过最大值)
parameter "<parameter>" failed validate predicate(参数未通过 validate 谓词)
parameter "<parameter>" validate predicate error: <detail>(参数的 validate 谓词出错)
格式失败的 <reason> 以该格式自身的术语说明值的问题。嵌套契约中的值以其路径命名,因此 items: 契约声明的 format 会在每个元素上检查,报告会指出失败的那个元素:hosts 参数的第二个元素报告于 .spec.parameters.hosts.1,其详情指出 "hosts.1"。
声明了 validateMessage: 的参数会用自己的文本替换整个详情,因此报告为 parameter contract violated (Aggregate, at .spec.parameters.<parameter>, <the validateMessage you wrote>)——框架不变,你写的句子位于约束详情原本所在的位置。
parameter "<parameter>.items": format "<format>" is not supported; the supported formats are email, uri, hostname, ipv4, ipv6, uuid, date-time, date(不支持该格式;支持的格式为 email、uri、hostname、ipv4、ipv6、uuid、date-time、date)
document envelope validation failed (Aggregate, at <path>); <line>:<column>: spec.parameters.<parameter>.format: enum: <format> does not equal any of: [email uri hostname ipv4 ipv6 uuid date-time date]. correct the document to match its kind’s schema(文档信封校验失败:format 的值不等于任何受支持的格式。请修正文档,使其符合其类型的 schema)
provider does not support the node’s input kind (node "<node-id>"). provider "<provider-name>" does not support <mode> recipes (this provider supports: <kinds>); declare one of the supported input kinds, or target a provider that supports <mode>(provider 不支持该节点的输入类型。该 provider 不支持此模式的 recipe;请声明其支持的输入类型之一,或改用支持该模式的 provider)
input-kind: [E0265] Recipe "<name>:<version>": provider "<provider-name>" does not support synthesized recipes (this provider supports: <kinds>); declare one of the supported input kinds, or target a provider that supports synthesized(输入类型:该 provider 不支持合成式 recipe;请声明其支持的输入类型之一,或改用支持合成的 provider)
provider does not support omits ("<provider-name>", node "<node-id>"). this provider’s contract does not declare that it leaves rendered documents out; remove the omits key, or render the source through a provider whose contract declares it(provider 不支持 omits(provider 及节点如上)。该 provider 的契约未声明它会略去已渲染的文档;请删除 omits 键,或通过契约声明了这一点的 provider 渲染该源)
provider does not support boundary artifacts ("<provider-name>", node "<node-id>"). this provider’s contract does not declare that it accepts files written to a boundary’s shared output; remove the boundary block, or render the Recipe through a provider whose contract declares it(provider 不支持边界制品(provider 及节点如上)。该 provider 的契约未声明它接受写入边界共享输出的文件;请删除 boundary 块,或通过契约声明了这一点的 provider 渲染该 Recipe)
Recipe: at least one input kind required (Recipe <name>:<version>, rule input-kinds, at <path>). declare one of: source (with valuesMapping), workload, artifacts(Recipe:至少需要一种输入类型(Recipe、规则 input-kinds 及位置如上)。请声明以下之一:source(配合 valuesMapping)、workload、artifacts)
filename collision across input kinds: two input-kind blocks produced a file under one output name (output name <filename>, produced by <origin1>, <origin2>)(跨输入类型的文件名冲突:两个输入类型块以同一个输出名称生成了文件,并给出该输出名称及生成它的各个块)
FeatureRecipe 中的冲突还会带上附加项:
filename collision across input kinds: two input-kind blocks produced a file under one output name (output name <filename>, produced by <origin1>, <origin2>, attachment <instance>)(跨输入类型的文件名冲突:两个输入类型块以同一个输出名称生成了文件,并给出该输出名称、生成它的各个块及所属附件)
recipe output-labels constraint: key uses a reserved namespace (Recipe <name>:<version>, rule output-labels, at .spec.outputLabels). key "<key>" in outputLabels uses a reserved namespace ("aggrega.ai/" and "app.kubernetes.io/" are reserved for platform provenance)(Recipe 的输出标签约束:键使用了保留命名空间;outputLabels 中的该键使用了保留命名空间,这两个前缀保留用于平台来源信息)
写在提升块中的键以该块的规则名报告,并在建议中指出该块:
recipe output-labels constraint: key uses a reserved namespace (Recipe <name>:<version>, rule output-component-labels, at .spec.outputComponentLabels). key "<key>" in outputComponentLabels uses a reserved namespace ("aggrega.ai/" and "app.kubernetes.io/" are reserved for platform provenance)(Recipe 的输出标签约束:键使用了保留命名空间;outputComponentLabels 中的该键使用了保留命名空间,这两个前缀保留用于平台来源信息)
recipe output-component-labels constraint: key is also declared in outputLabels (Recipe <name>:<version>, rule output-component-labels, at .spec.outputComponentLabels.<key>). key "<key>" is promoted through outputComponentLabels and also declared literally in outputLabels; keep whichever source the label should come from and drop the other(Recipe 的输出组件标签约束:该键也在 outputLabels 中声明;该键既通过 outputComponentLabels 提升,又在 outputLabels 中按字面声明;保留标签应来自的那个来源,删除另一个)
每次重复都是一条独立的检查结果,定位在重复的 id 处,并指出最先声明该 id 的步骤及其行号和列号。当某个 id 出现三次时,后面两个步骤都会指向第一个。
以下是针对第二个步骤重复了第一个步骤 id 的 FeatureRecipe 输出的消息。类别以及该条件的短代码 E0370 会出现在方括号中的头部:
a pipeline declares one step id twice (FeatureRecipe, at <path>); <line>:<column>: spec.pipeline[1].id: step id "<id>" is already declared at spec.pipeline[0].id (line <line>, column <column>). give each step of the pipeline its own id, and point every .steps.<id> reference a later step makes at the step it means (流水线将同一个步骤 id 声明了两次:spec.pipeline[1].id 的步骤 id 已在 spec.pipeline[0].id 处声明。请为流水线的每个步骤指定各自的 id,并让后续步骤中的每个步骤引用都指向它所指的步骤)
修复方法: 将两个步骤之一重命名,使每个 id 只声明一次。然后检查每个后续步骤的 with: 和 when: 模板中指向你所保留 id 的 .steps.<id> 引用,并让每个引用指向它真正需要其输出的那个步骤——正是重命名让两个步骤的输出能够分别被访问。
A document declares an API version this compiler no longer reads(文档声明了此编译器不再读取的 API 版本)
a document declares an API version this compiler no longer reads (Component, at <path>); 1:1: apiVersion: the document declares aggrega.ai/v1alpha1, and this compiler reads aggrega.ai/v1beta1. change the apiVersion line to apiVersion: aggrega.ai/v1beta1(文档声明了此编译器不再读取的 API 版本(Component);1:1: apiVersion:文档声明了 aggrega.ai/v1alpha1,而此编译器读取 aggrega.ai/v1beta1。请将 apiVersion 行改为 aggrega.ai/v1beta1)
A plugin declares a plugin ABI version this compiler no longer speaks(插件声明了此编译器不再支持的插件 ABI 版本)
插件声明了插件 ABI v1alpha1。此编译器支持插件 ABI v1beta1,不支持其他版本,因此针对较早版本构建的插件会被拒绝,而不会被运行。插件在两处声明其 ABI,每一处都在这同一个条件下被拒绝:其访客模块在加载时返回的 describe() 报告,以及其 Plugin 实体的 spec.abiVersion,后者在读取实体时即被拒绝,早于任何其他检查。声明了此编译器从未支持过的 ABI 版本的插件同样会被拒绝,由描述符检查(E0085)或 Plugin 模式(E0215)拒绝。
plugin "<plugin>" declares abi_version “v1alpha1”, and this compiler speaks “v1beta1”; rebuild the plugin against the current plugin kit and publish it again: a plugin declares a plugin ABI version this compiler no longer speaks(插件声明了 abi_version “v1alpha1”,而此编译器支持 “v1beta1”;请针对当前的插件工具包重新构建插件并重新发布:插件声明了此编译器不再支持的插件 ABI 版本)
针对 Plugin 实体输出的消息:
a plugin declares a plugin ABI version this compiler no longer speaks (Plugin, at <path>); <line>:<column>: spec.abiVersion: the Plugin declares abiVersion v1alpha1, and this compiler speaks v1beta1. rebuild the plugin against the current plugin kit and publish it again; its Plugin entity then declares abiVersion: v1beta1(插件声明了此编译器不再支持的插件 ABI 版本(Plugin);spec.abiVersion:该 Plugin 声明了 abiVersion v1alpha1,而此编译器支持 v1beta1。请针对当前的插件工具包重新构建插件并重新发布;之后其 Plugin 实体会声明 abiVersion v1beta1)
"<reference>" carries media type “application/vnd.aggrega.component.v1alpha1+yaml”, and this compiler reads “application/vnd.aggrega.component.v1beta1+yaml”; publish the artifact again with the current release: oci: artifact carries a media type this compiler no longer reads(带有媒体类型 “application/vnd.aggrega.component.v1alpha1+yaml”,而此编译器读取 “application/vnd.aggrega.component.v1beta1+yaml”;请使用当前版本重新发布该制品:oci: 制品带有此编译器不再读取的媒体类型)
file load failed: the file could not be read, or its bytes did not parse (Aggregate, at <path>, failed to read file: <underlying reason>)(文件加载失败:无法读取该文件,或其字节无法解析;读取文件失败)
以及其文本无法解析时:
file load failed: the file could not be read, or its bytes did not parse (Aggregate, at <path>, failed to unmarshal YAML: <underlying reason>)(文件加载失败:无法读取该文件,或其字节无法解析;YAML 反序列化失败)
file load failed: the file could not be read, or its bytes did not parse (Release, at .spec.parameters.$import: <path>, failed to read file: <underlying reason>)(文件加载失败:无法读取该文件,或其字节无法解析;读取文件失败)
file load failed: the file could not be read, or its bytes did not parse (Release, at .spec.parameters.$import: <path>, failed to unmarshal YAML: <underlying reason>)(文件加载失败:无法读取该文件,或其字节无法解析;YAML 反序列化失败)
相对路径从写入它的 Release 所在目录解析——即命令指定的 Release,或其 extends: 链中的某一环——无论命令从何处运行,因此命令行和编辑器读取的是同一个文件;绝对路径则指明其自身位置。请确认构建所基于的检出在该位置包含此文件:在你的机器上存在但被排除在版本控制之外的参数文件,在持续集成运行期间并不存在,这是遇到此问题的常见方式。指向工作区之外的路径——或者对于在工作区外指定的 Release,指向该 Release 自身目录之外的路径——根本不会被读取,并在下文“A reference to another file leads out of the directory it must stay inside(对另一文件的引用超出了它必须保持在内的目录)”下报告。
file load failed: the file could not be read, or its bytes did not parse. <surface>: read imported schema <value>: <the operating system's reason>(文件加载失败:无法读取该文件,或其字节无法解析;读取导入的 schema)
Recipe 或 FeatureRecipe 的 valuesMapping:、workload: 或 artifacts.<name>: 导入也会在此报告,原因和修复方法相同:该指令格式正确,但它指向的文件没有产出内容。这三种正文是 Go 模板源码而非文档,因此只有读取可能失败——此时不会解析它们。实体和指明路径的键会出现在从句中,源指针则是被导入文件自身的路径:
file load failed: the file could not be read, or its bytes did not parse (Recipe <name> valuesMapping file import, <the operating system's reason>). if you meant a library entry rather than a file, the reference needs its fragment — an $import: carrying none is read as a file path, and an unquoted value ends where a space before # starts a comment, so quote the whole reference(文件加载失败:无法读取该文件,或其字节无法解析;valuesMapping 文件导入。如果你指的是库条目而非文件,引用需要带上其片段——不带片段的 $import: 会被当作文件路径读取,而未加引号的值会在 # 前的空格开始注释处结束,因此请给整个引用加上引号)
file load failed: the file could not be read, or its bytes did not parse (Recipe <name> workload file import, <the operating system's reason>). if you meant a library entry rather than a file, the reference needs its fragment — an $import: carrying none is read as a file path, and an unquoted value ends where a space before # starts a comment, so quote the whole reference(文件加载失败:无法读取该文件,或其字节无法解析;workload 文件导入。如果你指的是库条目而非文件,引用需要带上其片段——不带片段的 $import: 会被当作文件路径读取,而未加引号的值会在 # 前的空格开始注释处结束,因此请给整个引用加上引号)
file load failed: the file could not be read, or its bytes did not parse (Recipe <name> artifact <key> file import, <the operating system's reason>). if you meant a library entry rather than a file, the reference needs its fragment — an $import: carrying none is read as a file path, and an unquoted value ends where a space before # starts a comment, so quote the whole reference(文件加载失败:无法读取该文件,或其字节无法解析;artifact 文件导入。如果你指的是库条目而非文件,引用需要带上其片段——不带片段的 $import: 会被当作文件路径读取,而未加引号的值会在 # 前的空格开始注释处结束,因此请给整个引用加上引号)
<n> documents under the catalog directories declare an Aggrega apiVersion and could not be loaded, so nothing was checked: <path>, <path>(catalog 目录下有若干文档声明了 Aggrega apiVersion 但无法加载,因此未检查任何内容)
file load failed: the file could not be read, or its bytes did not parse (catalog document, failed to unmarshal YAML: <the parser's reason>)(文件加载失败:无法读取该文件,或其字节未能解析(catalog 文档,YAML 反序列化失败))
对于能够解析但无法解码的文档,结尾为 failed to decode the envelope: 加上行号以及解码器在该处发现的内容——对于写成列表的 metadata,为 line 4 (metadata): a list is written where a map is expected;对于无法读取的文件,结尾为 failed to read file: 加上操作系统给出的原因。能够加载但声明了任何 catalog 都不包含的种类的文档,会由同一个中止指出,计入同一个头部的计数,并列在其自身的条件之下——参见下文“A catalog document declares a kind a catalog does not hold (catalog 文档声明了 catalog 不包含的种类)”。
<n> documents under the catalog directories declare an Aggrega apiVersion and could not be loaded, so nothing was checked: <path>, <path> (catalog 目录下有若干文档声明了 Aggrega apiVersion 但无法加载,因此未检查任何内容) catalog document declares a kind a catalog does not hold (kind “Componnent”). a catalog holds Component, Feature, Recipe, FeatureRecipe, SchemaLibrary, MappingLibrary, WorkloadLibrary, ArtifactLibrary, Aggregate and Plugin documents, and passes over a Workload, a Manifest or a Release; correct the kind, or move the file out of the catalog directories (catalog 文档声明了 catalog 不包含的种类。catalog 包含 Component、Feature、Recipe、FeatureRecipe、SchemaLibrary、MappingLibrary、WorkloadLibrary、ArtifactLibrary、Aggregate 和 Plugin 文档,并会跳过 Workload、Manifest 或 Release;请更正种类,或将该文件移出 catalog 目录)
对于未声明任何种类的文档,会以 no kind 代替 kind "<kind>"。
构建不会因这样的文档而停止:它会像每次加载一样跳过该文档,而任何 Release 都未到达的文档永远不会导致构建失败。当某个 Release 确实到达该实体时,构建会在该引用处停止,归于下文的“A reference names no entity the catalog holds (引用未指向 catalog 所包含的任何实体)”,并且当该文件声明了引用所要求的名称时,该失败下方的注释会指出该文件——参见该条目。
a path names content outside the entity’s own directory ("<path>"). remediation: move the file into the directory holding the entity, or a directory beneath it, and name it with a path relative to that directory. An entity’s content lives in the entity’s own directory because every file a publication of it carries is taken from there; a path that leaves it points at a file that would not travel with the entity(路径指向了实体自身目录之外的内容(即上述路径)。补救方法:将该文件移入存放该实体的目录或其下级目录,并使用相对于该目录的路径来指定它。实体的内容位于实体自身的目录中,因为实体的发布所携带的每个文件都取自该目录;离开该目录的路径指向的文件不会随实体一起分发)
对于被链接带出目录的路径,还会给出该链接及其指向的位置:
a path names content outside the entity’s own directory ("./frag/fragment.yaml", the link <entity-directory>/frag leads to <elsewhere>/frag). remediation: replace the link with a copy of what it leads to, placed inside the directory holding the entity. An entity’s content lives in the entity’s own directory because every file a publication of it carries is taken from there; a link leading out of it would carry the bytes it points at under a name inside the entity(路径指向了实体自身目录之外的内容(即上述路径,其中的链接指向目录之外的位置)。补救方法:将该链接替换为其所指内容的副本,并放在存放该实体的目录中。实体的内容位于实体自身的目录中,因为实体的发布所携带的每个文件都取自该目录;指向该目录之外的链接会以实体内部的名称携带其所指向的字节)
no source adapter serves the source kind (Recipe <name>:<version>, rule source-kind, at <file>). the source names kind "<kind>"; name a kind a source adapter serves (<the served kinds>), or write the source as a single URI whose shape names its kind(没有 source adapter 服务该源类型(Recipe,规则 source-kind)。源指定了该类型;请指定某个 source adapter 服务的类型,或将源写成一个其形式即表明类型的单一 URI)
No source adapter is registered in this program for a source kind(本程序中没有为某个源类型注册 source adapter)
源由为其类型注册的适配器获取。此条件报告的是按没有注册适配器的类型分派的获取。没有适配器服务的编写类型会在读取其 Recipe 时被拒绝(见上文“A Recipe’s source: names a kind nothing knows how to acquire(Recipe 的源指定了一种无从获取的类型)”),因此作者所写的任何内容都不会到达这里:它报告的是组装时缺少其所服务类型的适配器的程序,或基于 Aggrega 的 Go 包构建、分派其自行组装的类型的程序。
输出的消息,指明类型:
kind "<kind>": no source adapter is registered in this program for the source kind(本程序中没有为该源类型注册 source adapter)
the source URL carries a credential (Recipe <name>:<version>, rule source-url, at <file>). spec.source.url names a user or password for host <host>; remove it from the URL and write the credential in the netrc file instead, as an entry “machine <host> login <user> password <secret>” (the file NETRC names, else .netrc in your home directory, or _netrc in %USERPROFILE% on Windows)(源 URL 携带了凭据(Recipe,规则 source-url)。spec.source.url 为该主机指定了用户或密码;请将其从 URL 中删除,改为在 netrc 文件中以 machine、login、password 条目的形式写入凭据(即 NETRC 指定的文件,否则为主目录中的 .netrc,在 Windows 上为 %USERPROFILE% 中的 _netrc))
而对于其他协议,补救办法是删除密码:
the source URL carries a credential (Recipe <name>:<version>, rule source-url, at <file>). spec.source.url names a password for host <host>; remove it from the URL, which is written into the lockfile and the cache as authored(源 URL 携带了凭据(Recipe,规则 source-url)。spec.source.url 为该主机指定了密码;请将其从 URL 中删除,因为 URL 会按所写原样写入 lockfile 和缓存)
引用了 Release 未提供的键不属于此中止。缺失的键在此处解析为空值,并由上文“Parameter type mismatch / contract violation(参数类型不匹配/契约违例)”中描述的参数检查连同其类型和契约一起捕获。此中止报告的是模板引擎根本无法处理的文本——未闭合的 {{、拼写错误的函数名、各阶段无法衔接的管道。当 Release 未提供某个参数时,通过 index 读取该参数({{ index .parameters "db_size" }})属于运行时失败,由此中止承载并指出该键:如下文“A template indexes a map with a key the map does not hold(模板使用映射中不存在的键索引映射)”所述,在每个模板表面上,index 遇到映射中不存在的键都会中止。
invalid parameter reference: check the {{ .parameters.* }} expression names a declared parameter and parses as a Go template (Aggregate <path>, “template parse error: <underlying reason>”)(无效的参数引用:请检查 {{ .parameters.* }} 表达式是否指向已声明的参数并能解析为 Go 模板)
invalid parameter reference: check the {{ .parameters.* }} expression names a declared parameter and parses as a Go template (Aggregate, template parse error: <underlying reason>)(无效的参数引用:请检查 {{ .parameters.* }} 表达式是否指向已声明的参数并能解析为 Go 模板)
invalid parameter reference: check the {{ .parameters.* }} expression names a declared parameter and parses as a Go template (Aggregate, template execution error: <underlying reason>)(无效的参数引用:请检查 {{ .parameters.* }} 表达式是否指向已声明的参数并能解析为 Go 模板)
invalid parameter reference: check the {{ .parameters.* }} expression names a declared parameter and parses as a Go template (Aggregate, the template reads <reference>, and an Aggregate’s text defines no root but .parameters; template execution error: <underlying reason>)(无效的参数引用:请检查 parameters 表达式是否指向已声明的参数并能作为 Go 模板解析(Aggregate,模板读取了该引用,而 Aggregate 的文本除 .parameters 外未定义任何根;模板执行错误))
duplicate Aggregate/Manifest identity (metadata.name) in the Release directory: Aggregate "<name>" declared more than once in <release-directory>(Release 目录中存在重复的 Aggregate/Manifest 标识(metadata.name):Aggregate 被多次声明)
aggregate/manifest reference unresolvable: no Aggregate named "<reference>" in the Release directory, catalog, or registry(aggregate/manifest 引用无法解析:Release 目录、catalog 或注册表中均无该名称的 Aggregate)
aggregate/manifest reference unresolvable: Aggregate "<reference>" not found; unparseable file <path> could not be indexed and may be it: <parse failure>(aggregate/manifest 引用无法解析:未找到该 Aggregate;无法解析的文件未能建立索引,可能就是该实体)
以及当引用直接指向的正是一个无法解析的文件时:
aggregate/manifest reference unresolvable: needed Aggregate "<reference>" is the unparseable file <path>: <parse failure>(aggregate/manifest 引用无法解析:所需的 Aggregate 是一个无法解析的文件)
边界放置组件的方式有三种,三种都算数。 直接在 components: 下按组件在组合完成后所带的 id 命名它,即放置了它。在路由条目自身的 components: 中按组件在该子模块内所带的本地名称命名它,同样放置了它。在 aggregates: 下把整个子模块路由进来,则放置了该模块包含的每一个组件。因此,此中止也涵盖以下情况:一个子模块被路由进两个边界;一个模块被路由进一个边界,而嵌套在其中的模块被路由进另一个边界;一个组件在某个边界中被命名,而包含它的模块被路由进另一个边界。
把一个模块路由进某个边界,同时又在同一个边界下命名其某个组件,并不构成冲突——两处放置对组件所属位置的判断一致——可以正常构建。但在同一个边界下把一个 id 写两次,即使在这里也是冲突:边界的 components: 中的条目,与该边界路由条目内针对同一组件的条目,是为同一组件携带配置的两个条目,无从取舍。
component declared in more than one boundary: declare each component in exactly one boundary (Release <name>, at <field-path>, "<component>", named in the components block of boundary "<boundary-b>", while it is already named in the components block of boundary "<boundary-a>", that earlier entry naming "<component>", both declared in "<path>")(组件在多个边界中声明:每个组件只能在一个边界中声明)
命名边界的两个子句,其措辞取决于各条目所写的块。出错的条目采用以下之一:
named in the components block of boundary "<boundary>"——边界自身的 components: 映射;
named inside a routing entry in boundary "<boundary>"——该边界 aggregates: 下某个路由条目的 components: 映射;
routed as a sub-module into boundary "<boundary>"——路由条目本身。
更早的放置在同一句中接续,采用以下之一:
while it is already named in the components block of boundary "<boundary>";
while it is already named inside a routing entry in boundary "<boundary>";
while it is already placed by a sub-module routed into boundary "<boundary>"。
component declared in more than one boundary: declare each component in exactly one boundary (Release <name>, at <field-path>, sub-module "<module>", routed as a sub-module into boundary "<boundary-b>", while it is already placed by a sub-module routed into boundary "<boundary-a>", that earlier entry naming "<module>", both declared in "<path>")(组件在多个边界中声明:每个组件只能在一个边界中声明)
manifest annotation binding uses reserved prefix (Manifest, at <field-path>, "<key>", reserved prefix "aggrega.ai/", routing to Feature "<feature-uri>", author the binding under a domain of your own such as "feature.<your-domain>/")(Manifest 注解绑定使用了保留前缀)
对每个目标 Feature,一个给定的路径与支柱组合只能由一个绑定声明。两个绑定以不同路径指向同一个 Feature 属于正常写法,可以构建;两个绑定把同一路径路由到两个不同的 Features 也一样。
绑定按 Manifest 声明它们的顺序遍历,因此消息中先列出的绑定总是你文档中较早的那个。
发出的消息:
manifest annotation bindings collide on same Feature path+pillar (Manifest, at <path>, annotation bindings "<first-key>" and "<second-key>" both target Feature "<feature-uri>" with path "<path>" routing to pillar "<pillar>"; only one binding may declare a given (path, pillar) pair per Feature)(Manifest 注解绑定在同一 Feature 的路径+支柱上冲突)
release reached resolve un-normalized (non-empty root components alongside a synthesized default boundary): construct releases through the normalization core (types.NormalizeRelease via the load path), not a hand-built literal(release 未经规范化就进入解析:请通过规范化核心构造 release,而不是手工构建字面量)
同一条件也支撑着上文“YAML anchor aliased inside its own content(YAML 锚点在其自身内容中被别名引用)”中记录的锚点递归拒绝。那一种是单个文档自身文本内部的循环;这一种是文档之间的循环。消息中的链可以让你一眼区分两者:文档之间的循环列出库条目,文档内部的循环列出锚点。
A declared schema cannot be resolved(声明的 schema 无法解析)
**修复方法:**在消息指出的位置打开 schema,阅读所报告的原因。确认该关键字的值是字符串、模板可以解析,并且它访问的每条路径都是被验证的值实际具有的——谓词以 .value 读取该值,而去读取其他内容是最常见的错误。如果原因指出 index 未找到某个键,请改用 hasKey 检测该键,或用 get 读取它:index 遇到映射中不存在的键时会中止,详见下文“A template indexes a map with a key the map does not hold(模板使用映射中不存在的键索引映射)”。确保模板最终产生 true 或 false:比较运算会产生,而仅渲染该值的模板不会。
A Workload does not satisfy the Workload schema(Workload 不满足 Workload schema)
workload validation failed (Workload in Recipe <name>:<version>, at <path>, schema stage):
.containers.<name>.<field>: <what the schema required> — <the fix, where one can be stated>.initContainers[<i>].<field>: <what the schema required> — <the fix, where one can be stated>
.containers.main.imagePullPolicy: against /$defs/container: enum: <redacted> does not satisfy enum ["Always","Never","IfNotPresent"] (the value is withheld because the template that rendered this document reads a value declared sensitive)
workload featuresSchema cross-check failed (Workload in Recipe <name>:<version>, at <path>, featuresSchema stage):
.containers.<name>.attachments.<KEY>.from: references slot "<slot>" which is not declared in the Component’s featuresSchema — either declare the slot in the Component (or Feature) featuresSchema, or rename the reference to an existing slot
.containers.<name>.attachments.<KEY>.from: slot "<slot>" is blackbox (no inject: allowlist) and cannot be referenced from a Workload attachments entry — blackbox slots are delivered by Recipe-internal plumbing; remove the Workload-side reference, or widen the slot’s inject allowlist if Workload-side delivery is intended
.containers.<name>.attachments.<KEY>.as: delivery mechanism "<as>" is not permitted by slot "<slot>" (inject allowlist: [<mechanisms>]) — use one of the allowlisted delivery mechanisms ([<mechanisms>]), or widen the slot’s inject allowlist in the Component/Feature featuresSchema
.containers.<name>.attachments.<KEY>.connection: names connection "<alias>" for slot "<slot>", but the component draws no connection under that alias — name a connection the component draws (<aliases>), or remove connection to read a slot the Component declares for its own attachments
.containers.<name>.attachments.<KEY>.from: names slot "<slot>" of connection "<alias>", which socket "<socket>" does not declare — name a slot socket "<socket>" declares (<slots>), or declare the slot in that socket’s featuresSchema
.containers.<name>.attachments.<KEY>.from: names "<alias>.<slot>", the name the compiler composes for slot "<slot>" of connection "<alias>"; a slot a connection’s socket declares is named by naming the connection — write connection: <alias> beside from: <slot>
所需的键取决于条目,诊断结果会说明它需要哪些键。自行指定 key: 的条目本身提供了字段,因此只需发布资源的 name,这使其能够引用多键资源。未指定 key: 的条目读取插槽唯一发布的字段,因此 name 和 key 都必须存在。
该检查只判断这些键是否存在,从不检查其值。所有违规条目会在同一个标题下一并报告。
发出的消息:
workload attachment slot is not referenceable (Workload in Recipe <name>:<version>, at <path>, slotReferenceability stage):
.containers.<name>.attachments.<KEY>.from: slot "<slot>" is not referenceable: its resolved provides does not expose "<key>" (a workload attachment reference reads the provides keys name and key) — reference a slot filled by an attachment whose schema.provides declares the keys this reference reads, or deliver it through the slot’s inject pipe rather than a workload reference
输出的消息(针对 Recipe 的 Workload 中某个主容器上的一对)。类别和此情况的短代码 E0345 出现在方括号标头中,位置显示为 <path> at .spec.workload:
a container declares one environment variable twice ("<NAME>", container "<container>"). Rename one of the two, or write them under complementary template conditions so that only one of them renders(一个容器两次声明了同一个环境变量。请重命名其中之一,或将它们写在互补的模板条件下,使其中只有一个被渲染)
当一个 Workload 带有多对时,结果会归组在一行给出文档的标题下:containers of the Workload this Recipe renders name one environment variable twice,或者对于 FeatureRecipe,containers of the Workload rendered by the FeatureRecipe that attachment "<attachment>" binds name one environment variable twice。
document envelope validation failed (Release, at <path>); <line>:<column>: spec.parameters: no oneOf branch matched (2 branches tried): branch[0]: type: expected object, got array; branch[1]: type: expected object, got array. correct the document to match its kind’s schema(文档信封校验失败(Release):spec.parameters:没有匹配的 oneOf 分支(尝试了 2 个分支):branch[0]:类型:期望对象,得到数组;branch[1]:类型:期望对象,得到数组。请更正文档以匹配其类型的 schema)
对于与其他键并列的 $import:,第二个分支以 additionalProperties: unexpected property: "<key>" 结尾;对于写成列表而非字符串的 $import:,则以 validation: type: array has type "array", want "string" 结尾。
值不是映射时输出的消息,指明在该处所写的内容——例如 a list:
parameters: shape must be an inline object or {$import: }: line <line>: <shape> is written where a map is expected(parameters:形式必须是内联对象或仅含 $import 的映射:在需要映射的位置写入了其他形式)
以及 $import: 与其他内容共处同一映射,或指明的不是路径时:
parameters: shape must be an inline object or {$import: }: $import: must be the only key (got <n> keys) at line <line>(parameters:形式必须是内联对象或 $import 映射:$import: 必须是唯一的键,在所示行得到了多个键)
parameters: shape must be an inline object or {$import: }: $import value must be a string scalar at line <line>(parameters:形式必须是内联对象或 $import 映射:在所示行,$import 的值必须是字符串标量)
artifacts entry: shape must be a string scalar or {$import: }: got <n> keys at line <line>(artifacts 条目:形式必须是字符串标量或 $import 映射:发现多个键)
valuesmapping: shape must be a string scalar or {$import: }: got key "<key>" at line <line>(valuesmapping:形式必须是字符串标量或 $import 映射:发现了其他键)
workload: shape must be a string scalar or {$import: }: $import value must be a string scalar at line <line>(workload:形式必须是字符串标量或 $import 映射:$import 的值必须是字符串标量)
三个字段中的任何一个都可能报告上述任一结尾;既不属于任一形式的值以 line <line>: <shape> is written where text or a map is expected 结尾,并指明所写的内容——最常见的是 a list。
library reference: a reference to a library entry carries no whitespace or line break: $import target "<reference>" at line <line>(库引用:对库条目的引用不能包含空白或换行:$import 目标)
mappinglibrary: entry body must be a string scalar: line <line>: <shape> is written where text is expected(mappinglibrary:条目主体必须是字符串标量:在需要文本的位置写入了其他形式)
workloadlibrary: entry body must be a string scalar: line <line>: <shape> is written where text is expected(workloadlibrary:条目主体必须是字符串标量:在需要文本的位置写入了其他形式)
artifactlibrary: entry must be a mapping of filename to a string body: line <line>: <shape> is written where a map is expected(artifactlibrary:条目必须是从文件名到字符串主体的映射:在需要映射的位置写入了其他形式)
以及对于条目是映射、但其中某个文件不是标量的 bundle,消息会指出该文件:
artifactlibrary: entry must be a mapping of filename to a string body: file "<filename>": line <line>: <shape> is written where text is expected(artifactlibrary:条目必须是从文件名到字符串主体的映射:该文件在需要文本的位置写入了其他形式)
schemalibrary: template not found: "<template-name>" not declared in spec.templates
schemalibrary: template parameter missing: "<parameter-name>" (template "<template-name>")
schemalibrary: template parameter type mismatch: <what the type check found>
schemalibrary: template parameter type mismatch: argument "<argument-name>" is not declared in template "<template-name>"’s $params
provider "<plugin-name>" declares well-known annotation "<key>" at scope "<scope>", but its contract.inputKinds.<field> is not claimed; declare the key only at a scope the provider renders, or claim the input kind: wellKnownAnnotations: a key is declared at a scope the provider’s contract does not render
compactform at <path-inside-the-schema>:<line> (keyword "<key>"): cross-document $ref sibling not allowed (allowed: properties, required, description)
如果该同级键试图重新开放合并后的结构,语句会给出替代做法:
compactform at <path-inside-the-schema>:<line> (keyword "additionalProperties"): cross-document $ref sibling not allowed (allowed: properties, required, description); use $jsonschema: to embed an open-object schema if the merged shape must accept arbitrary properties
compactform at <path-inside-the-schema>:<line> (keyword "$jsonschema"): escape content does not parse as YAML: <what the parse reported>
compactform at <path-inside-the-schema>:<line> (keyword "$jsonschema"): expected block-scalar string or nested mapping
compactform at <path-inside-the-schema>:<line> (keyword "properties"): expected a mapping of property names to schemas
compactform: unsupported YAML node kind
compactform at <path-inside-the-schema>:<line> (keyword "<constraint>"): constraint applies to a single declared type (integer/number/string/array); type: is unresolved (union or absent) — narrow type: to a single value or remove this constraint
compactform at <path-inside-the-schema>:<line> (keyword "<constraint>"): constraint applies to integer/number/string/array; declared type is <the type as written>
compactform at <path-inside-the-schema>:<line> (keyword "type"): expected a scalar type name or a sequence of type names (JSON Schema 2020-12 array-of-types); got unsupported node kind
compactform at <path-inside-the-schema>:<line> (keyword "valuesType"): expected a scalar type name
它记录所属的条件是 compactform: constraint not valid for declared type,也就是其短代码所对应的条件。
compactform at <path-inside-the-schema>:<line> (keyword "$ref"): expected a non-empty reference URL(应为非空的引用 URL)
compactform at <consumer-document> (keyword "$ref"): cross-document $ref shape must be <LibraryName>#/schemas/<EntryName>: <the value as written>(跨文档 $ref 的形式必须是库名#/schemas/条目名)
compactform at <consumer-document> (keyword "$ref"): cross-document $ref version separator is ’:’, not ’@’ — use <the corrected value>: <the value as written>(跨文档 $ref 的版本分隔符是“:”而不是“@”,请使用更正后的值)
这些情况记录在条件 compactform: $ref unresolvable 之下。
目标不存在。 引用的写法正确,但库或库中的条目不存在,或者根本没有提供可供解析的库目录:
compactform at <consumer-document> (keyword "$ref"): SchemaLibrary <library> not found in catalog (referenced from <consumer-document>): <the value as written>(在目录中找不到该 SchemaLibrary)
compactform at <consumer-document> (keyword "$ref"): entry <entry> not found in SchemaLibrary <library>: <the value as written>(在该 SchemaLibrary 中找不到该条目)
compactform at <path-inside-the-schema>:<line> (keyword "$ref"): cross-document $ref but no SchemaLibrary catalog supplied: <the value as written>(存在跨文档 $ref,但未提供 SchemaLibrary 目录)
这些情况记录在条件 compactform: cross-document $ref target not found 之下。
将两者区分开,报告才具有可操作性:前者是需要在你正在查看的文档中改写的值,后者则是构建能看到什么的问题。展开为自身的引用又是第三种情况,报告为上文的“A library reference expands into itself (库引用展开为自身)”。
compactform at <consumer-document> (keyword "$ref"): cross-document $ref carries a registry host; reference the library by identity (use <Library>#/schemas/<Entry>): <the value as written>(跨文档 $ref 带有注册表主机;请按标识引用该库)
如果无法解析,诊断语句在值之后结束:
compactform at <consumer-document> (keyword "$ref"): cross-document $ref carries a registry host; reference the library by identity: <the value as written> (跨文档 $ref 带有注册表主机;请按标识引用库)
该情况记录在条件 compactform: cross-document $ref carries a registry host; reference the library by identity 之下,其短代码即解析为此条件。
**修复方法:**删除主机以及库名之前的所有内容,只保留 <Library>#/schemas/<Entry>。如需版本下限,在库名之后写作 :<version>。同一规则也适用于 Recipe 和 FeatureRecipe 上的 $import: 字段,这些字段在下文“A library $import: addresses its library by registry location(库导入按注册表位置寻址其库)”下单独报告。
A schema $import: cannot be applied(无法应用 schema 导入指令)
$import: must be the only key when a schema is imported from a file.(从文件导入 schema 时,该导入指令必须是唯一的键。) 该指令与手写的 schema 内容共用同一个映射。$import: 会替换整个值,因此同级的键没有可以合并的对象。
$import: value must be a path to a file.(该导入指令的值必须是文件路径。) 该值为空,或者不是单个字符串。
$import: takes a file path beside this entity, not a registry location <value>.(该导入指令接受的是此实体旁边的文件路径,而不是注册表位置。) 该值指向了一个注册表。名称通过哪个注册表解析属于工作区配置,因此 schema 位置从不携带注册表;消息会给出应改用的引用形式。
$import: takes a file path beside this entity; reference the SchemaLibrary entry <value> with $ref: instead.(该导入指令接受的是此实体旁边的文件路径;请改为用引用关键字引用该 SchemaLibrary 条目。) 该值指向了一个库条目。库条目应被引用,而不是导入——$ref: 才是解析库条目的关键字。
imported schema <value> must be a YAML map of schema content; it is not.(导入的 schema 必须是包含 schema 内容的 YAML 映射,但实际不是。) 文件已找到、读取并解析,但解析结果是标量或序列,因此没有可替换的 schema 内容。
格式正确、但所指文件构建无法获取的指令,会在别处以不同代码报告。 无法解析的路径、不存在或无法读取的文件,以及无法解析为 YAML 的字节,都不是你所写内容的错误(因为没有可供判断的导入文档),因此它们按加载错误报告,归在上文的“A file cannot be read, or its bytes do not parse (文件无法读取,或其字节无法解析)”之下,该处说明了每种情况所带的子句。如果你要捕获的是缺失或无法读取的导入文件,请匹配该条件并记录其代码。
路径相对于包含实体文件的目录进行解析,这与其他所有带导入的字段使用的基准相同。如果导入的内容本身又声明了 $import:,会继续跟随;若导入链返回到某个正在处理中的文件,则报告为上文的“A library reference expands into itself (库引用展开为自身)”,而不在此处报告。写在由导入引入的文件中的指令,会在该文件及其中的行处报告,因为那里才是需要修正的地方;写在实体中的指令则在实体处报告。
a schema block declares a key that names no data pillar (<Kind><name>, rule schema-pillars, at .spec.schema.<key>). rename "<key>" to one of the pillar keys, or remove it and the contract beneath it; allowed: values, infra, provides. See vocabulary/data-pillars.md for the canonical pillar set.(schema 块声明了一个不对应任何数据支柱的键。请将该键重命名为某个支柱键,或删除它及其下的契约;允许的键:values、infra、provides。规范的支柱集合见 vocabulary/data-pillars.md。)
aggrega_parse_source: producer-consumption re-entry denied: a producer reached through the host may not issue a further producer-consumption call(aggrega_parse_source:拒绝生产者消费重入:通过宿主调用的生产者不得再发起生产者消费调用)
<path>: artifact_cache_dir "<value>" names the workspace root itself; a catalog directory at the workspace root would then be stepped over as cache, leaving nothing to load — give the cache its own subdirectory (for example .aggrega/cache): workspace configuration is invalid(artifact_cache_dir 的值指向了工作区根目录本身;这样位于工作区根目录的目录会被当作缓存跳过,导致没有可加载的内容——请为缓存指定单独的子目录:工作区配置无效)
不可用的 signing.kinds 条目,消息还会给出涵盖所有类型的通配符:
<path>: signing.kinds entry "<kind>" is not a signable artifact kind; use a catalog entity or plugin kind, or "all" for every kind: workspace configuration is invalid(signing.kinds 中的该条目不是可签名的制品种类;请使用目录实体种类或插件种类,或使用表示所有种类的通配值:工作区配置无效)
写成注册表位置的 provider 绑定,它会指出该条目、capability 以及应写的形式:
<path>: plugins.providers[<n>] binds capability "<capability>" to "oci://<registry>/<repository>", which is where a plugin is published rather than which plugin it is; a provider binding names its plugin by its identity — write uri: provider/<name>, with an optional :<version>: workspace configuration is invalid(plugins.providers 条目把 capability 绑定到了注册表位置,而注册表位置说明的是插件发布在哪里,而不是它是哪个插件;provider 绑定按插件的标识指明其插件——请在 uri 中写插件的标识,可带可选的版本:工作区配置无效)
<path>: plugins.linter[<n>] names the entry function "<function>" but no plugin uri; an attachment on this list selects its plugin by uri, so this one attaches no plugin and "<function>" is never called — add the uri of the plugin that exports it: workspace configuration is invalid(plugins.linter 中的条目指明了入口函数,但没有指明插件的 URI;此列表上的挂接项按 URI 选择其插件,因此该条目不挂接任何插件,该函数永远不会被调用——请添加导出该函数的插件的 URI:工作区配置无效)
以其他拼写书写的 registry 主机,此处为 HUB.AGGREGA.AI:
<path>: default_registry "HUB.AGGREGA.AI" is not written as the registry host it names; write "hub.aggrega.ai" — lowercase, with no scheme, path, credentials or default port — which is the spelling that host’s trust policy is kept under: workspace configuration is invalid(default_registry 的值没有按其所指注册表主机的写法书写;请改用小写、不带协议、路径、凭据或默认端口的写法,该主机的信任策略正是以这一写法存放的:工作区配置无效)
<path>: default_registry "GHCR.io/acme" is not written as the registry location it names; write "ghcr.io/acme" — the registry host lowercase, with no scheme, credentials or default port, followed by the repository path — which keeps that host’s trust policy applying to it: workspace configuration is invalid(default_registry 的值没有按其所指注册表位置的写法书写;请将注册表主机写为小写、不带协议、凭据或默认端口,后接仓库路径,这样该主机的信任策略才会继续适用于它:工作区配置无效)
条目名称后跟路径,此处为 local/acme,而名为 local 的条目对应 127.0.0.1:5000:
<path>: default_registry "local/acme" is the name of the registries entry "local" followed by a path, and an entry’s name stands for that entry’s host alone; write "local" to use the entry, or its host followed by the path, "127.0.0.1:5000/acme": workspace configuration is invalid(default_registry 的值是 registries 条目的名称后接路径,而条目名称只代表该条目的主机;若要使用该条目,请只写条目名称,或写该条目的主机后接路径:工作区配置无效)
不指向任何主机的值,其说明会列出主机可采用的形式:
<path>: registries[<n>].host "<value>" is not a registry host; write a lowercase host name containing a dot (registry.example.com), localhost, a single name followed by a port (registry:5000), or an IP address, an IPv6 one in brackets — each with an optional :port and nothing else: workspace configuration is invalid(不是 registry 主机;请写包含点号的小写主机名(registry.example.com)、localhost、单个名称后跟端口(registry:5000),或 IP 地址(IPv6 地址加方括号)——均可带可选的 :port,不含其他内容:工作区配置无效)
列出的 catalog 目录处什么都不存在时,消息会指出文件和行、列表、按原样书写的条目及其解析到的路径——列表为 workspace.catalog_dirs、workspace.catalog_dirs_append,或某个 Release 条目的列表,例如 `catalog_dirs` of the `workspace.releases` entry "release.yaml":
<path>:<line>: the `workspace.catalog_dirs` entry "<entry>" names <directory>, which does not exist; create that directory, or remove the entry: workspace configuration is invalid(该条目指明的目录不存在;请创建该目录,或删除该条目:工作区配置无效)
以及空的 workspace: 标记:
workspaceconfig: <path>: workspace must be a mapping; write workspace: {} to mark a workspace root with no catalog directories: workspace configuration is invalid(workspace 必须是映射;若要标记一个没有目录的工作区根目录,请写一个空映射:工作区配置无效)
workspaceconfig: the <socket> socket is bound by capability "<capability>", but the cross-cutting sockets attach by uri: their plugin serves no capability, so a capability lookup matches nothing; attach it with uri: instead: a cross-cutting socket is bound by capability but attaches by uri(该插槽按 capability 绑定,但横切插槽按 uri 附加:其插件不提供任何 capability,因此按 capability 查找匹配不到任何内容;请改为按 uri 附加:横切插槽按 capability 绑定,但它按 uri 附加)
provider 绑定上不起作用的 function::
workspaceconfig: the provider socket binding for capability "<capability>" sets function:, but a provider drives a fixed set of phase-keyed exports rather than one selectable entry, so function: names nothing there; remove it: a provider socket binding sets a field with no referent on that socket(该 capability 的 provider 插槽绑定设置了 function 字段,但 provider 驱动的是一组固定的、按阶段键控的导出,而不是一个可选择的入口,因此该字段在此不指向任何内容;请删除它:provider 插槽绑定设置了一个在该插槽上没有指代对象的字段)
以及不起作用的 with:,它以相同形式报告,并指出该配置应放在何处:
workspaceconfig: the provider socket binding for capability "<capability>" sets with:, but provider render configuration belongs in the Recipe, not the workspace provider binding; remove it: a provider socket binding sets a field with no referent on that socket(该 capability 的 provider 插槽绑定设置了 with 字段,但 provider 的渲染配置应写在 Recipe 中,而不是工作区的 provider 绑定中;请删除它:provider 插槽绑定设置了一个在该插槽上没有指代对象的字段)
workspaceconfig: capability "<capability>" is bound to more than one provider plugin; keep exactly one plugins.providers entry per capability: capability is bound to more than one provider plugin(该 capability 绑定到了多个 provider 插件;每个 capability 只保留一个 plugins.providers 条目:capability 绑定到了多个 provider 插件)
importer "<identity>" is attached by <key>[<position>] in <file> (uri "<uri>") and again by <key>[<position>] in <file> (uri "<uri>"); keep exactly one plugins.importer entry per importer, its uri naming the version you want: importer is attached by more than one plugins.importer entry(该导入器由一个文件中的某个条目附加,又由另一个条目再次附加;每个导入器只保留一个 plugins.importer 条目,并让其 uri 指明你需要的版本:导入器被多个 plugins.importer 条目附加)
修复方法: 为消息所指的 importer 保留一个条目——其 uri 指向你想要的版本,并携带你想交给该 importer 的 with——删除另一个。如果两者位于不同文件中,应修改你控制的那个文件:删除你的条目即采用另一个文件的条目,而保留你的条目则意味着必须删除另一个文件中的条目。
A provider binding names a capability containing a colon(provider 绑定指定的能力包含冒号)
the provider socket binding for capability "<capability>": a Recipe’s capability reference is read as the capability up to its last colon and a version pin after it, so the capability a binding names carries no colon; bind the capability name alone and let each Recipe pin the version it needs: a provider socket binding names a capability containing a colon, which no Recipe can select(该 capability 的 provider 插槽绑定:Recipe 的 capability 引用被解读为最后一个冒号之前的 capability 名称和其后的版本锁定,因此绑定所指定的 capability 不含冒号;请只绑定 capability 名称,由各个 Recipe 锁定各自需要的版本:provider 插槽绑定指定了一个包含冒号的 capability,任何 Recipe 都无法选中它)
workspaceconfig: governance attachment "<uri>" declares no role; set role: to one of <the known roles>: a governance attachment declares no role or an unknown role(workspaceconfig:该 governance 挂载未声明角色;请将 role 设为已知角色之一:governance 挂载未声明角色或声明了未知角色)
角色无法识别时:
workspaceconfig: governance attachment "<uri>" declares unknown role "<role>"; use one of <the known roles>: a governance attachment declares no role or an unknown role(workspaceconfig:该 governance 挂载声明了未知角色;请使用已知角色之一:governance 挂载未声明角色或声明了未知角色)
registry alias "<alias>" matches <count> hosts (<hosts>); address the registry by host or remove the duplicate alias: registry alias matches more than one host(该 registry 别名匹配了多个主机;请按主机寻址该 registry,或删除重复的别名:registry 别名匹配了多个主机)
…: lockfile: file failed schema validation; run aggrega pull --release <release> to write it again from the Release(lockfile:文件未通过 schema 校验;请运行该命令,根据 Release 重新写入它)
完全为空的文档会单独报告,因为没有可以指出的字段:
lockfile: <path>: document is empty(lockfile:文档为空)
cyclic extends chain (<kind><name>, rule extends). <entity> extends <reference>, which is already in the chain; remove the extends on <entity>, or point it at an entity outside the chain(extends 链存在循环:该实体所扩展的引用已在链中;请删除该实体上的 extends,或将其指向链外的实体)
manifest mapping entry’s recipe spec.implements does not match the mapped component-type / feature-type key (manifest mapping "<component-type>" -> "<recipe-uri>", recipe spec.implements is "<recipe-implements>", expected "<component-type>", or a type "<component-type>" extends)(Manifest 映射条目所指 Recipe 的 spec.implements 与所映射的组件类型或特性类型键不匹配;期望值为该组件类型,或该组件类型所扩展的类型)
manifest mapping entry’s recipe spec.implements does not match the mapped component-type / feature-type key (Manifest, at .spec.components.<instance>, "<instance>", of type "<component-type>", compiled as "<component-type>:<version>", reached through manifest mapping key "<key>", mapped to recipe "<recipe-uri>", whose spec.implements is "<recipe-implements>"). map this type at this version to a recipe that implements it, with a mapping key naming the version(Manifest 映射条目所指 recipe 的 spec.implements 与所映射的组件类型 / 功能类型键不匹配(Manifest,该实例的类型与编译版本,经由该映射键到达,所映射的 recipe 的 spec.implements 不满足它)。请将此版本的此类型映射到实现它的 recipe,并使用指明该版本的映射键)
compiled as 值只会出现在类型未指明版本的实例上;指明了版本的实例会在 of type 中显示其版本。指明实例自身版本的键无需第二次判定,因为对条目的检查已经判定过它;已因其键被拒绝的条目只报告一次(如上所述),而不会针对每个实例再报告一次。aggrega build 和 aggrega pull 会因此中止,aggrega validate --release 会报告它并以非零状态退出。aggrega lint 判定的是 Manifest 的映射条目,而不是它们到达的实例,因此不会报告它。
malformed recipe reference in a Manifest mapping value: spec.mappings.components.type.<key> maps to <value>, which carries <n> slash-separated segments; a recipe reference accepts "name", "name:version", "capability/name" or "capability/name:version"; correct the mapping value in the Manifest(Manifest 映射值中的 recipe 引用格式错误:该映射值包含的斜杠分隔段过多;recipe 引用只接受名称、带版本的名称、带能力限定的名称或带能力限定且带版本的名称;请更正 Manifest 中的映射值)
features 部分会针对其自身坐标产生相同的消息,并将其称为 feature recipe 引用。
malformed recipe reference in a Manifest mapping value: spec.mappings.components.type.<key> maps to <value>, which carries a version pin in its capability segment <segment>; a pin belongs on the capability the recipe declares, and a recipe reference names the recipe by its bare capability, as "name", "name:version", "capability/name" or "capability/name:version"; correct the mapping value in the Manifest(Manifest 映射值中的 recipe 引用格式错误:该映射键映射到的值在其能力段中带有版本固定;版本固定应写在 recipe 声明的 capability 上,recipe 引用以裸能力名指明 recipe;请更正 Manifest 中的映射值)
你实际遇到的是针对 Manifest 未映射到任何对象的实例的停止,该停止会列出实现该类型的每个 Recipe,以便你固定其中一个,参见下文的“No Recipe is mapped for a component or feature instance(没有为组件或特性实例映射 Recipe)”。无论实现该类型的 Recipe 是一个还是五个,它的报告方式都相同,因此没有单独的歧义条件需要查找。
document envelope validation failed (Release, at <path>); <line>:<column>: spec.aggregate: value matches a shape that is not allowed here. correct the document to match its kind’s schema(文档信封验证失败(Release,位于上述路径及行列):spec.aggregate:值匹配了此处不允许的形态。请修正文档,使其符合其 kind 的 schema)
feature merge conflict: reconcile the Aggregate and Release declarations for the feature (Aggregate <name>, at .spec.components.<component>.features.<attachment>, "<aggregate-declared-type>", "<release-declared-type>")(功能合并冲突:请协调该功能在 Aggregate 与 Release 中的声明(Aggregate 声明的类型、Release 声明的类型))
连接所携带的附件同样如此。当 Aggregate 的连接条目与 Release 中同一连接的条目都在同一个槽位下写入附件并指定了不同的 Features 时,构建会在组合展平后于 Release 的条目处(即写入第二个类型的位置)停止,并列出两个类型、槽位、连接、插座和组件:
feature merge conflict: reconcile the Aggregate and Release declarations for the feature (Release <release-name>, at .spec.boundaries.<boundary>.components.<component>.uses.<socket>.<alias>, the Aggregate names "<aggregate-declared-type>", the Release names "<release-declared-type>", for the slot "<slot>", on the connection "<alias>", through socket "<socket>", of component "<component>"). Drop the type from the Release’s entry so it sizes the attachment the Aggregate declares, or name the same Feature in both documents.(feature 合并冲突:请协调该 feature 在 Aggregate 与 Release 中的声明(给出该 Release 及其条目路径、Aggregate 与 Release 各自指定的类型,以及所涉及的 slot、连接、socket 和 component)。请从 Release 的条目中删除该类型,使其为 Aggregate 声明的附件确定规格,或在两个文档中指定同一个 Feature。)
annotation binding does not resolve against its target Feature (Manifest, at .spec.mappings.features.annotations.<key>, "<key>", routes to Feature "<feature-uri>", which this build’s catalog does not hold; correct or publish the Feature named under "feature")(注解绑定无法针对其目标 Feature 解析(Manifest,该注解键路由到的 Feature 不在本次构建的目录中;请修正或发布 feature 字段下指定的 Feature))
发出的消息(schema 无法解析变体):
annotation binding does not resolve against its target Feature (Manifest, annotation binding routes to Feature "<feature-uri>", whose declared schema does not resolve: <resolution failure>)(注解绑定无法针对其目标 Feature 解析(Manifest,注解绑定路由到的 Feature 所声明的 schema 无法解析,并附上解析失败的原因))
annotation binding does not resolve against its target Feature (Manifest, at .spec.mappings.features.annotations.<key>, "<key>", routes to Feature "<feature-uri>", at pillar "<pillar>", and path "<path>", which that Feature does not declare a property for under "schema")(注解绑定无法针对其目标 Feature 解析(Manifest,该注解键路由到 Feature 的某个 pillar 和路径,而该 Feature 未在 schema 下为此路径声明属性))
**修复方法:**确认绑定的 feature: URI 存在于目录中,并与 Recipe implements: 中区分大小写的 URI 一致。如果未找到路径变体在 Feature schema 确实声明了的路径上触发,请确认点分路径的拼写(区分大小写)以及支柱名称(infra 还是 values)。
A bound annotation value does not conform to the target Feature’s schema(绑定的注解值不符合目标 Feature 的 schema)
annotation subkey does not conform to the target Feature’s schema at the routed pillar: annotation subkey <subkey> value <value> does not conform to Feature <feature-uri> spec.schema.<pillar>.<subkey>: <constraint failure>(注解子键在路由到的支柱上不符合目标 Feature 的 schema:该注解子键的值不符合该 Feature 在 spec.schema 中对应支柱与子键处的声明,并附约束失败信息)
发出的消息(未声明子键变体):
annotation subkey does not conform to the target Feature’s schema at the routed pillar: annotation subkey <subkey> is not declared at Feature <feature-uri> spec.schema.<pillar>.<subkey>(注解子键在路由到的支柱上不符合目标 Feature 的 schema:该注解子键未在该 Feature 的 spec.schema 中对应支柱与子键处声明)
该中止针对所写的注解触发,发生在注解展开为 Feature 附件之前,与它旁边的两个条件一样:上文的“A bound annotation value does not conform to the target Feature’s schema(绑定的注解值不符合目标 Feature 的 schema)”在 Feature 拒绝其值时拒绝绑定所路由的子键,下文的“An annotation routes through a pillar its authoring side may not use(注解经由其编写方不得使用的支柱路由)”则拒绝经由错误支柱路由的子键。没有任何绑定声明的键不属于此条件:没有任何东西路由它,构建会跳过它。
输出的消息,指明文档和编写注解的位置、子键、注解键以及绑定所路由的子键:
annotation subkey is not routed by the annotation’s binding (Release <release-name>, at .spec.boundaries.<boundary>.annotations, "<subkey>", written under annotation "<key>", whose binding routes only "<subkey>, <subkey>")(注解子键未被该注解的绑定路由(Release,该子键写在该注解下,而其绑定只路由所列的子键))
与相邻的几个条件一样,该中止针对按原样编写的注解引发,发生在它被展开为 Feature 附件之前,因此诊断信息会指明该值所在的文档和编写位置。每个你编写的注解只检查一次:写在边界或子系统上的值会在那里被拒绝一次,无论其中的组件是否采用它。构建中每一个这样的值都会被报告,而不仅是第一个。构建会依据编写注解的文档,将 Release 一侧的注解报告在 OPS_ERROR 标签下,将 Aggregate 一侧的注解报告在 DEVELOPER_ERROR 标签下。该条件为 a scalar annotation value does not route to exactly one path of its binding,这正是 aggrega explain 针对其代码打印的内容。
输出的消息,指明注解所在的文档和编写位置、注解键、值,以及绑定所路由的路径:
a scalar annotation value does not route to exactly one path of its binding (Release <release-name>, at .spec.boundaries.<boundary>.annotations, "<key>", carrying the bare value "<value>", whose binding routes "<path>, <path>, <path>")(标量注解值未能路由到其绑定中恰好一条路径:Release 中的该注解携带裸值,而其绑定路由的是所列路径)
annotation routes through a pillar its authoring side may not use: annotation <key> at <source> routes through pillar <pillar> at path <path>, but <side>-side annotations may only route through pillar <permitted-pillar>(注解经由其编写方不得使用的支柱路由:位于给定来源的该注解在给定路径上经由某一支柱路由,但该编写方的注解只能经由其被允许的支柱路由)
该检查覆盖标准的 schema 约束:类型错误的值(schema 声明为整数处给了字符串)、超出声明范围或 enum 的值、不满足声明的 pattern 的值、不是其声明的 format(命名格式之一)有效实例的字符串,以及未提供的必填字段。格式失败会指出关键字,并附带该值、格式及其问题——例如 aggrega pull 和 aggrega validate --release 对给定 :::: 的 uri 字段打印的 "format", "value \"::::\" is not a valid uri: a URI begins with a scheme followed by a colon, such as https:"。该检查感知默认值:schema 为其提供了 default: 的字段即使省略也视为已提供,因此带默认值的必填字段永远不会触发“缺失”检查。
authored pillar does not conform to its declared schema (Release probe, at .spec.boundaries.main.components.app.features.check.values.schema, values pillar does not conform to the Feature schema: missing required property: schema (required))
authored pillar does not conform to its declared schema (Aggregate <name>, at .spec.components.<component>.values.<field>, “values.<field>”, “<keyword>”, “<constraint failure>”)(编写的支柱不符合其声明的 schema)
authored pillar does not conform to its declared schema (Release <release-name>, at .spec.components.<component>.infra.<field>, “infra.<field>”, “<keyword>”, “<constraint failure>”)(编写的支柱不符合其声明的 schema)
authored pillar does not conform to its declared schema (Aggregate <name>, at .spec.components.<component>.features.<attachment>.values.<field>, values pillar does not conform to the Feature schema: <constraint failure>)(编写的支柱不符合其声明的 schema:values 支柱不符合该 Feature 的 schema)
authored pillar does not conform to its declared schema (Release <release-name>, at .spec.boundaries.<boundary>.components.<component>.features.<attachment>.infra.<field>, infra pillar does not conform to the Feature schema: <constraint failure>)(编写的支柱不符合其声明的 schema:infra 支柱不符合该 Feature 的 schema)
authored pillar does not conform to its declared schema (Release <release-name>, at .spec.boundaries.<boundary>.features.<attachment>.values.<field>, values pillar does not conform to the Feature schema: <constraint failure>)(编写的支柱不符合其声明的 schema:values 支柱不符合该 Feature 的 schema)
authored pillar does not conform to its declared schema (Aggregate <name>, at .spec.components.<component>.uses.<socket>.<alias>.values.<field>, “values.<field>”, “<keyword>”, “<constraint failure>”)(编写的支柱不符合其声明的 schema)
authored pillar does not conform to its declared schema (Aggregate <name>, at .spec.components.<component>.uses.<socket>.<alias>.features.<slot>.values.<field>, values pillar does not conform to the Feature schema: <constraint failure>)(编写的支柱不符合其声明的 schema:values 支柱不符合该 Feature 的 schema)
authored pillar does not conform to its declared schema (Release <release-name>, at .spec.components.<component>.uses.<socket>.<alias>.features.<slot>.values.<field>, values pillar does not conform to the Feature schema: <constraint failure>)(编写的支柱不符合其声明的 schema:values 支柱不符合该 Feature 的 schema)
authored pillar does not conform to its declared schema (Release <release-name>, at .spec.boundaries.<boundary>.components.<component>.uses.<socket>.<alias>.infra.<field>, “infra.<field>”, “<keyword>”, “<constraint failure>”)(编写的支柱不符合其声明的 schema)
消息按遇到失败的工具所报告的原样携带失败信息:对于编译失败,包括契约内的键、源代码行和出错的关键字;对于无法构建校验器的内容,包括校验器拒绝的位置;对于不在支持集合内的格式名称,包括字段、关键字 format、所写的名称以及所有支持的名称。socket 契约中的跨文档 $ref: 若其 SchemaLibrary 条目不在已加载的闭包中,在 aggrega validate 检查该实体或 Release 时也会导致同样的中止;在实体自身的 spec.schema 中,它按上文“A $ref: is not written in a form the compiler can resolve(引用未以编译器可解析的形式书写)”所述报告。aggrega pull 会为 Release 所需的库读取这两处,因此无论由两者中的哪一处引用,目录中缺失的库都会更早地使拉取停止,如“A reference names no entity the catalog holds(引用指向目录中不存在的实体)”(E0114)所述——而目录中存在的库,无论被哪一处引用,都会在锁文件中固定。
declared schema contract could not be compiled into a usable schema, so nothing was validated against it: correct the contract where it is declared, or remove it if the configuration it covers needs no validation. Component "<type>:<version>": spec.usesSchema.<socket>.valueSchema declares a schema no validator can be built from, so the values it constrains would go unmeasured: compactform at <key>:<line> (keyword "<keyword>"): unknown keyword(声明的 schema 契约无法编译为可用的 schema,因此未据此校验任何内容:请在声明处修正该契约,或在其覆盖的配置无需校验时将其移除。Component:spec.usesSchema 中某个 socket 的 valueSchema 声明了一个无法据以构建校验器的 schema,因此它所约束的值将无法得到衡量:compactform 位于所示的键和行(所示关键字):未知关键字)
以及 Component 的 values pillar 中一个不在支持集合内的格式名称:
declared schema contract could not be compiled into a usable schema, so nothing was validated against it: correct the contract where it is declared, or remove it if the configuration it covers needs no validation. Component "<type>:<version>": spec.schema.values declares a schema no validator can be built from, so the values it constrains would go unmeasured: validator/jsonschema: schema resolution failed (at values.<field>, keyword "format", format "<format>" is not supported; the supported formats are email, uri, hostname, ipv4, ipv6, uuid, date-time, date)(声明的 schema 契约无法编译为可用的 schema,因此未据此校验任何内容:请在声明处修正该契约,或在其覆盖的配置无需校验时将其移除。spec.schema.values 声明的 schema 无法构建校验器,因此其约束的值将不会被校验)
declared schema contract could not be compiled into a usable schema, so nothing was validated against it: correct the contract where it is declared, or remove it if the configuration it covers needs no validation. SchemaLibrary "<library>": schema "<entry>" names a format no validator can check, so the values it constrains would go unmeasured: validator/jsonschema: schema resolution failed (at <field>, keyword "format", format "<format>" is not supported; the supported formats are email, uri, hostname, ipv4, ipv6, uuid, date-time, date)(声明的 schema 契约无法编译为可用的 schema,因此未据此校验任何内容:请在声明处修正该契约,或在其覆盖的配置无需校验时将其移除。该 schema 指定了校验器无法检查的格式,因此其约束的值将不会被校验)
recipe source is an empty string, which names neither sourceless mode nor sourced mode (Recipe <name>:<version>, at .spec.source). omit the source field for sourceless mode, or name a non-empty path or URI for sourced mode(recipe 的 source 为空字符串,既未指定 sourceless 模式,也未指定 sourced 模式。若为 sourceless 模式,请省略 source 字段;若为 sourced 模式,请指定非空的路径或 URI)
同一条件也涵盖存在但无处可达的映射:一个具有可接受引用形态的值,指向目录中没有的 Recipe,包括该 Recipe 存在但版本与该值固定的版本不同的情况,以及其裸名称同时由两个能力提供的情况。两者都无法解析到一个可以说是作者所选的 Recipe。形态无法用任何引用表达的映射值会单独报告,见上文“Manifest mapping value is not a shape a recipe reference accepts(Manifest 映射值不是 recipe 引用所接受的形态)”,因此“某实体不存在”的判断只会针对本可以解析的引用作出。
针对组件实例发出的消息。当映射存在但指向不存在的内容时:
no recipe resolved for component/feature instance: add an explicit Manifest mapping for its type (Manifest, at .spec.components.<instance>, "<instance>", of type "<type>", mapped to recipe "<uri>"). correct the mapping value in the Manifest, or publish the recipe it names(未能为 component/feature 实例解析出 recipe:请为其类型添加显式的 Manifest 映射(上述 Manifest 位置、实例、类型及所映射的 recipe)。请更正 Manifest 中的映射值,或发布其所指定的 recipe)
当映射不存在而有实现该类型的 Recipes 时,它们会作为可供固定的候选列出:
no recipe resolved for component/feature instance: add an explicit Manifest mapping for its type (Manifest, at .spec.components.<instance>, "<instance>", of type "<type>", recipes implementing it "<recipe-uris>"). pin one of them in the Manifest(未能为 component/feature 实例解析出 recipe:请为其类型添加显式的 Manifest 映射(上述 Manifest 位置、实例、类型及实现该类型的 recipe)。请在 Manifest 中固定其中一个)
而当根本没有任何内容实现该类型时,就没有可列出的内容:
no recipe resolved for component/feature instance: add an explicit Manifest mapping for its type (Manifest, at .spec.components.<instance>, "<instance>", of type "<type>"). no recipe in the catalog implements this type; write one, then map the type to it(未能为 component/feature 实例解析出 recipe:请为其类型添加显式的 Manifest 映射(上述 Manifest 位置、实例及类型)。catalog 中没有任何 recipe 实现该类型;请编写一个,再将该类型映射到它)
no recipe resolved for component/feature instance: add an explicit Manifest mapping for its type (Manifest, at .spec.components.<instance>, "<instance>", of type "<type>"). no recipe the lockfile pins implements this type; with no catalog directory, the recipes searched are only those the lockfile pins, not a registry’s; pin one a registry publishes in the Manifest, or write one, then map the type to it(没有为组件/功能实例解析出任何配方:请在 Manifest 中为其类型添加显式映射(Manifest,位于所示位置,针对所示实例和类型)。lockfile 固定的配方中没有任何一个实现此类型;由于没有目录文件夹,搜索的配方仅限于 lockfile 固定的那些,而非 registry 中的;请在 Manifest 中固定一个 registry 发布的配方,或者编写一个,然后将该类型映射到它)
功能实例以自己的形式报告这些情况,每种情况都位于该条件的句子之后。Aggregate 中未写版本的功能类型会像组件类型一样,按构建编译它时所用的版本进行匹配——即目录中该 Feature 的最高版本——而指明 <type>:<version> 的消息指的是该版本的类型,也就是在目录中搜索的对象。当某个附加项的组件所映射到的 Recipe 已知时,FeatureRecipes 按该 Recipe 所绑定的能力加以区分:绑定到该组件能力的会优先提供,而绑定到其他能力的 FeatureRecipe 仍会渲染,作为组件输出旁边的独立输出,而不是渲染到组件输出之中;因此,当没有任何一个绑定到该组件的能力时,就改为提供那些。指向空处的映射显示为 feature "<instance>" (type "<type>"): the Manifest maps it to feature recipe "<uri>", which is not in the catalog。当有 FeatureRecipes 为该组件的能力实现该类型时,只列出这些:feature "<instance>" (type "<type>"); feature recipes implementing it for capability "<capability>", the capability its component's Recipe binds to: [<recipe-uris>]; pin one in the Manifest。当它们只为其他能力实现该类型时:feature "<instance>" (type "<type>"); no feature recipe in the catalog implements <type>:<version> for capability "<capability>", the capability its component's Recipe binds to; feature recipes implementing it for other capabilities: [<recipe-uris>]; pin one of those in the Manifest, and it renders as its own output beside the component's, or write one for "<capability>", then map the type to it。当根本没有任何一个实现该类型时:feature "<instance>" (type "<type>"); no feature recipe in the catalog implements <type>:<version>; write one, then map the type to it。而当能力未知时——组件自身的映射未解析到任何 Recipe(这一点会单独报告),或者附加项写在某个边界上,而该边界中的组件可能通过多种能力渲染——则列出每个实现者:feature "<instance>" (type "<type>"); feature recipes implementing it: [<recipe-uris>]; pin one in the Manifest。在未指定任何目录文件夹的工作区中,搜索的 FeatureRecipes 仅限于 lockfile 固定的那些:registry 中的那些不会被列出,而未为该类型映射任何条目的 Manifest 也不会固定任何条目。在这种情况下,关于缺失的说法针对的是已固定的内容而非目录,并且消息会明确说明这一点。当没有任何一个实现该类型时:feature "<instance>" (type "<type>"); no feature recipe the lockfile pins implements <type>:<version> for capability "<capability>", the capability its component's Recipe binds to; with no catalog directory, the feature recipes searched are only those the lockfile pins, not a registry's; pin one a registry publishes in the Manifest, where one for another capability renders as its own output beside the component's, or write one for "<capability>", then map the type to it——而当能力未知时,消息不指明任何能力,并以 pin one a registry publishes in the Manifest, or write one, then map the type to it 结尾。当已固定的 FeatureRecipes 只为其他能力实现该类型时,该情况的消息会以 no feature recipe the lockfile pins implements 代替 no feature recipe in the catalog implements,能力之后的从句相同。
a Manifest name mapping’s key names no component instance or attachment in this build, so the entry binds nothing: Manifest "<manifest>", key "<component>" under mappings.features.name: no attachment in this build is named "<component>"; a features.name key names an attachment by its own name — the key it is written under in a component’s features, or <alias>.<slot> for one written on a connection — never the component it is attached to; attachments of type "<feature-type>" in this build: "<attachments>"; "<component>" is a component, and a features.name key names the attachment rather than the component it is attached to — did you mean "<attachment>"?(Manifest 的 name 映射的键未指向此构建中的任何组件实例或附件,因此该条目不绑定任何内容:Manifest 的 mappings.features.name 下的该键:此构建中没有以此命名的附件;features.name 键按附件自身的名称指向附件——即它在组件的 features 中所写的键,或对写在连接上的附件为别名加槽位——绝不指向它所附加的组件;此构建中该类型的附件如上所列;该名称是一个组件,而 features.name 键指向的是附件,而不是它所附加的组件——你想写的是否是所示附件?)
以及针对与某个实例名称只差一次编辑的 components.name 键:
a Manifest name mapping’s key names no component instance or attachment in this build, so the entry binds nothing: Manifest "<manifest>", key "<key>" under mappings.components.name: no component instance in this build is named "<key>"; a components.name key names a component instance exactly as the Aggregate writes it; component instances of type "<component-type>" in this build: "<instances>"; did you mean "<instance>"?(Manifest 的 name 映射的键未指向此构建中的任何组件实例或附件,因此该条目不绑定任何内容:Manifest 的 mappings.components.name 下的该键:此构建中没有以此命名的组件实例;components.name 键按 Aggregate 中所写的名称原样指向组件实例;此构建中该类型的组件实例如上所列;你想写的是否是所示实例?)
每个不指向任何内容的键都会在一次构建中报告,顺序与 Manifest 中的书写顺序一致。
**如何修复:**将该键重命名为消息建议的名称,或其列出的名称之一——对于附件,应使用它所写在其下的名称,而不是其组件的名称。如果不再需要该条目,就将其删除;该类型的实例随后会通过 type 层解析。
A Manifest maps two version-distinct keys onto one type(某个 Manifest 将两个版本不同的键映射到同一类型)
manifest maps multiple version-distinct keys to the same base type; the type-to-recipe lookup is ambiguous: type "<type>" matches version-distinct keys [<keys>] — pin the authored type’s version or remove the duplicate mapping keys(manifest 将多个版本不同的键映射到同一基础类型;类型到 recipe 的查找存在歧义:该类型匹配了上述多个版本不同的键——请固定所编写类型的版本,或删除重复的映射键)
**工作区的制品缓存也以同样方式约束,读取时与写入时一致。**从 artifact_cache_dir 下的缓存中读取的所有内容——缓存的实体、插件或库及其旁边的 manifest、源归档及其元数据、固定的外部输入、签名包、注册表的本地搜索索引——以及 aggrega cache status、aggrega cache prune 和 aggrega cache clear 列出的每个工作区条目,都受限于写入缓存时所受限的目录:缓存目录本身,默认的 .aggrega/cache 与配置指定的、越出工作区根目录的缓存目录同样如此。其中任何指向缓存目录之外的链接——无论指向工作区内其他位置还是任何别处——都不会被读取;写在工作区根目录内、但自身是指向工作区之外的链接的缓存目录,其后的任何内容也不会被读取:build、pull、validation、search、这三个缓存命令,以及编辑器和助手读取缓存的请求都会停止并指出该链接——缓存以记录的摘要保存的内容也不例外,因为摘要说明的是字节是什么,而不是可以从哪里读取。写在工作区根目录内、指向工作区内其他位置的缓存目录,会在其指向的位置被读取。aggrega inspect 打印的弃用通知不决定任何事,因此不在此列。prune 或 clear 若遇到缓存自身的某个目录是指向缓存目录之外的链接,或缓存目录自身是指向工作区之外的链接,会在列出任何内容之前,将其视为它将要执行的删除,按 “A path the operation writes leads through a link out of the directory it must stay inside(操作写入的路径经由链接通向其必须限定的目录之外)” 处理。此消息给出的补救措施针对缓存:移除链接后,pull 会重新填充缓存;保存在别处的缓存应通过相对于工作区根目录的 artifact_cache_dir 指定,而不是通过链接访问。
**源获取的仓库受限于其自身的检出目录。**当 pull——aggrega pull,或解析 Release 依赖项的 build、编辑器或助手的请求——获取 git-repository 源时,会检出该仓库并归档源所指定的目录,而检出目录是独立的目录:仓库携带的每个链接,包括 module_subdir 本身,都受限于它。指向仓库内文件或目录的链接会以链接的名称归档为其所指向的内容。指向仓库之外的链接——它可能指向运行 pull 的机器上的任何文件——不会被读取:pull 会停止并指出该链接及其指向的位置,且不缓存任何内容。检出目录是 pull 停止后即被删除的临时目录,因此消息按链接在仓库中的位置指出该链接——chart/secret.txt,出现在命令行第一行和句子中——并将其必须限定的目录表述为源所指定的仓库和修订版本:which must stay inside the repository <url> at <ref> (commit <commit>),若源未指定 ref 或直接指定了提交本身,则为 at commit <commit>。链接指向的位置则按它在你机器上的实际位置给出。此消息给出的补救措施针对仓库:链接是在那里提交的,因此要在那里修改——使其指向仓库内部,或替换为文件本身——然后让源指定包含该修改的修订版本。若目录链接指回归档已经通过它读取的目录,pull 也会停止,因为它所代表的树没有尽头;这种拒绝是普通错误,而不是此条件。
名称(而非路径)不在此处判定——aggregate: payments、extends: base-manifest。它会在 Release 旁的文档中查找,对于 Aggregate 还会在目录(catalog)目录中查找,这些目录受上文 “A file the operation reads leads through a link out of the directory it must stay inside(操作读取的文件通过链接指向了它必须留在其中的目录之外)” 中的规则约束。
a reference a document makes to another file leads out of the directory it must stay inside (.spec.aggregate: ../shared/app.yaml, resolved from <workspace>, which leads to <elsewhere>/shared/app.yaml, outside the workspace <workspace>). nothing was read from that file. A document in the workspace reaches only files inside <workspace>: move the file there — or, where a link carries the reference out, make the link lead there — or open the workspace at a directory holding both documents. An Aggregate kept outside that directory is reached by its name rather than a path, from a catalog directory the workspace configuration lists(文档对另一文件的引用指向了它必须留在其中的目录之外(该引用从工作区解析,指向工作区之外的位置)。没有从该文件读取任何内容。工作区中的文档只能访问工作区内的文件:将该文件移到工作区内——或者,在由链接把引用带出的情况下,让该链接指向工作区内——或者在同时包含这两个文档的目录处打开工作区。保存在该目录之外的 Aggregate 通过其名称而非路径,从工作区配置列出的目录目录中访问)
对于在工作区之外指定的 Release 或 Manifest,其自身目录即是它必须留在其中的目录:
a reference a document makes to another file leads out of the directory it must stay inside (.spec.aggregate: ../aggregates/app.yaml, resolved from <directory>, which leads to <parent>/aggregates/app.yaml, outside <directory>, the directory of a document named outside the workspace <workspace>). nothing was read from that file. A Release or a Manifest named outside the workspace — on the command line, or by the workspace configuration — reaches only files inside its own directory <directory>: move the file there — or, where a link carries the reference out, make the link lead there — or name the document from a workspace holding both documents. An Aggregate kept outside that directory is reached by its name rather than a path, from a catalog directory the workspace configuration lists(文档对另一文件的引用指向了它必须留在其中的目录之外(该引用从在工作区之外指定的文档所在目录解析,指向该目录之外的位置)。没有从该文件读取任何内容。在工作区之外指定的 Release 或 Manifest——无论是在命令行上,还是由工作区配置指定——只能访问其自身目录内的文件:将该文件移到该目录内——或者,在由链接把引用带出的情况下,让该链接指向该目录内——或者从同时包含这两个文档的工作区中指定该文档。保存在该目录之外的 Aggregate 通过其名称而非路径,从工作区配置列出的目录目录中访问)
对于 extends: 或 parameters 的 $import:,引用之后会附上 written in <document>;若是链接将路径带出,末尾会附上 the link <link> leads to <place>。aggregate: 或 manifest: 引用不给出文档:扩展另一个 Release 的 Release 可能从链上更上层的 Release 继承了它,无论哪种情况,它都相对于命令所指定的 Release 解析。
no catalog version satisfies the referenced version constraint: entity "<reference>" (referenced from <referring paths>)(没有任何目录版本满足所引用的版本约束:所示实体,以及引用它的位置)
发出的消息,针对 extends: 指针上的版本固定:
no catalog version satisfies the referenced version constraint (Component <name>, at .extends, no catalog version satisfies extends parent "<reference>")(没有目录版本满足所引用的版本约束:该 Component 的 extends 父项引用没有可满足的目录版本)
它在报告引用解析失败的位置报告,因此格式错误的锁定永远不会改变哪些引用能够解析,只会改变失败信息的内容。格式正确但没有可用版本满足的锁定,仍保持该处为其报告的条件:上文的“No catalog version satisfies a version constraint(没有目录版本满足版本约束)”,或所在位置的未找到条件。
reference carries a malformed version pin (reference "<reference>", pin "<pin>", the text after ^ is not a version range, referenced from <authored location>). write the reference as , as : with a semantic version such as 1.0.0, or as :^ for the highest version compatible with it(引用带有格式错误的版本锁定:^ 之后的文本不是版本范围。请将引用写为仅名称、名称加语义化版本(如 1.0.0),或名称加 ^ 和版本以选择与之兼容的最高版本)
精确锁定会以 an exact pin must be a semantic version 代替 caret 子句。其后的值说明引用写在何处,用词取决于报告它的位置:referenced from 加编写位置、in the Release's spec.aggregate 或 in the recipe's spec.implements。当 Manifest 映射与其 Recipe 的 implements: 进行比对时,映射条目以及其中哪一侧带有锁定(in the mapping key 或 in the recipe's spec.implements)会改为出现在引用之前;Component 或 Feature 的 extends: 则在其前面写出扩展的实体和字段。
**如何修复:**将锁定改写为两种形式之一,或删除锁定以选择可用的最高版本。通配符如 1.x 应写为 caret 锁定 ^1.0.0;带前导 v 或少于三个数字的版本应写完整,即 1.0.0。
Every version a reference could select has been withdrawn(引用可选择的每个版本都已撤回)
every published version this reference could select has been withdrawn: <reference>: withdrawn: <version> (<recorded reason>), <version> (<recorded reason>)(该引用可选择的每个已发布版本均已被撤回,并列出各版本及其记录的原因)
**无论是否有 Recipe 请求该能力,都会对其进行判定。**否则,只有当 Recipe 的 capability: 指定某个绑定时才会读取它,于是能力拼写错误的绑定既不会被查阅,也不会被报告。因此,每次构建和每次 aggrega validate --release 都会检查每个指定了插件的绑定:无论是否有 Recipe 使用,pull 都会解析这样的绑定,因此构建持有该插件并知道它提供什么,而该插件不提供的能力必定是错误的。该检查读取的是工作区配置中的绑定,而不是 lockfile,并且不会改变由哪个插件渲染 Recipe,这仍由 lockfile 决定。指定了构建未持有的插件(尚未被任何 pull 获取的注册表插件)的绑定,在 pull 获取它之前不会被判定。未指定插件的绑定则以另一种方式判定,作为建议:参见下文“Conditions that do not halt a build”下的“A provider binding names a capability no plugin the build reads serves(provider 绑定指定的能力不由构建所读取的任何插件提供)”。
发出的消息,会补充所指定插件实际提供的能力,以及当绑定的能力与之只差一次编辑时的相应拼写:
plugins.providers entry names a plugin no provider-rendering plugin serving the capability matches: capability "<capability>" is bound to plugin "<plugin-identity>", but no provider-rendering plugin serving "<capability>" matches that identity; "<plugin-identity>" serves "<served capability>", and "<capability>" is one edit from "<served capability>"(plugins.providers 条目指定的插件与任何提供该能力的 provider 渲染插件都不匹配;消息还会给出所指定插件实际提供的能力,以及相差一处编辑的拼写)
当绑定指定的插件不在构建所读取的目录中时,消息在“matches that identity”之后结束,因为关于它提供什么已无可说明。
no provider-rendering plugin version satisfies the recipe’s provider version pin: capability "<capability>" pins "<version>" but no provider-rendering plugin serves it
no provider-rendering plugin version satisfies the recipe’s provider version pin: capability "<capability>" pins "<version>" but no serving plugin version satisfies it
no parser plugin advertises the requested format: no parser plugin advertises "parse:<format>"
no importer plugin advertises the requested format: no importer plugin advertises "import:<format>"
format is advertised by more than one parser plugin: format "<format>" is advertised by parser plugins [<plugin-names>]
format is advertised by more than one importer plugin: format "<format>" is advertised by importer plugins [<plugin-names>]
这与上文所述的没有导入器声明该格式不同:这里的导入器在导入可选范围内且声明了该格式,缺少的只是条目所指定的版本。不属于任何版本固定形式的固定值(例如 :latest)则会被报告为格式错误,如“A version pin is none of the forms a pin takes(版本固定值不属于任何固定形式)”所述。
输出的消息,指明该格式的能力以及条目固定的版本:
no importer plugin version satisfies the plugins.importer entry’s version pin: capability "import:<format>" pins "<version>" but no serving plugin version satisfies it(没有导入器插件版本满足 plugins.importer 条目的版本固定:该能力固定了某个版本,但没有提供服务的插件版本满足它)
**修复方法:**将条目 uri 中的版本改为目录中持有的版本(对于核心导入器,编译器自身的版本也算一个),或放宽范围,或将条目指定的版本添加到目录中。脱字符范围匹配同一主版本内不低于其下限的版本,因此无论 1.x 导入器多新,都不满足 ^2.0.0。
A plugin reference carries a registry host or an artifact path(插件引用带有注册表主机或制品路径)
Plugin 引用以形如注册表主机的段开头——包含点或冒号,如 DNS 名称或主机加端口——或以制品路径开头。Plugin 通过其坐标身份寻址:插件类型、斜杠、名称,以及可选的版本。拉取时会加上所配置的注册表和插件路径作为前缀,从而将该身份绑定到物理位置,因此已带有这些内容的引用会被加两次前缀,绑定到一个无法获取的位置。
catalog: tier-3 pull <uri>: wasm plugin reference must be the plugin coordinate identity (<pluginType>/<name>:<version>), not a registry-qualified or artifact path: "<identity>"(目录:第 3 层拉取:wasm 插件引用必须是插件坐标标识,而不是带注册表限定的路径或制品路径)
remediation: remove the registry host and the artifact path, leaving the coordinate alone — <pluginType>/<name>:<version>, for example provider/helm:1.0.0; the pull prefixes the configured registry itself, so a reference that already carries one is prefixed twice(修复建议:删除注册表主机和制品路径,只保留坐标;拉取会自行添加所配置注册表的前缀,因此已带有前缀的引用会被重复添加前缀)
catalog: tier-3 pull <uri>: wasm plugin reference must carry a pluginType scope (<pluginType>/<name>); an empty scope cannot bind to an OCI location: "<identity>"(目录:第 3 层拉取:wasm 插件引用必须带有 pluginType 作用域;空作用域无法绑定到 OCI 位置)
remediation: add the missing pluginType segment — write the reference as <pluginType>/<name>, for example provider/helm or governance/redact, using the pluginType the plugin entity declares under metadata.pluginType(修复建议:补上缺失的 pluginType 段,使用插件实体所声明的 pluginType)
catalog: tier-3 pull <uri>: recipe reference must be provider-scoped (<provider>/<name>); an empty provider cannot bind to an OCI location: "<identity>"(目录:第 3 层拉取:recipe 引用必须带有 provider 作用域;空 provider 无法绑定到 OCI 位置)
remediation: no local catalog directory held this reference, so it was looked for in the registry, where a provider segment is required; re-run as aggrega pull --release <release> --catalog <dir> so the directory that holds it is searched first (--catalog is repeatable)(修复建议:没有本地目录包含此引用,因此在注册表中查找,而注册表要求 provider 段;请指定包含它的目录重新运行,使该目录优先被搜索,该参数可重复使用)
deprecation: <reference> is retracted: <the publisher's recorded message> (recorded in the lockfile at pull, as of <when>; re-run `aggrega pull` to refresh it)
deprecation: build consumes a deprecated entity: <reference> is retracted: <the publisher's recorded message> (recorded in the lockfile at pull, as of <when>; re-run aggrega pull to refresh it): halt_on_deprecated_severity is "error"
resolve cached plugin "<plugin-identity>": the digest recorded as trusted for it is <recorded-digest>, but the plugin manifest in the content cache reports <cached-digest>; review what changed and re-record the trusted digest, or restore the recorded artifact: the digest recorded as trusted for this plugin does not match the digest its cached manifest reports
inheritance merge failed (Component <name>, at .spec.extends, <entity> extends <reference>, which no catalog entity provides). Verify the extends reference names an entity present in the catalog(继承合并失败:该实体所扩展的引用没有任何 catalog 实体提供。请确认 extends 引用指向 catalog 中存在的实体)
当报告该问题的检查按 lockfile 的 pin 从制品缓存中读取父级时——即构建和 aggrega validate --release 的 extends 检查、针对整个目录的 aggrega validate、aggrega inspect,以及从编辑器和助手的 validate 工具运行的相同检查——建议还会进一步指明 pull:“a base published to a registry is fetched by aggrega pull --release <release>”(发布到注册表的基础实体通过所示命令获取)。验证单个实体文件不读取 lockfile,因此 pull 不会改变它读取的任何内容,其消息止于目录。
inheritance merge failed (Manifest <name>, at .spec.extends, <entity> extends <reference>, which could not be resolved: <what looking produced>). Verify the extends reference is a relative path or the name of a Manifest in the Release’s directory(继承合并失败:该实体所扩展的引用无法解析。请确认 extends 引用是相对路径,或是 Release 所在目录中某个 Manifest 的名称)
inheritance merge failed (Release <name>, at .spec.extends, <entity> extends <reference>, which could not be resolved: <what looking produced>). Verify the extends reference is a relative path to a Release file, such as ./base-release.yaml, resolved from the directory holding this Release(继承合并失败:该实体所扩展的引用无法解析。请确认 extends 引用是指向某个 Release 文件的相对路径,例如 ./base-release.yaml,并从包含此 Release 的目录解析)
extends chain exceeds maximum depth (Component <name>, rule extends). the bound is 10 and this chain reaches <length>; shorten the chain, or extend a base that sits closer to its root(extends 链超出最大深度:上限为 10,而此链超出了该上限;请缩短该链,或扩展一个更靠近根的基础实体)
assertion name declared twice across the extends chain (Component <name>:<version>, rule assertions, at .spec.assertions.<key>). assertion "<key>" is already declared by the base Component "<base>", carrying a different rule; rename the extending entity’s assertion; an extending entity’s assertions add to the base’s and never replace one(断言名称在 extends 链中被声明了两次:该断言已由基础 Component 以不同的规则声明;请重命名扩展实体的断言;扩展实体的断言是对基础实体断言的补充,从不替换其中任何一个)
release extends chain composes both named boundaries and top-level components: declare one routing shape across the chain, never both (Release <release-file>, boundaries declared by "<file>", components declared by "<file>")(release extends 链同时组合了命名边界和顶层组件:在整条链中声明一种路由形态,切勿两者兼用;依次指出 Release 文件、声明边界的文件和声明组件的文件)
externalinputs: "<url>": plain http is allowed for loopback hosts only (allowed schemes: https, http to a loopback host, oci): externalinputs: URL scheme is not allowed(仅允许对回环主机使用明文 http(允许的协议:https、指向回环主机的 http、oci):URL 协议不被允许)
externalinputs: "<url>": scheme "<scheme>" is not allowed (allowed schemes: https, http to a loopback host, oci): externalinputs: URL scheme is not allowed(协议不被允许(允许的协议:https、指向回环主机的 http、oci):URL 协议不被允许)
"<url>" is not pinned in the lockfile; run aggrega pull --release <release> to pin every external input this Release’s render consumes, then build again: externalinputs: acquisition is disabled for unpinned inputs(该 URL 未在 lockfile 中固定;请运行该命令以固定此 Release 渲染所使用的每个外部输入,然后重新构建:对未固定的输入禁止获取)
externalinputs: "<url>": store blob sha256 is <digest>, pinned digest is <digest>: externalinputs: store blob mismatches its pinned record(存储 blob 的 sha256 与固定的摘要不一致:存储 blob 与其固定记录不匹配)
externalinputs: "<url>": store blob sha256/<digest> is <n> bytes but the pinned record says <n>: externalinputs: store blob mismatches its pinned record(存储 blob 的字节数与固定记录不一致:存储 blob 与其固定记录不匹配)
the compiler’s own views of the catalog disagree (internal error: this build resolved a component type that the catalog it reads then held no entry for. This is a fault in the compiler rather than in an authored document, so there is nothing to correct in the Aggregate, the Release or the catalog. Please report it, naming the command that produced this build and the type the views disagree on: "<type>")(编译器自身的目录视图存在分歧(内部错误:本次构建解析了一个组件类型,而它随后读取的目录中没有该类型的条目。这是编译器的故障,而不是所编写文档的问题,因此 Aggregate、Release 或目录中都没有需要更正的内容。请报告此问题,并注明产生本次构建的命令以及视图存在分歧的类型))
resolve: no entity in the catalog matches this URI: entity "<reference>" (referenced from <referring paths>)(resolve:目录中没有与此 URI 匹配的实体:该实体及引用它的位置见前文)
针对库:
resolve: no entity in the catalog matches this URI: library "<reference>"(resolve:目录中没有与此 URI 匹配的实体:所示库)
以及针对绑定到 provider 插槽的插件,它以承载它的工作区配置键命名,而不是以目录文档命名:
resolve: no entity in the catalog matches this URI: entity "<reference>" (referenced from .aggrega-config.yaml.plugins.providers)(resolve:目录中没有与此 URI 匹配的实体:所示实体,引用自 .aggrega-config.yaml.plugins.providers)
resolve: invalid library reference URI: "<the value as written>"(resolve:无效的库引用 URI:所示为按原样写出的值)
以及在使用 @ 作为分隔符时,引用该值应有的写法:
resolve: invalid library reference URI: version separator is ’:’, not ’@’ — use "<the corrected value>"(resolve:无效的库引用 URI:版本分隔符是 ’:‘,而不是 ’@‘——请使用所示的更正后的值)
annotation-transform plugin output was rejected: an injection targets a component coordinate the host did not supply, or carries a value that is not a string or an object of subkeys: injection targets boundary "<boundary>" component "<component>" (annotation "<key>")(注解转换插件的输出被拒绝:某次注入的目标是宿主未提供的组件坐标,或携带的值既不是字符串也不是由子键组成的对象:注入的目标为所示边界中的所示组件(所示注解)) annotation-transform plugin output was rejected: an injection targets a component coordinate the host did not supply, or carries a value that is not a string or an object of subkeys: injection for boundary "<boundary>" component "<component>" (annotation "<key>") carries a list; an injected annotation value is a string or an object of subkeys(注解转换插件的输出被拒绝:某次注入的目标是宿主未提供的组件坐标,或携带的值既不是字符串也不是由子键组成的对象:针对所示边界中所示组件(所示注解)的注入携带了一个列表;注入的注解值应为字符串或由子键组成的对象)
plugin reference is not a Plugin entity: "<reference>" is a filesystem path, but a pipeline plugin must be a plugin-type-scoped Plugin entity URI (<pluginType>/<name>, optionally versioned, as in parser/yaml or parser/yaml:1.0.0)(插件引用不是 Plugin 实体:该引用是文件系统路径,但流水线插件必须是以插件类型为作用域的 Plugin 实体 URI,可带版本,格式如上所示)
制品引用:
plugin reference is not a Plugin entity: "<reference>" is an artifact reference (an oci:// scheme, a bare .wasm, or an @sha256: digest), but a pipeline plugin must be a plugin-type-scoped Plugin entity URI (<pluginType>/<name>, optionally versioned, as in parser/yaml or parser/yaml:1.0.0)(插件引用不是 Plugin 实体:该引用是制品引用(OCI 协议、裸 Wasm 文件或 SHA-256 摘要),但流水线插件必须是以插件类型为作用域的 Plugin 实体 URI,可带版本,格式如上所示)
无人持有的 Plugin 实体 URI:
plugin reference is not a Plugin entity: "<reference>" is a Plugin entity URI, but no catalog directory holds the entity it names, the binary does not carry it, and no pull has fetched it into the content cache; place the Plugin entity in a catalog directory, or publish it to a registry and run aggrega pull(插件引用不是 Plugin 实体:该引用是 Plugin 实体 URI,但没有任何目录目录包含它所指的实体,编译器二进制文件中也不带该实体,且没有任何拉取将其获取到内容缓存中;请将该 Plugin 实体放入目录目录,或将其发布到注册表后运行上述拉取命令)
以及其他任何未指向实体的引用——没有插件类型作用域、在版本之前有多个 /,或带有注册表主机:
plugin reference is not a Plugin entity: "<reference>" must be a plugin-type-scoped Plugin entity URI (<pluginType>/<name>, optionally versioned, as in parser/yaml or parser/yaml:1.0.0); a bare .wasm reference or an artifact reference names no Plugin entity(插件引用不是 Plugin 实体:该引用必须是以插件类型为作用域的 Plugin 实体 URI,可带版本,格式如上所示;裸 Wasm 文件引用或制品引用不指向任何 Plugin 实体)
artifact "<reference>": cached signature bundle <path> is unreadable: cached signature bundle does not match its recorded digest. remediation: run aggrega pull --release <release> to verify the artifact’s signature at its registry again, record it in <file> and cache the bundle it names(制品:缓存的签名包不可读:缓存的签名包与其记录的摘要不匹配。修复:运行上述命令,在制品的注册表重新验证其签名,将其记录到上述文件中,并缓存其指定的签名包)
以及发生偏移时:
artifact "<reference>": cached signature bundle <path> has digest <actual>, recorded digest is <recorded>: cached signature bundle does not match its recorded digest. remediation: run aggrega pull --release <release> to verify the artifact’s signature at its registry again, record it in <file> and cache the bundle it names(制品:缓存的签名包的摘要与记录的摘要不同:缓存的签名包与其记录的摘要不匹配。修复:运行上述命令,在制品的注册表重新验证其签名,将其记录到上述文件中,并缓存其指定的签名包)
以及从内容缓存加载插件字节时,还会指明其来源:
plugin "<reference>" resolved from <source>: cached signature bundle <path> is unreadable: cached signature bundle does not match its recorded digest. remediation: run aggrega pull --release <release> to verify the artifact’s signature at its registry again, record it in <file> and cache the bundle it names(插件从上述来源解析:缓存的签名包不可读:缓存的签名包与其记录的摘要不匹配。修复:运行上述命令,在制品的注册表重新验证其签名,将其记录到上述文件中,并缓存其指定的签名包)
plugin "<reference>" resolved from <source>: cached signature bundle <path> has digest <actual>, recorded digest is <recorded>: cached signature bundle does not match its recorded digest. remediation: run aggrega pull --release <release> to verify the artifact’s signature at its registry again, record it in <file> and cache the bundle it names(插件从上述来源解析:缓存的签名包的摘要与记录的摘要不同:缓存的签名包与其记录的摘要不匹配。修复:运行上述命令,在制品的注册表重新验证其签名,将其记录到上述文件中,并缓存其指定的签名包)
verify: "<reference>" records a signature a build does not accept, and no registry is configured to ask about it again: cached signature bundle <path> is unreadable: cached signature bundle does not match its recorded digest(验证:该引用记录了构建不接受的签名,且未配置可重新查询的注册表:缓存的签名包不可读:缓存的签名包与其记录的摘要不匹配)
artifact "<reference>": signing: the recorded signature was made for a different artifact (<file> records it, cached signature bundle <path>, the artifact read has manifest <manifest-digest>). remediation: run aggrega pull --release <release> to verify the artifact’s signature at its registry again, record it in <file> and cache the bundle it names(工件:签名:记录的签名是为另一个工件生成的(由所示文件记录,所示缓存签名 bundle,所读工件具有所示 manifest)。修复方法:运行所示 pull 命令,在工件的注册表中重新验证其签名,将其记录到所示文件中,并缓存其指向的 bundle)
以及在加载插件字节时,还会指明其来源:
plugin "<reference>" resolved from <source>: signing: the recorded signature was made for a different artifact (<file> records it, cached signature bundle <path>, the artifact read has manifest <manifest-digest>). remediation: run aggrega pull --release <release> to verify the artifact’s signature at its registry again, record it in <file> and cache the bundle it names(从所示来源解析的插件:签名:记录的签名是为另一个工件生成的(由所示文件记录,所示缓存签名 bundle,所读工件具有所示 manifest)。修复方法:运行所示 pull 命令,在工件的注册表中重新验证其签名,将其记录到所示文件中,并缓存其指向的 bundle)
verify: "<reference>" records a signature a build does not accept, and no registry is configured to ask about it again: signing: the recorded signature was made for a different artifact (cached signature bundle <path>, the artifact read has manifest <manifest-digest>)(验证:所示引用记录了构建不接受的签名,且未配置可再次查询的注册表:签名:记录的签名是为另一个工件生成的(所示缓存签名 bundle,所读工件具有所示 manifest))
signing: no verified signature is recorded for an artifact that requires one ("<reference>", <lockfile-path> records no signature for it, required by <the settings that require it>). remediation: run aggrega pull --release <release> to verify the artifact’s signature at its registry and record it in <lockfile-path>(签名:要求签名的制品未记录经过验证的签名(锁文件未为该制品记录签名,由相应设置要求)。修复:运行 pull 命令,在制品的注册表处验证其签名并将其记录到锁文件中)
对于附加在 verdict 角色上的插件,列出其记录:
signing: no verified signature is recorded for an artifact that requires one ("<plugin>", <record-path> records no signature for it, required by <the settings that require it>). remediation: run aggrega pull --release <release> to verify the plugin’s signature at its registry and record it in <record-path>(签名:要求签名的制品未记录经过验证的签名(信任记录未为该插件记录签名,由相应设置要求)。修复:运行 pull 命令,在插件的注册表处验证其签名并将其记录到信任记录中)
设置以配置文件自身的措辞命名: `signing.required` at the top level of the workspace configuration、 `signing.required` on the `registries` entry for "<host>" 或 the official hub's built-in signature requirement for "hub.aggrega.ai",适用多项时会连在一起列出。
signing: a recorded signature is not the one a pull would record ("<reference>", <file> records <signature>, a pull would record <signature>). remediation: run aggrega pull --release <release> to bring <file> up to date(签名:已记录的签名与 pull 将记录的签名不一致(该条目所在文件记录了一个签名,而 pull 将记录另一个签名)。修复方法:运行该 pull 命令,使该文件保持最新)
对于在要求签名处未记录签名的条目(锁文件条目,或在离线模式下插件信任记录中的条目):
signing: a recorded signature is not the one a pull would record ("<reference>", <file> records no signature, a pull would ask its registry for the signature a requirement asks for and record it). remediation: run aggrega pull --release <release> to bring <file> up to date(签名:已记录的签名与 pull 将记录的签名不一致(该文件未记录签名,pull 将向其 registry 请求某项要求所需的签名并记录下来)。修复方法:运行该 pull 命令,使该文件保持最新)
对于其记录的签名是为另一个制品所做的条目(锁文件条目,或在离线模式下插件信任记录中的条目):
signing: a recorded signature is not the one a pull would record ("<reference>", <file> records <signature>, made for another artifact, a pull would ask its registry for this artifact’s own signature and record it). remediation: run aggrega pull --release <release> to bring <file> up to date(签名:已记录的签名与 pull 将记录的签名不一致(该文件记录的签名是为另一个制品生成的,pull 将向其 registry 请求该制品自身的签名并记录下来)。修复方法:运行该 pull 命令,使该文件保持最新)
signing: a recorded signature is not the one a pull would record ("<plugin>", <record-path> records no entry for it and a signature is required for it, a pull would record <signature>). remediation: run aggrega pull --release <release> to bring <record-path> up to date(签名:已记录的签名与 pull 将记录的签名不一致(该记录文件中没有该插件的条目,而该插件需要签名,pull 将记录一个签名)。修复方法:运行该 pull 命令,使该记录文件保持最新)
signing: a recorded signature is not the one a pull would record ("<plugin>", <record-path> records no entry for it and a signature is required for it, a pull would ask its registry for the signature a requirement asks for and record it). remediation: run aggrega pull --release <release> to bring <record-path> up to date(签名:已记录的签名与 pull 将记录的签名不一致(该记录文件中没有该插件的条目,而该插件需要签名,pull 将向其 registry 请求某项要求所需的签名并记录下来)。修复方法:运行该 pull 命令,使该记录文件保持最新)
<signature> 以签名的模式、签名者及其签名包的摘要来表述签名,即 a keyed signature by keyed:sha256:<fingerprint> with bundle digest sha256:<digest>,对于无密钥签名,会在签名者之后加上 issued by <issuer>;或者为 no signature。<file> 是 Release 的锁文件 <lockfile-path>,或 Release 目录中的 plugins-trust.yaml,即 <record-path>。
plugin artifact not found on this machine (Plugin entity "<reference>" is authored in a catalog directory, expected <file> in <directory>). Place the built .wasm beside the entity under that name, or publish the plugin and reference the published Plugin entity instead of the one in the catalog directory(本机上未找到插件制品(该 Plugin 实体编写在目录目录中,预期在所示目录中找到所示文件)。请将构建好的 .wasm 以该名称放在实体旁边,或发布该插件并引用已发布的 Plugin 实体,而不是目录目录中的那个)
plugin "<reference>" at version <version> is not on this machine; place its module, named <file>, beside its Plugin entity in <directory>: plugin artifact not found on this machine(该版本的插件不在本机上;请将其模块以所示文件名放在所示目录中其 Plugin 实体的旁边:在本机上找不到插件制品)
其他情况下,消息会指出查找该模块的每一个位置:
plugin "<reference>" is not on this machine: the binary does not carry its module, no catalog folder holds its Plugin entity and the content cache a pull fetches into does not hold it: plugin artifact not found on this machine(该插件不在本机上:二进制文件未携带其模块,没有任何目录文件夹持有其 Plugin 实体,拉取所写入的内容缓存中也没有它:在本机上找不到插件制品)
lint 只在二进制文件中查找,因此只指出上述位置中的第一个。
对于以注册表位置形式编写的引用,情况相同:
plugin "<reference>" not resolvable: an OCI plugin URI requires a prior aggrega pull --release <release> (so its bytes are cached) or an explicit local path; plugin resolution does not fetch from a registry: plugin artifact not found on this machine(该插件无法解析:OCI 插件 URI 需要事先针对该 release 运行 aggrega pull(以便缓存其字节)或提供显式本地路径;插件解析不会从 registry 获取:本机上未找到插件制品)
core importer "<importer>" at version <version> is not on this machine, and the workspace is offline, so its registry <host> is not asked for it; run the import once with the network available, which fetches it from the workspace’s default registry, verifies it and keeps it in the content cache for every later import, or place its module, named <file>, beside a Plugin entity of <importer> at <version> in a catalog folder: plugin artifact not found on this machine(该版本的核心导入器不在本机上,且工作区处于离线状态,因此不会向其 registry 请求它;请在网络可用时运行一次导入,这会从工作区的默认 registry 获取它、验证它,并将其保存在内容缓存中供之后的每次导入使用;或者将其模块以所示文件名放在目录文件夹中该导入器该版本的 Plugin 实体旁边:本机上未找到插件制品)
其他原因为 its registry <host> could not be reached (<cause>)、its registry <host> holds no <location>:<version> 和 the workspace names no default registry to fetch it from;后两者只给出第二种补救措施,因为在网络可用时运行并不会改变它们。
a plugin recorded as trusted for an accept-or-reject verdict is no longer attached at any verdict role: <record-path> records <plugin> as trusted, but no verdict attachment in the workspace configuration names it; a gate that was reviewed and is now absent leaves output indistinguishable from output that gate approved. Attach the plugin again under plugins.governance at an ir-verdict or render-verdict role, or under plugins.linter; or, if it was meant to go, run aggrega pull --upgrade --release <release> <plugin> to drop it from the record — an ordinary aggrega pull leaves the record as it is, so only an explicit upgrade removes an entry(一个被记录为可信、用于给出接受或拒绝裁决的插件已不再挂接在任何裁决角色上:该记录文件将此插件记录为可信,但工作区配置中没有任何裁决挂接指向它;一个经过审查、如今缺失的关卡,会使输出与该关卡批准的输出无从区分。请在 plugins.governance 下以 ir-verdict 或 render-verdict 角色重新挂接该插件,或挂接在 plugins.linter 下;或者,如果本就打算移除它,请运行上述定向升级命令将其从记录中删除——普通的 pull 会保持记录不变,因此只有显式升级才会删除条目)
plugin "<plugin-identity>": <record-path> records version <recorded-version> with digest <recorded-digest> as trusted for it, but this resolution reports version <resolved-version> with digest <resolved-digest>; review what changed and adopt it with aggrega pull --upgrade --release <release> <plugin>, or restore the recorded identity: the plugin identity recorded as trusted no longer matches what this resolution reports(插件:记录文件将某个版本及其摘要记录为该插件的可信身份,但本次解析报告的是另一个版本及摘要;请审查变更内容,并使用上述定向升级命令采用它,或恢复所记录的身份:被记录为可信的插件身份与本次解析报告的结果不再一致)
entity "<entity>" claims export "<export>", which the plugin’s describe() does not declare: wasm: entity contract claim does not match plugin describe()(实体声明了一个导出,但插件的 describe() 并未声明该导出:wasm:实体契约声明与插件 describe() 不匹配)
声明导出上的某个字段:
entity "<entity>" export "<export>" declares operates "<claimed>" but the plugin’s describe() reports "<reported>": wasm: entity contract claim does not match plugin describe()(实体的某个导出声明的 operates 与插件 describe() 报告的值不同:wasm:实体契约声明与插件 describe() 不匹配)
以及渲染行为字段,其报告形式相同,并指出不一致的字段:
entity "<entity>" declares boundary_assembly "<claimed>" but the plugin’s describe() reports "<reported>": wasm: entity contract claim does not match plugin describe()(实体声明的 boundary_assembly 与插件 describe() 报告的值不同:wasm:实体契约声明与插件 describe() 不匹配)
wasm: plugin "<plugin>": recorded command mirror <recorded set> does not match the plugin describe() commands <reported set>; re-run aggrega plugin sync and commit the result: wasm: recorded command mirror does not match plugin describe()(wasm:插件记录的命令镜像与插件 describe() 的命令不匹配;请重新运行 sync 命令并提交结果:wasm:记录的命令镜像与插件 describe() 不匹配)
发布时的同一比较会报告两个命令集,但不附带重新记录的说明:
plugin "<plugin>": recorded command mirror <recorded set> does not match the plugin describe() commands <reported set>: wasm: recorded command mirror does not match plugin describe()(插件记录的命令镜像与插件 describe() 的命令不匹配:wasm:记录的命令镜像与插件 describe() 不匹配)
plugin "<plugin>": recorded metadata.version "<recorded>" does not match the plugin describe() version "<reported>": wasm: entity metadata.version does not match plugin describe()(插件记录的 metadata.version 与插件 describe() 报告的版本不匹配:wasm:实体 metadata.version 与插件 describe() 不匹配)
在发布时,拒绝信息还会指出实体文件、.wasm 以及修复方法:
Plugin <plugin>: metadata.version in <entity-path> does not match the .wasm describe() version at <path> — set metadata.version to the release you are publishing and build the plugin from a clean checkout of the commit that release’s tag names, so it reports that version itself; for a new release, commit the entity with the source it releases and tag that commit first: plugin "<plugin>": recorded metadata.version "<recorded>" does not match the plugin describe() version "<reported>": wasm: entity metadata.version does not match plugin describe()(实体文件中的 metadata.version 与 .wasm 的 describe() 版本不匹配——请将 metadata.version 设为你要发布的版本,并从该版本标签所指提交的干净检出构建插件,使其自身报告该版本;对于新版本,请先将实体与其发布的源码一并提交,并为该提交打标签:插件记录的 metadata.version 与插件 describe() 报告的版本不匹配:wasm:实体 metadata.version 与插件 describe() 不匹配)
Plugin <plugin>: the .wasm at <path> was built from a working tree with uncommitted changes — set metadata.version in <entity-path> to the release you are publishing and build the plugin from a clean checkout of the commit that release’s tag names, so it reports that version itself; for a new release, commit the entity with the source it releases and tag that commit first: plugin was built from a working tree with uncommitted changes, so no commit reproduces the version it reports (plugin "<plugin>", describe() version "<version>", which ends with "-dirty")(该 Plugin 位于所示路径的 .wasm 是从含有未提交更改的工作树构建的——请将实体文件中的 metadata.version 设为你要发布的 release,并从该 release 的标签所指提交的干净检出构建插件,使其自身报告该版本;对于新的 release,请先将实体与其发布的源码一同提交,并为该提交打标签:插件是从含有未提交更改的工作树构建的,因此没有任何提交能复现它报告的版本(其 describe() 版本以 -dirty 结尾))
plugin "<plugin>": stamped spec.runtime.hostFunctions <recorded set> does not match <derived set> derived from the verified .wasm <artifact>: wasm: stamped host-function record does not match .wasm imports(插件上标记的 spec.runtime.hostFunctions 记录集合与从已验证的 .wasm 制品推导出的集合不一致:wasm:标记的宿主函数记录与 .wasm 导入不一致)
在验证插件时运行的同一比较会报告两个集合,但不包含制品:
plugin "<plugin>": recorded host-function record <recorded set> does not match the .wasm imports <derived set>: wasm: stamped host-function record does not match .wasm imports(插件记录的宿主函数集合与 .wasm 的导入集合不一致:wasm:标记的宿主函数记录与 .wasm 导入不一致)
输出的消息。消息以该条件自身的句子开头,随后是收集到的每一处不一致,每一处都指明其轴——对于实体,还指明其种类,因为实体由其种类和 URI 共同标识,所以 Aggregate 与 Manifest 同名的 Release 会有两个条目,对其中任一个的编辑都会针对被编辑的那一个报告:
lockfile: out of date; it no longer matches what its Release resolves to: entity "<uri>" (<kind>) not in lockfile (referenced from <site>)(lockfile:已过期;它不再与其 Release 解析出的结果一致:实体(及其种类)不在 lockfile 中,并附有引用它的位置) <axis>"<uri>" changed: lockfile=(<version>,<digest>) current=(<version>,<digest>)(所示轴上的所示引用已更改:lockfile 中的版本和摘要与当前的不同) entity "<uri>" (<kind>) changed: lockfile=(<version>,<digest>) current=(<version>,<digest>)(所示种类的所示实体已更改:lockfile 中的版本和摘要与当前的不同) <axis>"<uri>" no longer used by the release(所示轴上的所示引用不再被该发布使用) release document "<file>" was edited after the lockfile was written: its content no longer matches the recorded digest (lockfile=<digest> current=<digest>), so the pins may no longer describe what it asks for; re-resolving the Release records the files it reads as they now stand(所示发布文档在写入 lockfile 之后被编辑过:其内容不再与记录的摘要一致,因此这些 pin 可能不再描述它所请求的内容;重新解析该 Release 会按文件当前的状态记录它读取的文件)
source-artifact kind=<kind> url=<url>: reference "<ref>" moved — the lockfile pins <commit>, and it now resolves to <commit>; adopt where it now points with aggrega pull --upgrade --release <release>
构建会在条目之后打印补救方法:
run aggrega pull --release <release> to re-resolve the Release and rewrite its lockfile
remediation: add an entry for <host> (machine <host> login <user> password <secret>) to the netrc file <path>, then run the command again(补救措施:在 netrc 文件中为该主机添加一个条目(包含 machine、login 和 password),然后重新运行该命令)
the netrc file could not be read (file <path>, line <line>, a word stands where a keyword is expected (machine, default, login, password, account or macdef)). Correct the file, or set NETRC to the path of another netrc file to read instead(无法读取 netrc 文件(所示文件和行:应为关键字(machine、default、login、password、account 或 macdef)的位置出现了一个单词)。请修正该文件,或将 NETRC 设置为另一个要读取的 netrc 文件的路径)
以及针对无法读取的文件,并引述原因:
the netrc file could not be read (file <path>, <why it could not be read>). Correct the file, or set NETRC to the path of another netrc file to read instead(无法读取 netrc 文件(所示文件及无法读取的原因)。请修正该文件,或将 NETRC 设置为另一个要读取的 netrc 文件的路径)
aggrega plugin add: 127.0.0.1:18471: list versions for plugin/cli/mo: oci: list tags: Get “http://127.0.0.1:18471/v2/plugin/cli/mo/tags/list”: 127.0.0.1:18471 did not answer within 30s: egress: the server did not answer in time (aggrega plugin add: 127.0.0.1:18471: 列出 plugin/cli/mo 的版本: oci: 列出标签: Get: 127.0.0.1:18471 未在 30s 内应答: egress: 服务器未及时应答)
以及应答中途停止时:
<host> stopped answering: nothing more of its answer arrived for 30s: egress: the server did not answer in time (停止应答: 30s 内其应答再无任何内容到达: egress: 服务器未及时应答)
aggrega plugin add: 127.0.0.1:18472: no cli plugin is named “mo”, and searching every repository for a name containing it did not finish; name the plugin exactly, as aggrega plugin add cli <name>: the walk was stopped after 5m0s, before the listing ended (repositories named so far: 146): registry: the repository listing did not end in time (aggrega plugin add: 127.0.0.1:18472: 没有名为“mo”的 cli 插件,并且在每个仓库中搜索包含该名称的插件未能完成;请准确指定插件名称,例如 aggrega plugin add cli 后接插件名称: 遍历在 5m0s 后、列表结束前被停止 (目前已列出的仓库数: 146): registry: 仓库列表未及时结束)
过于繁忙的注册表会回答 429 Too Many Requests,或带有说明需等待多久的 Retry-After 标头的 503 Service Unavailable。命令向注册表发出的每个请求都会按注册表要求的时间等待(未说明时为十秒),然后再次发送;发往该注册表的每个请求都会随之等待,向其并发发送的请求也会减少,直到它再次正常回答。如果注册表在五分钟内只回答“放慢速度”,则以此条件拒绝,并指出该注册表、其最后一次回答以及它只给出这一回答的时长;在等待期间自身时间限制到期的请求也同样如此。随后 aggrega registry update 会将该注册表报告为未编入索引,而它保留运行前的索引。
发出的消息,针对要求放慢速度达五分钟的注册表:
<host> kept asking to slow down: its last answer was 429 Too Many Requests, and it had answered nothing else for 5m0s: oci: the registry kept asking to slow down (持续要求放慢速度:其最后一次回答是 429 Too Many Requests,且在 5m0s 内未回答其他内容:oci: 注册表持续要求放慢速度)
以及针对自身时间限制结束了等待的请求:
<host> kept asking to slow down: its last answer was 429 Too Many Requests, and it had answered nothing else for <how long> when the request’s own time ran out: oci: the registry kept asking to slow down (持续要求放慢速度:其最后一次回答是 429 Too Many Requests,且直到请求自身时间用尽时仍未回答其他内容:oci: 注册表持续要求放慢速度)
catalog: cached <uri> content digest <computed> does not match lockfile pin <pinned>: oci: content digest mismatch(缓存实体的内容摘要与 lockfile 中固定的摘要不匹配:内容摘要不匹配)
oci: content digest mismatch: pinned entity "<uri>": registry now serves digest <computed> for the pinned version, not the pinned digest <pinned>; run aggrega pull --upgrade --release <release> to update the pin(内容摘要不匹配:registry 现在为固定版本提供的摘要不是固定的摘要;运行上述命令以更新固定值)
pinned entity <uri>: no source holds the pinned bytes <pinned> (<what each source it read held>); with a registry reachable, aggrega pull --release <release> fetches the pinned version again: <the message above>(固定的实体:没有任何来源持有固定的字节;在 registry 可访问时,上述命令会重新获取固定版本:后接上面的消息)
oci: manifest has no layer of media type "<media-type>": oci: manifest has no layer of the expected content media type(manifest 中没有该媒体类型的层:manifest 中没有预期内容媒体类型的层)
以及有多个时,还会指出数量:
oci: manifest has <count> layers of media type "<media-type>"; expected exactly one: oci: manifest has multiple layers of the expected content media type(manifest 中有多个该媒体类型的层,预期恰好一个:manifest 中有多个预期内容媒体类型的层)
bundle root carries no entity document among <file>, <file>: oci: published bundle carries no entity document(包根目录的上述文件中没有实体文档:oci:已发布的包中没有实体文档)
没有实体、且包中什么都没有时:
bundle root carries no files at all: oci: published bundle carries no entity document(包根目录中没有任何文件:oci:已发布的包中没有实体文档)
有多个实体时,会同时给出数量和冲突的文档:
bundle root carries <count> entity documents (<file>, <file>): oci: published bundle carries more than one entity document(包根目录含有多个实体文档:oci:已发布的包中含有不止一个实体文档)
oci: unbundle gzip: <archive error>: oci: published bundle cannot be unpacked(oci:解包 gzip 失败:oci:已发布的包无法解包)
在某个文件中途中断的归档:
read <file> from the published bundle: <archive error>: oci: published bundle cannot be unpacked(从已发布的包中读取文件失败:oci:已发布的包无法解包)
声明了从不发布的类型的文档:
the published document declares kind <kind>, which a registry does not publish: oci: published artifact is not an entity document(已发布的文档声明了 registry 不发布的 kind:oci:已发布的制品不是实体文档)
以及根本不是文档的字节:
the published bytes do not parse as a document (<parse error>): oci: published artifact is not an entity document(已发布的字节无法解析为文档:oci:已发布的制品不是实体文档)
oci: target does not support referrer discovery: <target kind>: oci: referrer discovery could not be completed(oci:目标不支持 referrer 发现:oci:referrer 发现无法完成)
制品本身无法定位时:
oci: resolve subject "<reference>": <the underlying failure>: oci: referrer discovery could not be completed(oci:解析 subject 失败:oci:referrer 发现无法完成)
以及查找失败时:
oci: list referrers of "<reference>": <the underlying failure>: oci: referrer discovery could not be completed(oci:列出 referrer 失败:oci:referrer 发现无法完成)
不要求签名时,相同的文本会改为以通知形式出现:
signature verification could not run for <uri> (the registry could not answer the signature lookup and no signature is required; continuing): <the message above>(无法执行签名验证(registry 无法应答签名查询,且不要求签名;继续运行))
signing: signature bundle does not verify: <what the verifier reported>(signing:签名包未通过验证,后附验证器报告的内容)
以及在密码学检查通过、但对签名所针对制品的读取结果不一致时:
signing: signature bundle does not verify: its cryptographic check holds, but it does not name <manifest-digest> as the artifact it was made for(signing:签名包未通过验证:其密码学检查成立,但它未将所示清单摘要指明为其签名所针对的制品)
signing: signature bundle does not verify: its cryptographic check holds, but it is in a form from which the artifact it was made for cannot be read(signing:签名包未通过验证:其密码学检查成立,但其形式无法读取出其所针对的制品)
每条都以正在验证的引用为前缀:
verifying the signature of <uri>: <the message above>(正在验证该 URI 的签名,后附上述消息)
以及在 registry 的条目将验证设为建议性时,作为通知而非中止:
signature verification failed for <uri> (advisory; continuing): <the message above>(该 URI 的签名验证失败(仅作提示;继续执行),后附上述消息)
signing: signature identity is not trusted for this registry: <what the verifier reported>; signer presented issuer "<issuer>" with identity "<subject>", but no trusted identity permits that issuer(signing:该签名身份不受此 registry 信任,后附验证器报告的内容;签名者出示了所示颁发者及身份,但没有任何受信任的身份允许该颁发者)
以及无法读取时,回退为验证器自身的报告:
signing: signature identity is not trusted for this registry: <what the verifier reported>(signing:该签名身份不受此 registry 信任,后附验证器报告的内容)
egress: network access refused because the workspace is offline; remediation: pass --offline=false to allow the network for this one run, or clear the top-level offline key in the configuration file (or AGGREGA_OFFLINE) to allow it from now on; where the work is a build that needs content the machine does not have, run aggrega pull --release <release> from a connected environment first to populate the cache(出站:由于工作区处于离线状态,网络访问被拒绝;补救方法:传入上述标志以仅在本次运行中允许网络访问,或清除配置文件中的顶层离线键(或 AGGREGA_OFFLINE)以从此允许网络访问;如果所做的工作是需要本机所没有内容的构建,请先在联网环境中运行上述 pull 命令来填充缓存)
uses edge target does not exist ("<target>", wired into socket "<socket>"). Point the target at a component the Aggregate declares, or declare a component under that name. (uses 边的目标不存在(括号内为该目标及其所接入的 socket)。请将目标指向该 Aggregate 声明的某个 component,或以该名称声明一个 component。)
connection alias is already used by another connection of the same component ("<alias>", on component "<component>", this connection wired into socket "<socket>", with target "<target>", written in "<file>", at "<key path>", the connection already holding the alias wired into socket "<socket>", with target "<target>", written in "<file>", at "<key path>"). Give one of the two connections an alias of its own: a component reads each connection by its alias, whatever socket it is wired into. A list entry takes its target’s name as its alias, so a target listed twice is listed once, or written as two keyed entries under two aliases. (该连接别名已被同一 component 的另一个连接使用(括号内依次为别名、component、本连接所接入的 socket、目标、编写所在的文件和键路径,以及已占用该别名的连接的 socket、目标、文件和键路径)。请为两个连接之一指定单独的别名:component 按别名读取每个连接,无论其接入哪个 socket。列表条目以其目标的名称作为别名,因此被列出两次的目标应只列出一次,或写成两个使用不同别名的键控条目。)
如果两个连接写在同一键路径下——即一个列表两次列出同一目标——则每个连接还会以其在该列表中的位置来指明,如 list entry "2" 与 list entry "1",这是区分这两个条目的唯一依据。
unknown uses socket: name a socket the entity declares in its usesSchema — only a component’s own uses block may name one the catalog did not declare (Release <release-name>, at .spec.components.<component>, "<component-type>", "<socket-name>", "<declared-sockets>")(未知的 uses socket:请指定该实体在其 usesSchema 中声明的 socket——只有组件自身的 uses 块可以指定目录未声明的 socket;括号中依次给出 Release、位置、组件类型、socket 名称及已声明的 socket)
a connection carries an attachment under a name its socket declares no slot for (Aggregate <aggregate-name>, at .spec.components.<component>.uses.<socket>.<alias>, "<attachment>", on the connection "<alias>", through socket "<socket>", of component "<component>", the socket declaring the slots "<slots>"). Write the attachment under one of the slots the socket declares, or declare this slot in the socket’s featuresSchema on the Component.(连接以其 socket 未声明槽位的名称携带了一个附件;括号中给出 Aggregate、条目路径、附件名称、连接、socket、组件以及该 socket 声明的槽位。请将附件写在该 socket 声明的某个槽位下,或在 Component 上该 socket 的 featuresSchema 中声明此槽位。)
a connection carries an attachment under a name its socket declares no slot for (Release <release-name>, at .spec.boundaries.<boundary>.components.<component>.uses.<socket>.<alias>, "credentail", near the declared slot "credential", on the connection "<alias>", …)(连接以其 socket 未声明槽位的名称携带了一个附件;括号中给出 Release、条目路径、附件名称、与之接近的已声明槽位以及连接等)
对于这样的名称,不会另外发出提示。在组件自身的 features: 块上,与已声明槽位相差一处编辑的名称是合法的,只会触发下文“An attachment name is one edit from a declared slot(附件名称与已声明槽位相差一处编辑)”中的提示;而在连接上,该名称会被拒绝,拒绝信息本身即包含这一配对。
如果插槽不声明任何槽位,则不显示列表,建议为“The socket declares no slots, so no connection wired through it carries an attachment: remove the attachment, or declare the slot in the socket’s featuresSchema on the Component.(该插槽不声明任何槽位,因此经由它的连接都不携带附件:请删除该附件,或在 Component 上该插槽的 featuresSchema 中声明该槽位。)”如果 Component 根本未声明该插槽,则建议为“The component’s type does not declare this socket, so the socket declares no slots and no connection wired through it carries an attachment: remove the attachment, or declare the socket and its slot in the Component’s usesSchema.(该组件的类型未声明此插槽,因此该插槽不声明任何槽位,经由它的连接都不携带附件:请删除该附件,或在 Component 的 usesSchema 中声明该插槽及其槽位。)”
release edge retargets a developer-declared edge (declared target "<declared-target>", target the Release names "<release-target>", wired into socket "<socket>"). Drop the target from the Release entry to configure the connection as it was declared, or change the target where the connection is declared.(Release 边重新指定了开发者声明的边的目标(括号中依次为声明的目标、该 Release 指定的目标以及所接入的 socket)。请从 Release 条目中删除目标,以按声明配置该连接;或者在声明该连接的位置修改目标。)
release per-edge configuration has no edge to apply to (Release <release-name>, at .spec.boundaries.<boundary>.components.<consumer>.uses.<socket>.<alias>, "<consumer>", on socket "<socket>", under alias "<alias>"). Give the entry a target to wire the edge, or remove it: an entry with no target configures an edge that must already exist.(Release 的逐边配置没有可应用的边(括号中依次为该 Release、条目路径、消费方组件、socket 和别名)。请为该条目指定目标以连接该边,或删除该条目:没有目标的条目配置的是一条必须已经存在的边。)
当条目指定的 component 未在 Aggregate 中声明时,该中止来自构建的更早阶段,内容如下,并指出条目设置的内容——infra、features 或 infra and features:
release per-edge configuration has no edge to apply to: release edge <consumer>/<socket>/<alias> sets <infra|features|infra and features> on <consumer>, which is not a component in the topology(Release 的逐边配置没有可应用的边:该 Release 边在一个并非拓扑中组件的消费方上设置了 infra、features 或两者)
a Release attachment takes the name of an attachment one of a component’s connections carries (Release <release-name>, at .spec.components.<component>, "<alias>.<slot>", of component "<component>", on the connection "<alias>", through socket "<socket>", in the slot "<slot>"). Write it on the connection entry, under uses.<socket>.<alias>.features.<slot>, and remove "<alias>.<slot>" from this entry’s features: an attachment a connection carries is written on that connection and nowhere else.(某个 Release 附件使用了某个组件的一条连接所携带附件的名称。请将其写在该连接条目上,并从此条目的 features 中移除该键:连接所携带的附件只写在该连接上,不写在其他任何地方。)
输出的消息(针对边界上的键)。它会指明该边界的附加项块,以及其连接携带该附加项的组件:
a Release attachment takes the name of an attachment one of a component’s connections carries (Release <release-name>, at .spec.boundaries.<boundary>.features, "<alias>.<slot>", of component "<component>", on the connection "<alias>", through socket "<socket>", in the slot "<slot>"). Write it on component "<component>"’s connection entry, under uses.<socket>.<alias>.features.<slot>, and remove "<alias>.<slot>" from this boundary’s features: an attachment a connection carries is written on that connection and nowhere else.(某个 Release 附件使用了某个组件的一条连接所携带附件的名称。请将其写在该组件的连接条目上,并从此边界的 features 中移除该键:连接所携带的附件只写在该连接上,不写在其他任何地方。)
a Release connection attachment names no Feature type, and the type is required for an attachment only the Release makes (Release <release-name>, at .spec.components.<component>.uses.<socket>.<alias>, "<slot>", on the connection "<alias>", through socket "<socket>", of component "<component>"). Name the Feature this attachment attaches under its type, or declare the attachment on the Aggregate’s connection entry and size it here.(某个 Release 连接附件未指定 Feature 类型,而仅由 Release 创建的附件必须指定类型。请在其类型下指定此附件所挂载的 Feature,或在 Aggregate 的连接条目上声明该附件,并在此处设定其规格。)
该检查读取的是组件实际携带的标识;对于由导入的 Aggregate 贡献的组件,这是限定标识——模块名称、一个点号,再加上组件自身的名称。因此,两个各自都可接受的名称仍可能连接成一个不可接受的标识:名为 bfr--x 的模块与其内部名为 y 的组件连接成 bfr--x.y,它以组合标识的方式开头。该中止会给出连接后的标识,同时指向你编写的键。
针对目标会拒绝的标识,发出的消息:
component identity cannot be the name its emitted resources are stamped with: rename the component (Aggregate, at <field-path>, "<identity>", which must "<rule>")(组件标识不能作为其发出的资源所标记的名称:请重命名该组件;括号内依次为 Aggregate、字段路径、该标识及其必须满足的规则)
component identity cannot be the name its emitted resources are stamped with: rename the component (Aggregate, at <field-path>, "<identity>", which must not open with the reserved "<opening>")(组件标识不能作为其发出的资源所标记的名称:请重命名该组件;括号内依次为 Aggregate、字段路径、该标识及其不得使用的保留开头)
the target will not accept a name derived from this component’s authored identity: rename the component (component "<identity>", written at <field-path>, which the target cannot use as a <name-kind>, <the target's reason>). choose a name of at most <n> characters that the target accepts(目标不接受从该组件所编写的标识派生出的名称:请重命名该组件,并选择一个长度不超过所述字符数、且目标可以接受的名称)
**修复方法:**在每个命名该组件的位置——声明它的 Aggregate,以及放置并配置它的 Release——将其重命名为目标接受的名称。如果消息说明了长度,请不要超出。如果没有说明,请阅读目标给出的原因:通常是目标不接受的某个字符,最常见的是名称开头的大写字母——或者在 helm 目标下,开头的数字。优先使用小写字母和数字,单词之间用连字符分隔;命名章节说明了在每类目标下名称的代价。如果原因指明了某个 Service 键,也可以在工作负载声明该键的位置缩短它来腾出长度——而如果原因说明该键没有留下空间,则只有这样做才行。重命名组件会改变其资源所带的名称,因此对于已部署的应用,请像对待任何其他资源重命名一样处理。
provider guest never accepted a component identity the compiler composed for it (provider guest "<provider>", refused <n> proposals, the last of them "<identity>"). report the defect to whoever maintains that provider plugin(provider guest 始终未接受编译器为其组合的组件标识:请将该缺陷报告给该 provider 插件的维护者)
required uses socket not populated (Component, at .spec.components.<instance>.uses.<socket>, "<socket-name>", declared required by component type "<component-type>")(必需的 uses socket 未填充:所示位置的该 socket 由所示组件类型声明为必需)
cyclic extends chain (Component <name>, rule extends). <entity> extends <reference>, which is already in the chain; remove the extends on <entity>, or point it at an entity outside the chain(extends 链存在循环:某实体所继承的引用已在链中;请移除该实体上的 extends,或将其指向链外的实体)
component placed in no boundary: name it under a boundary’s components, or place the sub-module that contributes it under aggregates (Release <name>, at <authored key>, "<component-id>")(组件未被放入任何边界:请在某个边界的 components 下列出它,或将贡献它的子模块放在 aggregates 下)
sub-module placed in no boundary: route it into a boundary under aggregates, or name its components there under components (Release <name>, at <authored key>, "<module-path>")(子模块未被放入任何边界:请在 aggregates 下将其路由到某个边界,或在 components 下逐一列出其组件)
boundary names a component the composition does not hold: correct the name, or remove the entry (Release <name>, at <authored key>, "<addressed id>")(边界列出了组合中不存在的组件:请更正名称,或删除该条目)
修复方法: 将消息引用的 id 与组合中实际存在的组件进行比对。缺少模块前缀和把子系统名称写入 id 是两种常见原因;去掉子系统、加上模块前缀,或更正拼写。若该条目是已删除或已重命名组件的遗留条目,请删除它。
uses edge target was pruned because its active toggle resolved to false ("<target>", wired into socket "<socket>"). Keep the target’s active toggle true, or drop the dependency on it.(uses 边的目标因其 active 开关解析为 false 而被移除。请将目标的 active 开关保持为 true,或删除对它的依赖。)
uses edge target names a component its module does not export ("<target>", module "<module>", which exports "<aliases>", wired into socket "<socket>"). Name the component through one of the module’s exported aliases, or list it under the module’s exportedComponents.(uses 边的目标指向了其模块未导出的组件(依次为目标、模块及其导出的别名、所接入的 socket)。请通过模块导出的别名之一指向该组件,或将其列在模块的 exportedComponents 下。)
active toggle did not resolve to a boolean (node "<node>", active resolved to "<value>")(active 开关未解析为布尔值)
若它解析为空,则附带指出常见原因的建议:
active toggle did not resolve to a boolean (node "<node>", active resolved to ""). a toggle reading a parameter resolves to nothing until that parameter is fulfilled(active 开关未解析为布尔值。读取参数的开关在该参数被满足之前解析为空)
flattened node ID collision: rename one of the colliding instances so their flattened IDs differ (id "<identifier>", path "<path in the composition>", collides with existing entry from "<the other contributor>")(扁平化后的节点 ID 冲突:请重命名其中一个冲突的实例,使其扁平化后的 ID 不同;该 ID 与另一贡献方已有的条目冲突)
components in different subsystems take the same identity: rename one of them, since a subsystem contributes nothing to a component’s identity (Aggregate, at .spec.subsystems.<second>.components.<identifier>, "<identifier>", declared under subsystems "<first>, <second>")(不同子系统中的组件具有相同的标识:请重命名其中一个,因为子系统不参与构成组件的标识)
mutator patch rejected: patch <n> does not decode as a JSON Patch document: <what the reader could not do>(变更器补丁被拒绝:该补丁无法解码为 JSON Patch 文档)
mutator patch rejected: patch <n> does not apply to the node-label surface: <what the patch engine refused>(变更器补丁被拒绝:该补丁无法应用于节点标签视图)
或者应用补丁后的结果不是宿主交出的那个视图:
mutator patch rejected: mutated node set changed size (a mutator may not add or remove nodes)(变更器补丁被拒绝:变更后的节点集合大小发生了变化(变更器不得添加或删除节点))
mutator patch rejected: mutated node set introduced node "<node>" (a mutator may not add nodes)(变更器补丁被拒绝:变更后的节点集合引入了新节点(变更器不得添加节点))
mutator patch rejected: node "<node>" gained a field outside "labels" (a mutator may only touch labels)(变更器补丁被拒绝:节点获得了标签之外的字段(变更器只能修改标签))
mutator patch rejected: node "<node>" lost its "labels" field(变更器补丁被拒绝:节点丢失了其标签字段)
mutator patch rejected: node "<node>" carries a non-string label value after patching: <what the reader found>(变更器补丁被拒绝:应用补丁后节点带有非字符串的标签值)
invalid inject key: the from-key must name a provides key its source publishes (Aggregate <name>, at .spec.components.<component>.inject.<mechanism>.<delivery-key>, "<from-key>", "<component-type>", "<key-1>", "<key-2>")(无效的 inject 键:from-key 必须指定其来源所发布的 provides 键)
invalid inject key: the from-key must name a provides key its source publishes (Aggregate <name>, at .spec.components.<component>.uses.<socket>.<alias>, "<mechanism>", "<delivery-key>", "<from-key>", "<component-type>", "<key-1>")(无效的 inject 键:from-key 必须指定其来源所发布的 provides 键)
invalid inject key: the from-key must name a provides key its source publishes (Aggregate <name>, at .spec.components.<component>.features.<attachment>, "<from-key>", in "<in>", mechanism "<mechanism>", FeatureRecipe "<feature-recipe>", publishes "<key-1>", publishes "<key-2>")(无效的 inject 键:from-key 必须指定其来源所发布的 provides 键)
missing required feature: attach a Feature of the required type to the component (<required-type>, required by component type <component-type>, under the requirement label <label>)(缺少必需的 feature:请将所需类型的 Feature 附加到该组件)
required attachment slot unfilled (<slot>, declared required by component type <component-type>). Attach a Feature at that name, in the Aggregate or in the Release, on the component or at a scope above it.(必需的附加槽位未填充:该槽位由所示组件类型声明为必需。请在 Aggregate 或 Release 中,在该组件上或其上层作用域中,以该名称附加一个 Feature。)
required attachment slot unfilled ("<slot>", declared required by socket "<socket>", of component type "<component-type>", left unfilled by the connection "<alias>"). Attach a Feature under that slot in this connection’s features, on its entry in the Aggregate or in the Release.(必需的附加槽位未填充:该槽位由所示组件类型的所示 socket 声明为必需,所示连接未填充它。请在该连接的 features 中、在其于 Aggregate 或 Release 中的条目上,以该槽位附加一个 Feature。)
一处声明即足够:只要任一 Feature 的列表列出了另一个,就会触发停止。比较名称时双方都会去掉版本,因此一个条目匹配它所指 Feature 的所有版本。编译器将 Feature 作者声明的名称与组件所带的 Features 进行比较,不对任何一方作额外解读。
发出的消息:
a Feature reaches a component alongside a Feature it declares a conflict with ("<feature>", attached in the Release on boundary "<boundary-path>", conflicts with "<other-feature>", attached in the Aggregate on component "<component>", on component "<component>"). Attach only one of the two where they meet: remove one attachment, or move it to a scope that does not hold this component.(一个 Feature 与其声明冲突的另一个 Feature 同时到达同一组件:所示两个 Feature 及其各自的附加位置和交汇的组件如上所列。请在二者交汇处只附加其中一个:移除一个附加,或将其移到不包含该组件的作用域。)
第一个值是其列表列出另一个的 Feature——即上面句子所指的那个——其后是它被附加的每个位置;然后是与之冲突的 Feature,及其被附加的每个位置;最后是它们相遇的组件。每个位置都用你要打开以修改它的那份文档的措辞表述:attached in the Aggregate on component、attached in the Aggregate on subsystem、attached in the Release on boundary(嵌套边界的路径用 / 连接各层级)、attached in the Release on the entry for component 后接 in boundary,或者 attached by annotation-driven expansion of 加上注解,再后接 declared at 及其编写位置。写在连接上的附加项表述为该连接的条目,因为编辑它的地方是该条目而不是组件自身的块:attached in the Aggregate on the connection 后接 through socket 和 of component,或 attached in the Release on the connection 后接 through socket、of the entry for component 和 in boundary。附加在两处的 Feature 会列出两处。报告定位于 components: 下该组件自身的键;在多个组件上相遇的一对会为每个组件各报告一次,顺序与 Aggregate 声明组件的顺序一致。
**如何修复:**在它们相遇处只附加其中一个——删除其中一个附加项,或将其中一个移到不包含此组件的作用域,例如兄弟边界。如果附加项来自注解驱动扩展,需要修改的是注解,而不是它扩展到的块。如果这两个 Features 实际上可以组合使用,那么错的是声明:从声明方 Feature 的目录实体上的 conflictsWith 列表中删除另一个 Feature。
Attachment does not conform to its declared slot shape(附加项不符合其声明的槽位结构)
attachment does not conform to its declared slot shape (Aggregate <name>, at .spec.components.<component>.features.<attachment>, "<slot>", "<mechanism>", "<permitted-mechanism>")(附件不符合其声明的槽位形态)
attachment does not conform to its declared slot shape (Aggregate <name>, at .spec.components.<component>.features.<attachment>.<key>, attachment does not conform to the declared slot shape: this key is not part of the slot’s declaration — <remedy>)(附件不符合其声明的槽形状:该键不属于槽的声明)
其中 <remedy> 取决于该键:
remove it,用于在允许列表为空的槽位上指明某个机制的 inject: 块;
remove it, or add it to the slot's inject allowlist in the entity's featuresSchema,用于槽位允许列表可以列出的机制——env、file 或 arg;
remove it: a slot's inject allowlist in the entity's featuresSchema accepts only env, file and arg,用于任何其他机制,这类机制没有任何槽位能够声明。
attachment does not conform to its declared slot shape (Aggregate <name>, at .spec.subsystems.<scope>.features.<attachment>, this attachment is declared at a scope that reaches component <component>, whose attachment slot <slot> does not accept the delivery it carries: move the attachment down to the components that may receive it)(附件不符合其声明的槽形状:该附件声明所在的作用域覆盖了某个组件,而该组件的附件槽不接受此附件携带的交付方式:请将该附件下移到可以接收它的组件上)
duplicate delivery key across inject sources(多个 inject 来源之间存在重复的交付键) (Aggregate <name>, at .spec.components.<component>.inject.<mechanism>.<key>, "<mechanism>", "<key>", "<other-mechanism>")
两个机制都不是肇事者,两份报告都由你来修改:在其中一个机制下重命名该键,或删除两次交付之一。组件究竟可以使用哪些机制是另一个问题,由其 spec.inject 允许列表回答——参见下文“Self-inject mechanism not in the component’s allowlist(自注入机制不在组件的允许列表中)”。
由附加到组件的 Feature 声明的键,从其三个编写面中的第三个进入同一个共享空间,并在下文“An attachment delivers a key another inject source already claimed(附件交付了另一个 inject 来源已声明的键)”下报告;由两个附加的 Features 交付、且两者中后者通过其 FeatureRecipe 的 injectMapping 交付的键,在“Two attached Features deliver one key, the later through its FeatureRecipe’s injectMapping(两个附加的 Features 交付同一个键,后者通过其 FeatureRecipe 的 injectMapping 交付)”下报告。
Self-inject on a component without an allowlist(在没有允许列表的组件上自注入)
self-inject on component without spec.inject allowlist (Aggregate <name>, at .spec.components.<component>.inject, "inject", "<component-type>")(在未声明 spec.inject 允许列表的组件上使用自注入)
uses-edge inject dictates a delivery mechanism the socket does not permit ("<mechanism>", on socket "<socket>", declared on the component type "<component-type>"). The socket declares no delivery allowlist, so it permits no dictation at all — the entity that declared it delivers the dependency’s values itself. Remove the inject block from this connection and read the values from the connection’s provides in the consuming Recipe, or declare the mechanisms the socket permits in its usesSchema entry.(uses 边的 inject 指定了该套接字不允许的交付机制(上述机制、套接字及其声明所在的组件类型)。该套接字未声明交付允许列表,因此完全不允许指定——声明它的实体会自行交付依赖的值。请从此连接中移除 inject 块,并在进行消费的 Recipe 中从该连接的 provides 读取这些值,或在该套接字的 usesSchema 条目中声明它允许的机制。)
uses-edge inject dictates a delivery mechanism the socket does not permit ("<mechanism>", on socket "<socket>", which permits "<mechanism-1>, <mechanism-2>", declared on the component type "<component-type>"). Dictate one of the mechanisms the socket permits, or widen that socket’s inject allowlist in the declaring entity’s usesSchema entry.(uses 边的 inject 指定了该套接字不允许的交付机制(上述机制、套接字、其允许的机制及其声明所在的组件类型)。请指定该套接字允许的机制之一,或在声明实体的 usesSchema 条目中扩大该套接字的 inject 允许列表。)
inject entry on a connection carries value:; a connection delivers the target’s published keys, each named with from: ("<mechanism>", "<in>")(连接上的 inject 条目携带字面值;连接交付的是目标发布的键,每个键都以来源键指定)
每个有问题的条目都作为独立的发现报告,以 DEVELOPER_ERROR 归入编写该块的文档所属的 Aggregate——对于在模块中编写的附加项,即模块自身的文档——并定位在该文档中附加项块内的交付机制处:.spec.components.<component>.features.<attachment>.inject.<mechanism>,或者对于子系统的附加项,.spec.subsystems.<subsystem>.features.<attachment>.inject.<mechanism>。同一文档中的所有此类条目会一次性报告;导入模块中的条目会在导入它的 Aggregate 通过之后报告。该发现指出机制和条目的 in:。同时携带 value: 和 from: 的条目只报告一次,见上文“An inject: entry carries both a literal and a source key(注入条目同时携带字面值和来源键)”。
发出的消息:
inject entry on an attachment carries value:; an attachment delivers the keys its FeatureRecipe publishes, each named with from:, and a literal belongs in the component’s own inject block ("<mechanism>", "<in>")(附加项上的 inject 条目携带了字面值;附加项交付其 FeatureRecipe 发布的键,每个键都以来源键指定,而字面值应放在组件自身的 inject 块中)
inject delivery: shape must be a list of entries, each in: with exactly one of from: or value: ("<mechanism>")(inject 交付:形状必须是条目列表,每个条目带有目标位置,以及来源键或字面值中的恰好一个)
attachment slot selector unsatisfied ("<selector>", declared on slot "<slot>", not satisfied by the labels of the Feature filling it, "<feature-type>"). Add the labels the slot’s selector requires to the Feature’s labels, or fill the slot with a Feature that already carries them.(附件槽位选择器未满足:槽位上声明的选择器未被填充该槽位的 Feature 的标签满足。请将该槽位选择器要求的标签添加到该 Feature 的标签中,或改用已带有这些标签的 Feature 填充该槽位。)
约束本身无法求值时:
attachment slot selector unsatisfied ("<selector>", declared on slot "<slot>", which could not be evaluated: "<why it could not be evaluated>"). Correct the selector on the slot’s declaration in the component’s catalog entity.(附件槽位选择器未满足:槽位上声明的选择器无法求值。请在该组件的目录实体中修正该槽位声明上的选择器。)
[OPS_ERROR E0008] release.yaml at .spec.boundaries.main.components.app.features.identity
attachment slot selector unsatisfied ("feature.aggrega.ai/kind!=secret", declared on slot "identity", not satisfied by the labels of the Feature filling it, "core/secret-value"). Add the labels the slot's selector requires to the Feature's labels, or fill the slot with a Feature that already carries them.
在 Aggregate 中的 component 上编写的同一填充会报告 [DEVELOPER_ERROR E0008] aggregate.yaml at .spec.components.app.features.identity。
attachment slot selector unsatisfied ("<selector>", declared on slot "<slot>", of socket "<socket>", filled on the connection "<alias>", not satisfied by the labels of the Feature filling it, "<feature-type>"). Add the labels the slot’s selector requires to the Feature’s labels, or fill the slot with a Feature that already carries them.(附件槽位选择器未满足:该插座的槽位上声明、在该连接上填充的选择器未被填充该槽位的 Feature 的标签满足。请将该槽位选择器要求的标签添加到该 Feature 的标签中,或改用已带有这些标签的 Feature 填充该槽位。)
attachment slot selector unsatisfied ("<selector>", declared on slot "<slot>", of socket "<socket>", which could not be evaluated: "<why it could not be evaluated>"). Correct the selector on the slot’s declaration in the socket’s featuresSchema on the component’s catalog entity.(附加槽位选择器未满足:在套接字的槽位上声明的选择器无法求值。请在组件目录实体上该套接字的 featuresSchema 中,更正该槽位声明上的选择器。)
该挂载面上的其他一切仍是自由的。Feature 不适合任何已声明槽的挂载可以构建;在已有内容绑定的槽旁边的额外挂载也可以构建,只要它适合的其他槽都没有留空。component 从子系统或 Release 边界继承的挂载永远不会被判定,因此共享形态——在多个 component 所在的作用域中挂载一次凭据,且没有 component 填充该槽——可以构建。未声明 selector: 的槽没有说明它面向哪个 Feature,因此不会以这种方式要求任何挂载。连接所携带的挂载在此也不会被判定:socket 的槽是封闭集合,连接上的任何其他名称都会在“A connection carries an attachment under a name its socket declares no slot for(连接携带的挂载所用名称未被其 socket 声明为槽)”下中止。
attachment written under a name no slot declares fits a slot its component leaves empty ("<attachment>", on component "<component>", attaching the Feature "<feature-type>", which fits the empty slot "<slot>"). Attach it as "<slot>" to fill the slot.(以任何槽位都未声明的名称编写的附件符合其组件留空的一个槽位:该组件上的此附件所附加的 Feature 符合该空槽位。请以该槽位的名称附加它,以填充该槽位。)
attachment written under a name no slot declares fits a slot its component leaves empty ("<attachment>", on component "<component>", attaching the Feature "<feature-type>", which fits the empty slot "<slot>", and the empty slot "<another-slot>"). Attach it under the name of the slot it is meant to fill.(以任何槽位都未声明的名称编写的附件符合其组件留空的一个槽位:该组件上的此附件所附加的 Feature 符合多个空槽位。请以它要填充的那个槽位的名称附加它。)
[OPS_ERROR E0328] release.yaml at .spec.boundaries.main.components.app.features.metrics
attachment written under a name no slot declares fits a slot its component leaves empty ("metrics", on component "app", attaching the Feature "core/prometheus-exporter", which fits the empty slot "identity"). Attach it as "identity" to fill the slot.
如果空槽是必需的,它本身是一个单独的结果,在 Aggregate 中的 component 处以“Required attachment slot not bound(必需的挂载槽未绑定)”报告。
与近似匹配提示的区别。“An attachment name is one edit from a declared slot(挂载名称与已声明的槽仅差一次编辑)”下的提示关注名称的拼写:名称与某个槽仅差一次编辑,而挂载的 Feature 不满足该槽的 selector:,此时构建通过并报告警告。本中止条件关注 Feature 适合什么,与名称无关:名称可以是任何内容,而它适合的槽必须为空。如果名称与某个槽仅差一次编辑,且其 Feature 确实适合该槽,则不会发出提示;若该槽为空,本中止条件就是唯一报告的结果。
An attachment delivers a key another inject source already claimed(挂载交付的键已被另一个注入来源占用)
有三个编写面通过 inject: 块向同一个 component 的注入管道交付:component 自身的 inject: 块、其依赖块各条目上的 inject: 块,以及挂载到它的每个 Feature 上的块。它们按交付机制共享同一个键空间,因此被其中两者同时占用的键会使到达的值产生歧义,构建会停止,而不是让一个编写面静默取代另一个。挂载的 Feature 还可以通过第二种方式交付,即其 FeatureRecipe 的 injectMapping;该途径在所有块交付之后才进入同一空间,并在下文“Two attached Features deliver one key, the later through its FeatureRecipe’s injectMapping(两个挂载的 Features 交付同一个键,后者通过其 FeatureRecipe 的 injectMapping 交付)”下报告。
本条件对应该空间中挂载块的一侧。当挂载自身的 inject: 块占用了某个先前交付已持有的键时报告——上文“Duplicate delivery key across inject sources(跨注入来源的重复交付键)”下的条目是从开发者编写一侧解读的同一规则,二者合起来覆盖了每个块的占用。
duplicate delivery key across two attachments: an attachment’s FeatureRecipe writes a delivery key another attachment already delivered ("<key>", mechanism "<mechanism>", attachment "<attachment>", delivered first by attachment "<other-attachment>"). Give one of the two attachments a key of its own, or attach one fewer: the key this attachment delivers under is chosen by its FeatureRecipe, which can read the attachment’s own values and infra, and the other’s is chosen the same way or by its own inject block where it delivered through one. A Release sets an attachment’s infra and never its values, so where a key is chosen by a value, attach that attachment in the Aggregate with the value, and keep giving the rest from the Release.(两个挂载之间的投递键重复:某个挂载的 FeatureRecipe 写入了另一个挂载已经投递过的投递键。请为两个挂载之一提供独立的键,或少挂载一个:此挂载用于投递的键由其 FeatureRecipe 选择,该 FeatureRecipe 可以读取挂载自身的 values 和 infra;另一个挂载的键以同样的方式选择,或者在它通过自身的 inject 块投递时由该块选择。Release 设置挂载的 infra,但从不设置其 values,因此当键由某个值选择时,请在 Aggregate 中挂载这一项并写入该值,其余部分继续由 Release 提供。)
custom inject mechanism has no matching key in injectMapping output; add the mechanism’s key to the Recipe injectMapping ("<mechanism>", recipe "<featurerecipe>")(自定义注入机制在 injectMapping 输出中没有匹配的键;请将该机制的键添加到 Recipe 的 injectMapping 中)
FeatureRecipe injectMapping output writes a key no delivery mechanism of the host reads ("all", recipe "<featurerecipe>", an output may carry "env, file, arg, or a custom mechanism the host's Recipe reads under its own name")(FeatureRecipe 的 injectMapping 输出写入了宿主的任何交付机制都不读取的键,并列出该 recipe 以及输出可以携带的键)
provides block references a root outside the self-contained set ("<expression>")(provides 块引用了自包含集合之外的根)
该中止定位到声明该条目的 Recipe 及其中编写的键——.spec.provides.<name>——因此它指出的是需要编辑的块,而不是绑定该 Recipe 的组件。所有越出该表面的条目都会在同一次构建中报告;多于一个时,这些发现归入 provides entries that reach outside the data they are evaluated against 分组下。
发出的消息,针对组件 Recipe 自身 locals: 块中的条目。它定位到该 Recipe 中编写的键,所有出错条目都在同一次构建中报告;多于一个时,这些发现归入 locals entries that read a sibling they cannot 分组下:
locals entry references a sibling defined later in the same block ("<expression>", the key it names is "<referenced>", resolved at this point "<the locals available here>", reached through the component "<component>"). define "<referenced>" above "<key>" in the locals block(locals 条目引用了同一块中稍后定义的同级条目:给出表达式、其引用的键、此处已解析的 locals 以及经由的组件。请在 locals 块中将被引用的键定义在当前键之上)
locals entry references a sibling defined later in the same block ("<expression>", the key it names is "<key>", resolved at this point "<the locals available here>", reached through the component "<component>"). a locals entry cannot read itself; compute the value from .values and .infra directly(locals 条目引用了同一块中稍后定义的同级条目:给出表达式、其引用的键、此处已解析的 locals 以及经由的组件。locals 条目不能读取自身;请直接根据 .values 和 .infra 计算该值)
**一个 Recipe 会被许多组件绑定,因此共享块中的一个错误会针对每个绑定它的组件各报告一次——而 reached through the component 正是区分这些发现的依据。**它们共享同一位置,因为都涉及同一文档中同一个编写的条目;位置指出在哪里编辑,组件名称则指出每个发现对应你的哪个组件。这些发现不会合并为一个,因为合并只能说明有问题,却无法说明问题影响到哪些组件,而那正是你需要处理的部分。
template references a key the locals block does not declare (Recipe <recipe> provides[<key>] references <expression>, the locals block declares no <referenced>, it declares <the keys it does declare>). correct the key name(模板引用了 locals 块未声明的键。请更正键名)
template references a key the locals block does not declare ("<expression>", the missing key is "<referenced>", the block declares "<the keys it does declare>", reached through the component "<component>"). correct the key name(模板引用了 locals 块未声明的键。请更正键名)
该检查读取的是引用解析到的路径,而不是其字面写法,因此会跟随块的别名:通过 with .locals 主体重新绑定的点访问的键,或通过绑定到 .locals 的变量访问的键,都会按与直接写法完全相同的条件检查,并以同样方式终止;从加括号的块上读取的键——{{ (.locals).nope }} 或 {{ ($.locals).nope }}——也是如此,因为括号产生的就是块本身,别无其他。只有一种写法会绕过检查:通过调用访问的键,而模板文本无法指明该调用的结果——{{ index .locals "nope" }} 或 {{ (default dict .locals).nope }}——因为此类调用产生什么是在模板运行时决定的,而不是由写法决定。作为此类调用结果上的字段读取的不存在的键——即 (default dict .locals).nope 形式——不会终止,并会渲染模板引擎的占位文本 <no value>。通过 index 访问不存在的键会终止,但报告为下文的“A template indexes a map with a key the map does not hold(模板使用映射中不存在的键对映射进行索引)”,而不是本检查:index 遇到映射中不存在的任何键都会终止。因此,index 仍是访问名称本身经计算得出的键的方式,而块中未声明的计算名称仍会按其键报告。
Template references a root the render context does not define(模板引用了渲染上下文未定义的根)
template references a root the render context does not define(模板引用了渲染上下文未定义的根)(template <template-name> references <dotted-path>, the render context defines <the roots that context defines>)
根正确但已声明支柱下的某个键不正确时:
template references a root the render context does not define(模板引用了渲染上下文未定义的根)(template <template-name> references <dotted-path>, <pillar> defines <the keys that pillar defines>)
artifact template references a pillar the Recipe does not declare (<expression>, artifact <output-name>, attachment <attachment-name>)(artifact 模板引用了 Recipe 未声明的支柱)
此中止不同于上文的“Template references a root the render context does not define(模板引用了渲染上下文未定义的根)”,二者值得区分,因为修复方法不同。那个中止在引用表面根本未定义的根时触发,或在形态固定的支柱下出现拼写错误的键时触发——例如在确实声明了 workload 的 Recipe 上使用 {{ .workload.containres }}。而此中止在对一个根本不存在的支柱进行拼写正确的引用时触发。
A template reads a rendered name the node’s provider does not report(模板读取了节点的 provider 未报告的渲染名称)
template reads the name the target gives the resources it renders for the node, and this node’s provider reports no such name; a conforming template reads a value the node’s own provider supplies (".context.rendered_name", provider "<provider>"). read {{ .context.instance_id }} instead: this node supplies no source of its own, so its resources are named after the node’s identity(模板读取了目标为该节点所渲染资源指定的名称,而该节点的 provider 不报告这样的名称;合规的模板应读取该节点自身的 provider 提供的值。请改为读取实例 ID:该节点不自带源,因此其资源以该节点的标识命名)
而节点提供了源、且其 provider 不推导这样的名称时:
template reads the name the target gives the resources it renders for the node, and this node’s provider reports no such name; a conforming template reads a value the node’s own provider supplies (".context.rendered_name", provider "<provider>"). write a value that does not depend on a name this target derives: it reports none for the output it renders from supplied source, so there is nothing of that kind to read here(模板读取了目标为该节点所渲染资源指定的名称,而该节点的 provider 不报告这样的名称;合规的模板应读取该节点自身的 provider 提供的值。请编写一个不依赖该目标所派生名称的值:对于从所提供的源渲染的输出,它不报告任何名称,因此这里没有此类内容可读)
template reads its callers’ render facts, but the FeatureRecipe does not set readsCallerRenderFacts (<reference>, written in <field>)(模板读取了其调用方的渲染事实,但该 FeatureRecipe 未设置 readsCallerRenderFacts)
pipeline step reads its callers’ render facts, but a pipeline step does not read the components connecting to its host; it reads only the host’s own render facts (<reference>, written in <field>)(流水线步骤读取了其调用方的渲染事实,但流水线步骤不读取连接到其宿主的组件;它只读取宿主自身的渲染事实)
引用相对于读取它的那个连接引用,即 .render_facts 或 .render_facts.<name>,与上一条相同;字段按 id 指明步骤:pipeline[<step>].with 或 pipeline[<step>].when。多个步骤读取这些事实时,每个步骤各有一份报告,位于一行指明它们共同之处的说明之下:
pipeline steps reading their callers’ render facts(读取其调用方渲染事实的流水线步骤)
template reads the render facts of a component its host is wired to, but the FeatureRecipe does not set readsTargetRenderFacts (<reference>, written in <field>)(模板读取了其宿主所连接组件的渲染事实,但该 FeatureRecipe 未设置 readsTargetRenderFacts)
pipeline step reads the render facts of a component its host is wired to, but a pipeline step reads only the host’s own render facts (<reference>, written in <field>)(流水线步骤读取了其宿主所连接组件的渲染事实,但流水线步骤只读取宿主自身的渲染事实)
引用的写法与上一条相同,字段按 id 指明步骤:pipeline[<step>].with 或 pipeline[<step>].when。多个步骤读取这些事实时,每个步骤各有一份报告,位于一行指明它们共同之处的说明之下:
pipeline steps reading the render facts of the components their host is wired to(读取其宿主所连接组件渲染事实的流水线步骤)
selector violation ("", declared on socket "", not satisfied by the labels of ""). Add the labels the selector requires to the target’s component type, or wire the socket to a component that already carries them.(选择器违规:目标的标签不满足该插槽上声明的选择器表达式。请为目标的组件类型添加选择器要求的标签,或将该插槽连接到已带有这些标签的组件。)
selector violation ("", declared by Feature "", not satisfied by the labels of ""). Add the labels the Feature’s appliesTo requires to this component’s type, or attach a Feature whose applicability the component already satisfies.(选择器违规:组件的标签不满足该 Feature 声明的 appliesTo 表达式。请为该组件的类型添加该 Feature 的 appliesTo 要求的标签,或附加一个该组件已满足其适用条件的 Feature。)
selector violation ("", declared by Feature "", which could not be evaluated: ""). Correct the appliesTo selector on the Feature’s catalog entity.(选择器违规:该 Feature 声明的 appliesTo 表达式无法求值。请更正该 Feature 目录实体上的 appliesTo 选择器。)
selector violation ("", declared on socket "", which could not be evaluated: ""). Correct the selector on the socket’s declaration in the component type’s usesSchema.(选择器违规:在套接字上声明的选择器无法求值。请在组件类型的 usesSchema 中更正该套接字声明上的选择器。)
[OPS_ERROR E0007] release.yaml at .spec.boundaries.main.components.app.features.metrics
selector violation ("component.aggrega.ai/type in (server, worker)", declared by Feature "core/prometheus-exporter", not satisfied by the labels of "app"). Add the labels the Feature's appliesTo requires to this component's type, or attach a Feature whose applicability the component already satisfies.
capability is served by more than one provider plugin; add a plugins.providers entry to select one: capability "<capability-name>" is served by more than one provider plugin (<plugin-1>, <plugin-2>); add a plugins.providers entry for "<capability-name>" selecting one(该能力由多个 provider 插件提供;请添加一个 plugins.providers 条目以选择其中之一)
boundary-level Feature’s output is routed to a dispatch path nothing assembles (boundary "<boundary>", feature "<instance>", dispatch path "<path>", provider "<provider>"). attach the Feature at a boundary whose output path also receives its components, or give the boundary’s components the directory the Feature’s output is routed to(边界级 Feature 的输出被路由到一个没有任何内容组装的分派路径。请将该 Feature 挂载到其输出路径同时接收其组件的边界上,或者为该边界的组件指定 Feature 输出被路由到的目录)
[OPS_ERROR E0365] release-compose.yaml at .spec.boundaries.bridge.features.gateway
boundary-level Feature's output is routed to a dispatch path nothing assembles (boundary "bridge", feature "gateway", dispatch path "bridge/compose", provider "compose"). attach the Feature at a boundary whose output path also receives its components, or give the boundary's components the directory the Feature's output is routed to
当违规的 Feature 不止一个时,这些发现会一起归在报告 boundary-level Features whose output is routed to a dispatch path nothing assembles 之下。
此终止针对的是变量。若在允许的变量之下拼错了键,例如 {{ .manifest.recipe_nmae }},则会报告上文的“Template references a root the render context does not define(模板引用了渲染上下文未定义的根)”,并列出 .manifest 确实定义的键,因为变量本身已被接受,只是键错了。
发出的消息:
path template references a field not in the documented allowlist ("<dotted-path>", written in "<directory|subDirectory>", the render context defines "<the variables that field may read>")(路径模板引用了不在文档所列允许列表中的字段)
boundary output directory does not name a directory beneath the output root (Release "<release>", boundary "<boundary>", directory: "<value>", output path "<path>"). write a directory beneath the output root, such as “deploy/prod” — no leading ”/”, no ”..” climbing above it, and not the output root itself(边界输出目录未指向输出根目录下的某个目录(依次为 Release、边界、directory 的值与输出路径)。请写一个输出根目录下的目录,例如 “deploy/prod”——不要以 “/” 开头,不要用 “..” 向上越出根目录,也不能是输出根目录本身)
boundary-level Feature instance name is not a directory name (Release "<release>", boundary "<boundary>", feature "<instance>"). rename the Feature instance under the boundary’s features to an ordinary name, such as “audit”(边界级 Feature 实例名称不是目录名(依次为 Release、边界与 feature 实例)。请将该边界 features 下的 Feature 实例重命名为普通名称,例如 “audit”)
**修复方法:**将 boundary 的 features: 下的实例重命名为普通名称。
Instance-ID collision across boundaries assembling to the same path(组装到同一路径的多个 boundary 之间发生实例 ID 冲突)
两个组装到同一 (path, provider) 元组的 boundary 贡献了实例 ID 相同的组件。合并后的组装无法区分这两个组件片段——单个 Helm chart 不能包含两个名为 web-server 的 Deployment,单个 docker-compose 文件也不能包含两个名为 api 的服务。
发出的消息:
multiple contributors share an instance ID at the same dispatch path: dispatch path "<path>" provider "<provider>" already contains node "<instance-id>" (contributing boundaries: [<boundaries>]); component instance IDs must be unique within an assembly group(多个贡献者在同一分发路径上共用一个实例 ID:该分发路径与 provider 下已包含同名节点(并列出参与贡献的边界);组件实例 ID 在一个组装组内必须唯一)
assembled output collision: two contributors write the same output path (output path "<output-path>", written by "<contributor-1> and <contributor-2>", assembled within "<boundary-1> and <boundary-2>")(组装输出冲突:两个贡献者写入同一输出路径(依次为输出路径、写入它的贡献者,以及组装所在的边界))
derived name collision: one name is derived more than once in one key space(派生名称冲突:同一名称在同一键空间中被多次派生) ("<name>", key space "<kind-of-name>", derived by component "<contributor>", provider "<provider>", dispatch path "<path>")
贡献者按其类别来命名,这也说明了其名称写在何处:组件实例为 derived by component,附加到边界的 feature 为 derived by feature。
derived name collision: one name is derived more than once in one key space(派生名称冲突:同一名称在同一键空间中被多次派生) ("<name>", key space "<kind-of-name>", derived by feature "<feature-name>", attached at boundary "<boundary-path>", provider "<provider>", dispatch path "<path>")
组件带有其渲染派生了该名称的那个附加项的键,因为组件对你写下的每个键各带一个附加项:
derived name collision: one name is derived more than once in one key space(派生名称冲突:同一名称在同一键空间中被多次派生) ("<name>", key space "<kind-of-name>", derived by component "<component>", carrying attachment "<attachment-key>", provider "<provider>", dispatch path "<path>")
derived name collision: one name is derived more than once in one key space(派生名称冲突:同一名称在同一键空间中被多次派生) ("<name>", key space "<kind-of-name>", derived more than once by component "<contributor>", provider "<provider>", dispatch path "<path>")
two things a plugin produced occupy one name in its output(插件生成的两项内容在其输出中占用了同一个名称)
cloudformation-provider: an export name a cross-boundary link derives is already declared by another Outputs entry in the same stack: the link derives the export name <export-name> for provides key <provides-key> of component <component> in boundary <boundary> of Release <release>, and another Outputs entry of the same stack already declares that same export name — that declaration sits under the stack output <stack-output>, a name this provider assembles rather than one a Recipe wrote; each shadowing Outputs entry spells its export name exactly as the halt does, so searching your Recipes for that name reaches the entry — rename the export name the entry declares, or remove that entry’s Export block and let the link publish the export(cloudformation-provider:跨边界链接派生的导出名称已由同一栈中的另一个 Outputs 条目声明:该链接为某个 Release 中某个边界内某个组件的某个 provides 键派生出该导出名称,而同一栈的另一个 Outputs 条目已声明了相同的导出名称——该声明位于某个栈输出之下,该名称由此 provider 组装,而非由 Recipe 编写;每个与之冲突的 Outputs 条目拼写其导出名称的方式与该终止信息完全一致,因此在你的 Recipes 中搜索该名称即可找到该条目——请重命名该条目声明的导出名称,或删除该条目的 Export 块,让链接发布该导出)
two things a plugin produced occupy one name in its output(插件生成的两项内容在其输出中占用了同一个名称)
cloudformation-provider: the stack output a cross-boundary link publishes its export on already carries an Export the link did not write: the link derives the export name <export-name> for provides key <provides-key> of component <component> in boundary <boundary> of Release <release>, and the stack output this provider assembles for that key and component <what-it-found>; remove that entry’s Export block and let the link publish the export every consumer imports(cloudformation-provider:跨边界链接发布其导出所在的栈输出已带有一个并非该链接写入的 Export:该链接为某个 Release 中某个边界内某个组件的某个 provides 键派生出该导出名称,而此 provider 为该键和组件组装的栈输出存在所发现的情况;请删除该条目的 Export 块,让链接发布所有消费者导入的导出)
<what-it-found> 为以下之一,顺序与上述形态一致:
already declares the export name <name>(已声明该导出名称)
already declares an export name that is not a string — one given as an intrinsic, which resolves at deploy time, so this provider cannot read what it spells(已声明一个不是字符串的导出名称——以内部函数给出,在部署时才解析,因此此 provider 无法读出其拼写)
already carries an Export block declaring no export name(已带有一个未声明导出名称的 Export 块)
already carries an Export that is not a block, where CloudFormation expects one carrying a Name(已带有一个不是块的 Export,而 CloudFormation 期望的是一个带有 Name 的块)
FeatureRecipe template references a field outside its scope’s allowlist(FeatureRecipe 模板引用了其作用域允许列表之外的字段)
一个带有 executionScope: boundary 的 FeatureRecipe 在为边界只运行一次的模板中——其 locals:、provides:、valuesMapping:、artifacts:,或某个 pipeline 步骤的 with: 或 when:——引用了仅限单个组件的字段,例如 .context.instance_id、.context.inject 或 .context.uses——这些字段在边界作用域中没有有意义的值。反之亦然:组件作用域的 FeatureRecipe(默认)引用 .boundary.* 字段时,会在同一个验证器处失败。验证在解析时针对相应作用域的字段允许列表运行,早于任何渲染工作。边界作用域 FeatureRecipe 的 injectMapping 不在此检查:它在挂载所到达的每个组件的上下文中为该组件各运行一次,因此读取的是 .context.*,其中对 .boundary 的引用由上文“Template references a root the render context does not define(模板引用了渲染上下文未定义的根)”报告。
发出的消息:
FeatureRecipe template references a per-component-only field with executionScope: boundary ("<dotted-path>", written in "<field>", the render context defines "<the roots the boundary-scope context defines>")(executionScope 为 boundary 的 FeatureRecipe 模板引用了仅限每个组件的字段)
[CATALOG_ERROR E0039] scope-probe-fr at .spec.valuesMapping
FeatureRecipe template references a per-component-only field with executionScope: boundary (".context.instance_id", written in "valuesMapping", the render context defines ".values, .infra, .locals, .provides, .features, .metadata, .steps, .source, .boundary")
这是由该表面的 .context 决定的:它只携带 instance_id、labels 和 annotations,别无其他。因此,.context.inject 和 .context.uses 是该表面的上下文未定义的键,该引用会按上文“Template references a root the render context does not define(模板引用了渲染上下文未定义的根)”所述,在解析时、任何渲染开始之前停止构建。诊断信息会指出该模板所属的机制和交付键,并列出 .context 在此处定义的键——因此同一份报告既涵盖真正试图读取跨节点数据的情况,也涵盖诸如 {{ .context.nmae }} 这样的普通拼写错误;后者是更常见的错误,否则会被渲染为空。
发出的消息——引用层面的细节;外围报告还会指出节点、机制和交付键:
template references a root the render context does not define(模板引用了渲染上下文未定义的根)(模板 self-inject.<mechanism>[<key>] 引用了 .context.inject,而 .context 定义的是 .context.instance_id、.context.labels、.context.annotations)
resolve: parse template at <name>:<version>.spec.locals.<key>, read by <name>:<version>.spec.source.<field>: resolve: source-template parse error (cause: template: <name>:<version>.spec.locals.<key>:1: function "<function>" not defined); a source field, and every locals entry it reads, is evaluated when the source is resolved with Aggrega’s own helpers only (optional, capitalizedWords and index), not the Sprig functions a render adds; write the value without that function, or move the value into a locals entry no source field reads
source: 字段自身调用该函数时,以相同方式报告,只指出该字段。
作用范围是坐标读取的条目。 解析坐标时,会对 source: 字段读取的每个 locals: 条目求值,并依次对这些条目读取的每个条目求值,此外不求值其他条目。没有 source: 字段触及的条目,在解析源时不会被求值、解析或检查,因此渲染所需的 local(例如用 Sprig 函数做算术,或依据 .context.instance_id 命名资源)对固定制品没有影响;它会在 Recipe 渲染时求值,其中的任何错误也在那时报告。字段读取哪些条目由其文本决定,因此以不指明具体条目的方式读取 .locals 的字段(如 {{ index .locals "version" }}、将整个块传给 optional 或绑定到变量)会使所有条目都被求值,而通过这种方式触及的条目的诊断会说明这一点:它不写 read by <field>,而是写 evaluated for <field>, which reads the locals block as a whole rather than by entry, so every entry is evaluated。
对于坐标读取的每个条目,引用顺序契约在这里同样适用。 解析坐标时,在其求值的每个条目中拒绝的引用与渲染时拒绝的相同:读取该块中在其下方声明的同级条目的条目,以及读取该块未声明的键的任何模板。两者都报告上文“locals: entry references a sibling defined later in the same block(locals: 条目引用了同一块中稍后定义的同级条目)”和“locals: key does not exist(locals: 键不存在)”下记录的条件——无论哪一种解析先遇到,条件相同,补救方法也相同——并且报告会指明该条目为之求值的 source: 字段。对于没有任何 source: 字段读取的条目,其中的错误会在 Recipe 渲染时以同一条件被拒绝。
resolve: evaluate template at <name>:<version>.spec.source.<field>: resolve: source-template evaluation failure at lock time (cause: template: … map has no entry for key "<key>"); it reads <name>:<version>.spec.locals.<key>, which could not be evaluated here (cause: template: … map has no entry for key "context")
source-version template at <name>:<version>.spec.source.<field> references .provides, which is an invalid reverse reference (locals feed provides, never the reverse) — refactor to read only .values and .infra (and .locals over the same): resolve: source-template references .provides (invalid reverse reference)
template: <template>:<line>:<column>: executing "<template>" at <index <map> <key>>: error calling index: template indexes a map with a key the map does not hold (key "<key>"). read a key that may be absent through a function that tests for it first, such as optional, get or hasKey(模板使用映射中不存在的键索引该映射;请通过先检测键是否存在的函数读取可能缺失的键,例如 optional、get 或 hasKey)
在以自身条件报告模板失败的表面上——provides: 条目(“A provides: template could not be evaluated”(无法对 provides: 模板求值))、参数插值(“A {{ .parameters.* }} reference cannot be interpolated”(无法插值 .parameters.* 引用))、schema 谓词(“An x-aggrega-when: or x-aggrega-validate: predicate cannot be evaluated”(无法对 x-aggrega-when: 或 x-aggrega-validate: 谓词求值))、source: 坐标(“Resolving a source: coordinate registers a narrower function set”(解析 source: 坐标时注册的函数集更窄))——报告头部带有该条件的代码,而上面那一行就是它所携带的原因,其中包含该键。
不会被打印:当读取位于 if、with 或 range 主体内,或位于 else 分支中时,因为该读取是否运行取决于某个条件,而该条件可能正是防止它遇到空内容的那个测试——因此在 range .values.user 旁边的 {{ if .values.user }}{{ .values.user }}{{ end }} 会像以往一样渲染。当它是守卫自身的测试、变量的赋值,或函数的参数时——{{ .values.user | quote }}、{{ toYaml .values.user }}——也不算打印,因为其输出是函数的结果而不是占位符。
在确实会运行的主体中打印不包含任何内容的路径,仍会写出 <no value>,这超出了本检查的范围。同一路径的一种写法与其他任何写法都是同一路径,因此以一种写法进行的打印与以另一种写法进行的 range 会被放在一起判断,消息引用模板最先写出的那种写法。包含值的路径会像以往一样打印和迭代,而父级不包含任何内容的路径则交由穿过空内容向下取值时本就会引发的中止来处理。
发出的消息,作为报告的最后一行——其上方的帧指出节点和模板,消息头带有本条件的代码:
template reads a path as a value and iterates it, and the data holds nothing at that path (path <path>). supply a value at the path, guard the printed read with an if or with over the path, or read it one way only(模板将某个路径作为值读取并对其进行迭代,而数据在该路径上不包含任何内容。请在该路径上提供一个值,用针对该路径的 if 或 with 守护被打印的读取,或只以一种方式读取它)
Aggregate 中的参数插值同样以本条件的代码报告同一行。provides: 条目在“A provides: template could not be evaluated(该模板无法求值)”下报告模板失败,因此在那里消息头带有该条件的代码,而上面这一行是它所带的原因,其中包含路径。
Recipe 或 FeatureRecipe 的值模板——上文“Missing template key — asymmetric policy(缺失模板键——非对称策略)”所列的模板之一,其中包括 Workload 主体、artifacts: 主体或 locals: 条目——已完成解析并开始运行,却在生成文本之前停止。使其停止的是模板引擎自身给出的原因,中止信息会将其附在下方:引用穿过了未提供任何内容的容器,例如在未编写 tls 的情况下引用 {{ .values.tls.ca }};比较两种不同类型的值,例如 {{ if eq .context.instance_id 1 }},它将文本与数字比较,并以 cannot compare text with a number 中止;或者调用 Sprig 的 fail,值模板可以借此用自己的消息拒绝某个输入。
这些模板上有四种失败会改为在各自的条件下报告。provides: 条目在下文“A provides: template could not be evaluated(该模板无法求值)”下报告,其消息中包含本句以及引擎给出的原因。对映射中不存在的键进行 index 读取,在上文“A template indexes a map with a key the map does not hold(模板以映射中不存在的键索引映射)”下报告。打印并迭代同一个不包含任何内容的路径的模板,会在运行之前被拒绝,在上文“A template reads and iterates a path that holds nothing(模板读取并迭代一个不包含任何内容的路径)”下报告。而无法解析的模板在运行之前就会停止,因此不属于本条件。
ir-verdict: plugin "<the attachment's uri>": with.settings does not satisfy the plugin’s declared settings schema: <what the schema check found>: policy attachment settings do not satisfy the plugin’s declared settings schema(策略挂接的设置不满足插件声明的设置 schema)
失败的对象以步骤的 id 和索引命名,其后的子句说明是哪一部分出了问题:渲染步骤的 with 输入、调用本身、宿主无法读取的输出、插件返回的错误、插件发出的错误级别诊断、补丁引擎拒绝的补丁,或者命名了遍历中不存在的作用域的补丁。
失败的步骤会被整体回滚。 文档恢复到该步骤运行之前的状态,步骤自身的输出也随之丢弃,因此后续步骤的 when 或 with 无法读取到部分结果。声明了 optional: true 的步骤随后以警告形式报告,遍历继续进行;非可选的步骤则会停止构建。optional:不容忍的是违反已声明的契约——见下一条。
输出的消息:
pipeline step failed: step "<id>" (index <n>) with: <what the render could not do>
pipeline step failed: step "<id>" (index <n>) invoke: <what the call could not do>
pipeline step failed: step "<id>" (index <n>) error diagnostic: <the plugin's message>
pipeline step failed: scope "<scope>" key "<key>": <what the patch engine refused>
pipeline step failed: unknown patch scope "<scope>"
pipeline step "<id>"with input does not satisfy the declared input contract: <what the schema check found>: pipeline step typed-I/O contract violation
pipeline step "<id>" returned outputs that do not satisfy the declared output contract: <what the schema check found>: pipeline step typed-I/O contract violation
对于契约未声明的诊断严重级别,消息出现在步骤失败的框架内:
pipeline step failed: step "<id>" (index <n>): <the severity the host could not route>: pipeline step typed-I/O contract violation
如果步骤的 with 模板读取了声明为敏感的值,输入违规不会列出任何值。 schema 检查的发现会被替换为每个失败位置及拒绝它的关键字,最后附上一条说明原因的提示——at '/origin': pattern (the value is withheld because the template that rendered this input reads a value declared sensitive)——因此需要修正的字段仍会被指出。参见 vocabulary/compact-form-authoring.md “What a refusal says about a declared value”。
两者都是遍历自身的拒绝,构建会针对其流水线生成该补丁的节点报告它们,因此上述消息出现在一条指出该节点的停止信息之下。该停止信息是这两种寻址错误导致构建停止的形式,记录在下文“A pipeline step addresses documents the node does not have(流水线步骤指向节点不具有的文档)”中——该条目还涵盖步骤可能无法定位任何内容的第三种地址:在不对应任何宿主组件的位置请求宿主组件的文档。
**如何修复:**问题出在插件,而不是你的文档。测试所期望的值在文档中不存在,通常意味着插件正运行在它并非为之编写的结构上——另一个 provider 的输出,或者已被同一流水线中较早步骤修改过的文档。如果补丁由你负责修正,可以将测试放宽为文档实际携带的内容,或者让步骤的 when 条件跳过该情况,而不是在补丁内部对其进行测试。
A workload: form and the fields beside it do not agree(workload: 的 form 与其旁边的字段不一致)
workload: 声明一个 form:——即所运行事物的形态,用每个目标都能理解的术语表述,而不是任何单一目标的词汇。有些字段只在某一种 form 上才有意义,而声明了 form 却缺少其所需字段,就没有任何一致的内容可渲染。两个方向都会检查,且在任何目标翻译该 workload 之前进行,因此这种不一致只针对你所写的内容报告一次,而不是每个目标以各自的说法各报告一次。
共强制检查 5 种配对,每种都会报告自己的一句话,指出两方以及应当如何书写:
workload declares a persistentTemplate volume but is not form: stateful; declare form: stateful(workload 声明了 persistentTemplate 卷,但不是 form: stateful;请声明 form: stateful)
workload is form: reference but declares no endpoint; set endpoint to the external host or URL the reference points at(workload 为 form: reference,但未声明 endpoint;请将 endpoint 设为该引用指向的外部主机或 URL)
workload declares an endpoint but is not form: reference; declare form: reference or remove the endpoint(workload 声明了 endpoint,但不是 form: reference;请声明 form: reference 或移除 endpoint)
workload is form: scheduled but declares no schedule; set schedule to a 5-field cron expression or an @-macro (e.g. @daily)(workload 为 form: scheduled,但未声明 schedule;请将 schedule 设为 5 字段 cron 表达式或 @ 宏(例如 @daily))
workload declares a schedule but is not form: scheduled; declare form: scheduled or remove the schedule(workload 声明了 schedule,但不是 form: scheduled;请声明 form: scheduled 或移除 schedule)
**有一种配对只单向检查。**没有逐副本声明模板的 form: stateful workload 是普通情况,不会引发任何报告——规则是声明模板需要只有该 form 才提供的稳定逐副本标识,而不是该 form 需要声明模板。另外两种配对则双向检查,因为 endpoint 和 schedule 各自都只在唯一一种 form 上有意义。
workload validation failed (Workload in Recipe <name>:<version>, at <path>, schema stage): .endpoint: value matches a shape that is not allowed here(workload 验证失败,schema 阶段:endpoint 的值匹配了此处不允许的形状)
workload declares suspend but is not form: scheduled; declare form: scheduled with a schedule or remove suspend(workload 声明了 suspend,但不是 form: scheduled;请声明带有调度的 form: scheduled,或移除 suspend)
artifacts $import: is not a bare-name artifact-library reference (#/artifacts/): "<the value as written>"(artifacts $import: 不是裸名称的 artifact-library 引用)
valuesMapping $import: is not a bare-name mapping-library reference (#/mappings/): "<the value as written>"(valuesMapping $import: 不是裸名称的 mapping-library 引用)
workload $import: is not a bare-name workload-library reference (#/workloads/): "<the value as written>"(workload $import: 不是裸名称的 workload-library 引用)
artifacts $import: is not a bare-name artifact-library reference (#/artifacts/): version separator is ’:’, not ’@’ — use "<the corrected value>"(artifacts 的 $import: 不是裸名称形式的制品库引用:版本分隔符是 ’:‘,而不是 ’@‘,请改用修正后的值)
artifacts $import: is not a bare-name artifact-library reference (#/artifacts/) ("<the value as written>", bundle "<bundle>", bundle file "<filename>", artifacts entry "<key>"). a bundle file body cannot import another bundle — compose the two at the artifacts entry that consumes them(artifacts $import: 不是裸名称的 artifact-library 引用。bundle 文件主体不能导入另一个 bundle——请在使用它们的 artifacts 条目处组合二者)
artifacts $import: is not a bare-name artifact-library reference (#/artifacts/): bundle "<bundle>" file "<filename>" body is a field-root $import: (nested library import inside a bundle file is not supported; compose at the consumption site)(artifacts $import: 不是裸名称的 artifact-library 引用:bundle 文件主体是字段根级 $import:(不支持在 bundle 文件内嵌套库导入;请在使用处组合))
valuesMapping $import: is not a bare-name mapping-library reference (#/mappings/) ("<the value as written>"). name the library and the entry either side of the fragment — write #/mappings/(valuesMapping 的 $import: 不是裸名称形式的映射库引用。请在片段两侧分别写出库名和条目名)
workload $import: is not a bare-name workload-library reference (#/workloads/) ("<the value as written>"). name the library and the entry either side of the fragment — write #/workloads/(workload 的 $import: 不是裸名称形式的工作负载库引用。请在片段两侧分别写出库名和条目名)
**如何修复:**将该值改写为 <Library>#<entry-path>,仅在需要为可选版本设定下限时,才在库名称之后添加 :<version>。检查片段是否与字段匹配——在 workload: 上使用 #/mappings/… 的条目路径,指向的是该字段不读取的表面,会在此报告,而不是作为缺失条目报告。同样的身份形式也适用于 schema 的 $ref:,其拒绝情况记录在上文的“A $ref: is not written in a form the compiler can resolve(未以编译器能够解析的形式书写)”中。
A library $import: names a library or an entry the catalog does not hold(库导入指向的库或条目不在目录中)
artifact-library import references an ArtifactLibrary not present in the catalog: ArtifactLibrary "<library>" (bundle "<entry>")(artifact-library 导入引用了目录中不存在的 ArtifactLibrary)
mapping-library import references a MappingLibrary not present in the catalog: MappingLibrary "<library>" (entry "<entry>")(mapping-library 导入引用了目录中不存在的 MappingLibrary)
workload-library import references a WorkloadLibrary not present in the catalog: WorkloadLibrary "<library>" (entry "<entry>")(workload-library 导入引用了目录中不存在的 WorkloadLibrary)
条目不存在:
artifact-library import references a bundle not present in the ArtifactLibrary: bundle "<entry>" in ArtifactLibrary "<library>"(artifact-library 导入引用了 ArtifactLibrary 中不存在的 bundle)
mapping-library import references an entry not present in the MappingLibrary: entry "<entry>" in MappingLibrary "<library>"(mapping-library 导入引用了 MappingLibrary 中不存在的条目)
workload-library import references an entry not present in the WorkloadLibrary: entry "<entry>" in WorkloadLibrary "<library>"(workload-library 导入引用了 WorkloadLibrary 中不存在的条目)
artifact-library import references a bundle not present in the ArtifactLibrary ("<entry>", ArtifactLibrary "<library>", artifacts entry "<key>")(artifact-library 导入引用了 ArtifactLibrary 中不存在的 bundle)
mapping-library import references an entry not present in the MappingLibrary ("<entry>", MappingLibrary "<library>")(mapping-library 导入引用了 MappingLibrary 中不存在的条目)
workload-library import references an entry not present in the WorkloadLibrary ("<entry>", WorkloadLibrary "<library>")(workload-library 导入引用了 WorkloadLibrary 中不存在的条目)
library $import: carries a registry host; reference the library by bare-name identity: "<the value as written>"(库 $import: 携带了 registry 主机;请按裸名称身份引用该库)
它按 Recipe 针对该 Recipe 自身的输出触发,这正是它与组装中两个不同贡献者落到同一路径的区别——后者是上文的“Two contributors write the same output path(两个贡献者写入同一输出路径)”,补救方法不同。
发出的消息:
artifacts output filename collision: two artifact outputs carry the same filename (Recipe "<recipe>", artifact output "<filename>" emitted more than once)(artifacts 输出文件名冲突:两个 artifact 输出使用了相同的文件名)
artifact-library bundle file name does not name a file of its own beneath the artifacts key its output is nested under ("<filename>", ArtifactLibrary "<library>", artifacts entry "<key>"). rename the file inside the ArtifactLibrary bundle to an ordinary file name beneath the artifacts key it is consumed at, such as “config.yaml” or “rbac/role.yaml” — no ”.” or ”..” part, and no leading, trailing or doubled ”/“(artifact-library bundle 文件名未在其输出所嵌套的 artifacts 键之下指定属于自己的文件。请将 ArtifactLibrary bundle 中的该文件重命名为其使用所在 artifacts 键之下的普通文件名,例如 “config.yaml” 或 “rbac/role.yaml”——不含 ”.” 或 ”..” 部分,也不含开头、末尾或重复的 ”/”)
artifact-library bundle file name does not name a file of its own beneath the artifacts key its output is nested under (Recipe "<recipe>", artifact "<key>", bundle file "<filename>"). rename the file inside the ArtifactLibrary bundle to an ordinary file name beneath the artifacts key it is consumed at, such as “config.yaml” or “rbac/role.yaml” — no ”.” or ”..” part, and no leading, trailing or doubled ”/“(artifact-library bundle 文件名未在其输出所嵌套的 artifacts 键之下指定属于自己的文件。请将 ArtifactLibrary bundle 中的该文件重命名为其使用所在 artifacts 键之下的普通文件名,例如 “config.yaml” 或 “rbac/role.yaml”——不含 ”.” 或 ”..” 部分,也不含开头、末尾或重复的 ”/”)
imported artifact content does not match the digest recorded for it in entity.lock ("<artifact>", imported file "<path>", its content digests to "<digest>", the recorded pin is "<digest>"). If the file was changed on purpose, run aggrega pin on the entity that imports it to record its new digest; otherwise restore the file(导入的 artifact 内容与 entity.lock 中为其记录的摘要不匹配。如果文件是有意修改的,请对导入它的实体运行 pin 以记录新摘要;否则请恢复该文件)
imported artifact content does not match the digest recorded for it in entity.lock ("<artifact>", imported file "<path>", its content digests to "<digest>", the recorded pin is "<digest>", attachment "<attachment>"). If the file was changed on purpose, run aggrega pin on the entity that imports it to record its new digest; otherwise restore the file(导入的 artifact 内容与 entity.lock 中为其记录的摘要不匹配,并给出附加项。如果文件是有意修改的,请对导入它的实体运行 pin 以记录新摘要;否则请恢复该文件)
the files of the entity’s local source do not match the pins recorded for them in entity.lock (file <path> digests to <digest> and its recorded pin is <digest>). If the source was changed on purpose, run aggrega pin on the entity to record its files again; otherwise restore the files(实体本地源的文件与 entity.lock 中为其记录的固定值不匹配(该文件的摘要与为其记录的固定值不同)。如果源是有意更改的,请对该实体运行 aggrega pin 以重新记录其文件;否则请恢复这些文件)
the files of the entity’s local source do not match the pins recorded for them in entity.lock (file <path> digests to <digest> and no pin is recorded for it). If the source was changed on purpose, run aggrega pin on the entity to record its files again; otherwise restore the files(实体本地源的文件与 entity.lock 中为其记录的固定值不匹配(该文件有摘要,但没有为其记录固定值)。如果源是有意更改的,请对该实体运行 aggrega pin 以重新记录其文件;否则请恢复这些文件)
the files of the entity’s local source do not match the pins recorded for them in entity.lock (file <path> is no longer in the source and its recorded pin is <digest>). If the source was changed on purpose, run aggrega pin on the entity to record its files again; otherwise restore the files(实体本地源的文件与 entity.lock 中为其记录的固定值不匹配(该文件已不在源中,但仍记录有其固定值)。如果源是有意更改的,请对该实体运行 aggrega pin 以重新记录其文件;否则请恢复这些文件)
a symbolic link sits among the files an entity carries (<path>). remediation: replace the link with a copy of what it points to, placed inside the entity’s own directory. A link met inside a source directory can instead be left out with a line in the .aggregaignore beside the entity, which takes effect when the entity is pinned again. A link is refused rather than followed because the bytes it points to would travel under the link’s name, from wherever it points(实体携带的文件中存在符号链接。补救方法:将该链接替换为其所指内容的副本,并放在实体自身的目录中。对于源目录中遇到的链接,也可以在实体旁的 .aggregaignore 中添加一行将其排除,该设置在重新固定实体时生效。链接会被拒绝而不是被跟随,因为它所指向的字节无论来自何处,都会以该链接的名称被携带)
**修复方法:**如果实体需要链接所指向的内容,请将链接替换为实体目录中该内容的副本,然后重新固定实体。如果链接只是为了你自己的方便而存在、实体并不读取它,请将其路径添加到实体文档旁的 .aggregaignore 中,然后重新固定。Which files ship with an entity 介绍了决定实体携带哪些内容的规则。
An entity reads an input the lock beside it records no pin for(实体读取了其旁锁文件未记录固定值的输入)
an input the entity reads has no pin recorded for it in the entity.lock beside it (Recipe "<name>", remote source <url>@<version>: no pin recorded, imported file <key>: the recorded pin no longer matches it). remediation: run aggrega pin <entity-path> and commit the entity.lock it writes beside the entity; to have every pull in this workspace record the pins itself instead, set pin_sources_at_pull: true in the workspace configuration
an input the entity reads has no pin recorded for it in the entity.lock beside it (Recipe "<name>", remote source <url>@<version>: no pin recorded). remediation: run aggrega pin <entity-path> and commit the entity.lock it writes beside the entity; to have this publication record the pins itself instead, re-run it with --pin-sources; to have every publication in this workspace record them, set pin_sources_at_push: true in the workspace configuration
Recipe or FeatureRecipe does not publish a provides key its abstract entity’s schema.provides contract declares ("<key>", declared by component type "<type>", bound to component instance "<instance>")(Recipe 或 FeatureRecipe 未发布其抽象实体的 schema.provides 契约所声明的 provides 键)
Recipe or FeatureRecipe does not publish a provides key its abstract entity’s schema.provides contract declares (<attachment context>, <the FeatureRecipe> does not publish provides key "<key>" declared by <the Feature>’s schema.provides contract)(Recipe 或 FeatureRecipe 未发布其抽象实体的 schema.provides 契约所声明的 provides 键)
**引用一个没有任何来源提供的键也会在此报告。**该表面以严格的缺失键处理方式求值,正是为了让引用渲染为空的谓词无法与“无”比较并悄然通过——否则一个拼写错误就会使断言本应强制执行的规则失效。这也是为什么普通的 default 在此表面上无法提供回退值:裸引用会在回退执行之前就停止求值。请用 hasKey 守护该引用,或使用 optional 辅助函数;通过 index 读取同样会停止并指出该键,如“A template indexes a map with a key the map does not hold(模板使用映射中不存在的键进行索引)”所述。
**声明为敏感的值不会出现在消息中。**当断言读取此类值,并以完整写成单个带引号字符串的语句调用 fail 时(即 fail "…",既没有通过管道传入任何内容,也没有进行任何拼接),无论该值的内容是什么,消息都会原样包含该语句,因为该语句没有引用断言读取的任何内容。当其消息引用了该值时,消息会在该值的位置显示 <redacted>。当消息以其他任何方式拼接而成,且断言的行为取决于该值的内容时,失败表达式之后的消息会被替换为 failure text withheld: this template reads a value declared sensitive, and the failure depends on what that value holds;停止及其代码保持不变。哪些算作已声明,以及哪些拒绝不在此范围内,参见 vocabulary/compact-form-authoring.md 中的“What a refusal says about a declared value”。
**单独检查实体时,失败的断言会作为警告报告。**给定 Recipe 文件的 aggrega validate、编辑器通过 aggrega serve 对该文件的检查,以及给定 entity 的 aggrega mcp 的 validate 工具,都会基于占位符和 schema 默认值而非 Release 设置的值来构建该 Recipe,因此无法区分等待 Release 的断言与已损坏的断言。在这些场景中,调用 fail 的断言——无论是 Recipe 自身的,还是它所实现的 Component 声明的——会作为警告报告,附带上述消息,并以句子 A Release must satisfy this assertion before a build of it can pass. 结尾,检查仍会通过。引用无来源提供的键以及无法解析的断言不属于失败的断言:二者都是断言自身文本中的错误,该检查会像对待其他错误一样判定它们。构建总是有一个 Release,并会按此处所述在断言上停止;参见失败的断言是一个警告。
pipeline /host operation from a step with no host component(来自没有宿主组件的步骤的管道 /host 操作)
pipeline /host operation from a step with no host component ("<attachment>")(来自没有宿主组件的步骤的管道 /host 操作,附挂载)
这三种情况是流水线遍历本身所报告的寻址拒绝的构建停止形式,见上文的“A pipeline patch addresses a document the set does not hold, or one with no tree to address(流水线补丁寻址了集合中不存在的文档,或没有可寻址树的文档)”。
pipeline PATCH targets an assembler provider’s pre-assembly fragments ("<attachment>")(管道 PATCH 指向组装型 provider 的组装前片段,附挂载)
pipeline PATCH targets an assembler provider’s pre-assembly fragments (node "<instance>", <scope>-scope document "<key>" is rendered by an assembler provider). the post-assembly phase re-runs this PATCH once the documents are discrete(管道 PATCH 指向组装型 provider 的组装前片段,该作用域的文档由组装型 provider 渲染;文档分离后,组装后阶段会重新运行此 PATCH)
pipeline plugin is not compatible with the rendering provider ("<provider>")(管道插件与执行渲染的 provider 不兼容,附 provider)
pipeline plugin is not compatible with the rendering provider ("<attachment>", "<provider>")(管道插件与执行渲染的 provider 不兼容,附挂载与 provider)
rendering node "<instance>": node "<instance>" (provider "<provider>"): two renders of identical input produced different output: provider render is not deterministic
an omits entry left out nothing the source rendered (node "<node-id>", provider "<provider>", "<document>" omits[<position>], kind "<kind>", name "<name>", namespace "<namespace>"). correct the entry so it names something the source renders, or remove it; a source upgrade that renamed or removed it is the usual cause
a provider’s omitted counts do not match the omits entries it was handed (node "<node-id>", provider "<provider>", handed <n> omits entries, returned <m> omitted counts)(provider 的省略计数与交给它的 omits 条目不匹配)
a template does more than copy a value it reads off a cross-boundary link (template "<template>", provides key "<key>" that component "<consumer>" reads off its connection "<alias>" on socket "<socket>" to component "<producer>"). Copy the value as it stands, whole or inside a larger string, because the provider writes in its place what the value becomes in the other output, and branch on a value of the component’s own instead(模板对从跨边界链接读取的值所做的不只是复制:消息列出模板、provides 键、通过某个插座上的连接读取该键的消费方组件,以及生产方组件。请按原样复制该值,完整写出或放在更长的字符串中,因为 provider 会在其位置写入该值在另一个输出中的形式;请改为基于组件自身的值进行分支)
**修复方法:**复制消息指出的值,而不是对其进行测试或转换,并基于消费方 component 自己编写的值(它自身的某个 values 或 infra 键)作出判断,而不是基于其连接读取到的值。CloudFormation provider 说明了被复制的值在另一个栈中会变成什么。
A provider named a directory for a contributor that is not one directory(provider 为贡献者指定的目录不是单个目录)
provider named a directory for each contributor’s own sub-directory that is not a single directory name: provider "<provider>" declared nest_segment "<value>"; the value must name one directory, carrying no path separator and naming neither the current nor the parent directory(provider 为每个贡献者自身子目录指定的目录不是单个目录名:该值必须指定一个目录,不含路径分隔符,且既不指向当前目录也不指向父目录)
attachment binds a FeatureRecipe with executionScope: boundary and no boundary holding the component declares it ("<attachment>", on a component in boundary "<boundary>")(附加绑定了 executionScope: boundary 的 FeatureRecipe,但包含该组件的边界均未声明它)
对于不属于任何作用域的组件,不提供此类值:
attachment binds a FeatureRecipe with executionScope: boundary and no boundary holding the component declares it ("<attachment>")(附加绑定了 executionScope: boundary 的 FeatureRecipe,但包含该组件的边界均未声明它)
plugin "<plugin>" declares abi_version "<declared>"; host speaks "<supported>": wasm: plugin rejected by the sandbox(插件声明的 abi_version 与宿主支持的版本不符:wasm:插件被沙箱拒绝)
宿主没有对应词汇的插件类型:
plugin "<plugin>" declares unknown plugin_type "<declared>": wasm: plugin rejected by the sandbox(插件声明了未知的 plugin_type:wasm:插件被沙箱拒绝)
无法读取的自我报告:
wasm: plugin "<plugin>" describe() output is not valid JSON: <what the read reported>: wasm: plugin rejected by the sandbox(wasm:插件的 describe() 输出不是有效的 JSON:wasm:插件被沙箱拒绝)
缺少其类型所要求导出的插件,该导出取自读取类型本身的同一注册表:
<kind> plugin "<plugin>" declares no "<export>" export: wasm: plugin rejected by the sandbox(插件未声明其类型所要求的导出:wasm:插件被沙箱拒绝)
plugin "<plugin>" export "<export>" declares unknown scope "<declared>" (want "own", "host", or empty): wasm: plugin rejected by the sandbox(插件的导出声明了未知的 scope:wasm:插件被沙箱拒绝)
声明了成对能力却未同时提供两个导出,或提供了导出却未声明该能力:
plugin "<plugin>" declares the cross-boundary linking capability but does not export both "link_publish" and "link_resolve": wasm: plugin rejected by the sandbox(插件声明了跨边界链接能力,但未同时导出 link_publish 和 link_resolve:wasm:插件被沙箱拒绝)
plugin "<plugin>" (plugin_type "provider") serves the capability "<name>", which contains a colon; a Recipe’s capability reference is read as the capability up to its last colon and a version pin after it, so no Recipe can name "<name>": report the capability name without a colon: wasm: plugin rejected by the sandbox(插件提供的能力名称包含冒号;Recipe 的能力引用以最后一个冒号之前的部分作为能力名称、之后的部分作为版本固定,因此任何 Recipe 都无法引用该名称:请报告不含冒号的能力名称:wasm:插件被沙箱拒绝)
plugin "<plugin>" declares host function "<name>" in describe() that its wasm does not import: wasm: plugin rejected by the sandbox(插件在 describe() 中声明了其 wasm 并未导入的宿主函数:wasm:插件被沙箱拒绝)
plugin "<plugin>" imports host function "<name>" that its describe() does not declare: wasm: plugin rejected by the sandbox(插件导入了其 describe() 未声明的宿主函数:wasm:插件被沙箱拒绝)
wasm: plugin "<plugin>": expected a <kind in words> plugin (plugin type "<expected>") but its describe() reports plugin type "<reported>": wasm: declared plugin type does not match plugin describe()(wasm:插件类型与预期不符,其 describe() 报告了另一种插件类型:wasm:声明的插件类型与插件的 describe() 不匹配)
call "<export>": wasm: guest plugin returned an output that is not the shape the socket reads: <what could not be read>(调用该导出:wasm:guest 插件返回的输出不是插槽所读取的结构,并附上无法读取的内容)
plugin "<plugin>" call "<export>": wasm: guest plugin returned a diagnostic whose severity the contract does not declare: diagnostic <index> has severity "<value>"; the declared severities are "halt", "warn" and "info"(插件调用该导出:wasm:guest 插件返回的诊断的严重级别未在契约中声明:给出该诊断的索引及其严重级别;已声明的严重级别为 halt、warn 和 info)
provider guest returned two output files under one path; a conforming guest returns each output path at most once (path "<path>", node "<node>")(provider guest 在同一路径下返回了两个输出文件;符合规范的 guest 对每个输出路径最多返回一次,并给出该路径和节点)
A provider reported a render fact whose value is not a list(provider 报告的渲染事实的值不是列表)
provider 可以在其文件之外报告关于其渲染输出的事实——每个事实包含一个名称和一个值,使用该 provider 自己文档中定义的词汇——挂接到 component 上的 Features 会在其模板中读取这些事实。每个事实的值都是一个列表,即使只有一个条目:同一个名称可能由 component 的多次渲染报告,包括其自身 provider 的调用以及挂接到它的 Features 的渲染,这些列表会在该名称下合并为一个,供读取它的模板使用。provider 在渲染时无法知道自己的报告是否会是该名称下唯一的一个,因此值为对象、字符串、数字、布尔值或 null 时,会在 provider 交出它时被拒绝,对每次渲染都如此,无论是否有模板读取该事实。
输出的消息,指明该事实、报告它所针对的节点、报告它的 provider,以及值的类型:
provider guest reported a render fact whose value is not a list; a conforming guest reports every render fact’s value as a JSON array, even with one entry (fact "<fact>", node "<node>", provider "<provider>", its value is <kind>)(provider guest 报告的渲染事实的值不是列表;符合规范的 guest 会将每个渲染事实的值报告为 JSON 数组,即使只有一个条目)
link patch names an output file the dispatch group did not emit; a conforming link patch names a file the group’s own render returned (file "<file>", node "<node>")(link patch 指定了一个分派组未输出的输出文件;符合规范的 link patch 指定的是该组自身渲染返回的文件)
emit_file side effect carries no file; a conforming emit_file side effect carries a file with its path and content (node "<node>", side effect <index>)(emit_file 副作用未携带文件;符合规范的 emit_file 副作用会携带一个包含路径和内容的文件)
side effect declares a kind the plugin contract does not define; a conforming side effect declares emit_file or emit_crd (node "<node>", side effect <index>, kind "<value>")(副作用声明了插件契约未定义的种类;符合规范的副作用声明 emit_file 或 emit_crd)
reassemble names a patched unit token the carve did not produce; a conforming codec carves and reassembles a file under the same tokens (token "<token>", file "<file>")(reassemble 指定了 carve 未产生的已修补单元 token;符合规范的 codec 会在相同的 token 下切分并重组文件)
a plugin has no expression for a construct this build declares(插件无法表达此次构建所声明的构造)
compose: workload form "<form>" has no compose mapping; compose supports stateless and stateful only: compose cannot express this workload form(compose:该 workload 形式没有 compose 映射;compose 仅支持 stateless 和 stateful:compose 无法表达此 workload 形式)
a plugin has no expression for a construct this build declares(插件无法表达此次构建所声明的构造)
compose: node "<node>" container "<container>": compose: node "<node>" declares container lifecycle hooks; compose has no lifecycle-hook primitive: compose has no lifecycle-hook primitive; container declares lifecycle hooks(compose:节点、容器:compose:该节点声明了容器生命周期钩子;compose 没有生命周期钩子原语:compose 没有生命周期钩子原语;容器声明了生命周期钩子)
a plugin has no expression for a construct this build declares(插件无法表达此次构建所声明的构造)
compose: node "<node>" container "<container>": compose: node "<node>" declares container envFrom; compose has no env-from-object primitive: compose has no env-from-object primitive; container declares envFrom(compose:节点、容器:compose:该节点声明了容器 envFrom;compose 没有 env-from-object 原语:compose 没有 env-from-object 原语;容器声明了 envFrom)
a plugin has no expression for a construct this build declares(插件无法表达此次构建所声明的构造)
compose: an omits entry (name "<name>") names kind "<kind>": compose leaves out a service, a volume or a config, each named by its key under services:, volumes: or configs:, and no other kind(compose:某个 omits 条目指定了该 kind:compose 只会省略 service、volume 或 config,分别以其在 services:、volumes: 或 configs: 下的键命名,不支持其他 kind)
a plugin has no expression for a construct this build declares(插件无法表达此次构建所声明的构造)
compose: an omits entry (kind "<kind>", name "<name>") names namespace "<namespace>", and a compose file has no namespaces: compose leaves out a service, a volume or a config, each named by its key under services:, volumes: or configs:, and no other kind; remove the namespace from the entry(compose:某个 omits 条目指定了 namespace,而 compose 文件没有 namespace:compose 只会省略 service、volume 或 config,分别以其在 services:、volumes: 或 configs: 下的键命名,不支持其他 kind;请从该条目中删除 namespace)
a plugin has no expression for a construct this build declares
cloudformation-provider: an omits entry (kind "<kind>", name "<name>") names namespace "<namespace>", and a CloudFormation template has no namespaces: cloudformation leaves out a resource, named by its Type as the entry’s kind and its logical ID under Resources as the entry’s name; remove the namespace from the entry
a plugin has no representation for a value it was given
compose: node "<node>" apply service ports: compose publishes a port’s transport as a tcp or udp suffix; this port declares a transport compose cannot express
a plugin has no representation for a value it was given
compose: node "<node>" container "<container>": compose: the <cpu|memory|nvidia.com/gpu><request|limit> at <path>: "<value>" is not a quantity: <reason>; a quantity is a number such as 2, 0.5 or 1.5, with an optional sign and at most one of an integer exponent (1e3, 5E-2) or a unit suffix (n, u, m, k, M, G, T, P, E, Ki, Mi, Gi, Ti, Pi, Ei): resources quantity cannot be converted to a compose deploy.resources value
对于 compose 无法表示的数量,其后会给出 compose 对该资源所能容纳的范围:
a plugin has no representation for a value it was given
compose: node "<node>" container "<container>": compose: the memory <request|limit> at <path> is "<value>", a quantity compose cannot represent exactly; a compose memory value is a whole number of bytes from 0 to 9223372036854775807: resources quantity cannot be converted to a compose deploy.resources value
a plugin has no representation for a value it was given
compose: node "<node>" container "<container>": compose: the cpu <request|limit> at <path> is "<value>", a quantity compose cannot represent exactly; a compose cpus value is a core count from 0 to 9223372036.854775807 with at most nine decimal places: resources quantity cannot be converted to a compose deploy.resources value
a plugin has no representation for a value it was given
compose: node "<node>" container "<container>": compose: the nvidia.com/gpu <request|limit> at <path> is "<value>", a quantity compose cannot represent exactly; a compose device count is a whole number of devices from 0 to 9223372036854775807: resources quantity cannot be converted to a compose deploy.resources value
GPU 请求和限制要求不同数量时,消息会指出两个路径和两个数量:
a plugin has no representation for a value it was given
compose: node "<node>" container "<container>": compose: the nvidia.com/gpu request at <path> and the limit at <path> ask for different counts (<request> and <limit>); compose reserves one device count for a service, so write the same count in both or only the limit: resources quantity cannot be converted to a compose deploy.resources value
a plugin has no representation for a value it was given
helm: node "<node>": <path>: "<value>" is not a quantity: <reason>; a quantity is a number such as 2, 0.5 or 1.5, with an optional sign and at most one of an integer exponent (1e3, 5E-2) or a unit suffix (n, u, m, k, M, G, T, P, E, Ki, Mi, Gi, Ti, Pi, Ei)
修复方法: 按 Workload → 资源数量 中规定的格式写入该值。若字段使用了模板,需要修复的是模板读取的值:像 m 或 Mi 这样单独的后缀,是模板插入的值为空时留下的结果;而 Release 参数会按其原样传到该字段。
A service type the helm provider cannot render(helm provider 无法渲染的服务类型)
helm provider 将每个 Workload services 条目渲染为一个 Kubernetes Service,其类型为该条目的 type。Loopback 条目要求其端口只能从主机自身的回环地址访问,而 Kubernetes Service 没有能做到这一点的类型:NodePort Service 在哪些节点地址上监听,是整个集群的设置,而不是单个 Service 的设置。因此构建会在写入任何资源之前,于第一个 Loopback 条目处停止(按服务声明的顺序)。
构建会停止,而不是将该条目渲染为其他类型,因为 Service 现有的每种类型都会改变端口的可达范围:ClusterIP Service 会丢掉条目所要求的对外发布,而 NodePort Service 会在集群允许的每个节点地址上发布该端口——这正是该条目要避免的更大暴露面。
输出消息。 消息以该条件开头,然后给出节点、服务在 Workload 中的路径以及类型:
a plugin has no representation for a value it was given
helm: node "<node>": services.<service>: type “Loopback” publishes the service’s ports on the host’s loopback address only, and a Kubernetes Service has no type that does; declare ClusterIP to keep the ports inside the cluster, or NodePort or LoadBalancer to publish them outside it
a plugin has no representation for a value it was given
helm: node "<node>" in boundary "<boundary>": annotation aggrega.ai/kubernetes-version: "<value>" is not a Kubernetes version a chart can be rendered for: <reason>; write the version of the cluster the chart deploys to, such as “1.31” or “v1.31.2”, on the component or on its boundary
a plugin could not resolve something it requires to exactly one value
compose: node "<node>" container "<container>": probe http: requires at least one container port; container declares none
a plugin could not resolve something it requires to exactly one value
compose: node "<node>" container "<container>": probe declares no shape (http/tcp/exec)
a plugin could not resolve something it requires to exactly one value(插件无法将其所需的某项解析为唯一值)
compose AssembleBoundary: service "<service>" references config "<name>" mounted at "<path>"; declare each one as a top-level configs: entry from the Recipe’s artifacts: input: configmap volume requires a file emitted via the Recipe’s artifacts: input; none found
该检查读取声明该条目的 Recipe 或 FeatureRecipe 自身的文件,因此即使同一组装文件的另一个贡献者声明了与被省略单元同名的单元,渲染仍会停止。报告的是所有引用,而不只是第一个——先按键顺序列出 services,然后是 jobs,每个 service 的钩子紧随其后——因此一次构建就能列出全部引用。
输出的消息。先给出状况,然后是每个引用方条目、它引用的单元以及引用所在的字段:
a plugin could not resolve something it requires to exactly one value(插件无法将其所需的某项解析为唯一值)
compose: what an omits entry left out is still named by the file: service "<service>" names <kind>"<name>" at <field>; compose refuses a file naming a service, a volume or a config it does not declare: leave out what names it as well, change the reference through valuesMapping, or remove the entry
若某单元条目的名称由声明为敏感的值构建,则显示为 <redacted>。
**修复方法:**确定你本意是两者中的哪一种。如果引用方 service 仍需要该单元,就保留它:移除该条目。如果不需要,通过 Recipe 的 valuesMapping: 修改引用——其中的列表会替换基础文件的列表,因此 depends_on: [] 可将其清空——或用单独的条目将引用方 service 也省略掉。
What an omits entry left out is still named by a CloudFormation template(omits 条目省略的内容仍被 CloudFormation 模板引用)
omits: 条目会从来源 CloudFormation 模板中省略某个资源,而 CloudFormation 会拒绝引用了未声明资源的模板。因此,在移除条目对应的资源后,其余模板对其中任一资源的每个引用都会停止渲染:Ref、列表形式或点分字符串形式的 Fn::GetAtt、资源的 DependsOn,或 Fn::Sub 的变量——在每个资源的主体和每个输出中的任何位置读取。完整列表以及只是看起来像引用的值,见 cloudformation → Leaving resources out of a sourced template。
该检查一并读取声明该条目的 Recipe 或 FeatureRecipe 自身的模板:对这些模板中另一个仍在声明的逻辑 ID 的引用不会被停止,而对被省略资源的引用即使在另一个 component 声明了该逻辑 ID 的资源时也会停止渲染。报告的是所有引用,而不只是第一个——按来源中模板的顺序逐个模板,每个模板先资源后输出,均按键顺序——因此一次构建就能列出全部引用。
a plugin could not resolve something it requires to exactly one value(插件无法将其所需的某项解析为唯一值)
cloudformation-provider: what an omits entry left out is still named by the source’s templates: template "<template>" names resource "<logical-id>" (type "<type>") by <Ref|Fn::GetAtt|DependsOn|Fn::Sub> at <path>; CloudFormation refuses a template naming a resource it does not declare: leave out what names it as well, or remove the entry
若条目的字段由声明为敏感的值构建,其资源的逻辑 ID 和类型显示为 <redacted>,路径中拼出该逻辑 ID 的任何一步也同样如此。
a plugin could not resolve something it requires to exactly one value(插件无法将其所需的某项解析为唯一值)
cloudformation-provider: the Recipe’s or FeatureRecipe’s valuesMapping writes the key "<key>", and no template of the source declares a parameter of that name: template "<template>" declares "<parameter>", …; a sourced template takes values only through the parameters it declares, so rename the key to the parameter it is meant for, or remove it from the valuesMapping
a plugin could not resolve something it requires to exactly one value(插件无法将其所需的某项解析为恰好一个值)
cloudformation-provider: a parameter a sourced template’s binding filled is still referenced from elsewhere in the assembled stack: component "<component>"’s template "<template>" references parameter "<parameter>", which the valuesMapping of a Recipe or FeatureRecipe rendering for component "<component>" binds; …; binding a parameter removes its declaration from the source that declares it, and no template in the stack declares it any more, so the reference names nothing CloudFormation can resolve: reference what the binding component publishes instead, declare the parameter in the template that references it, or remove the key from the valuesMapping(来源模板绑定填充的参数仍在组装 stack 的其他地方被引用……绑定参数会从声明它的来源中移除其声明,stack 中已没有模板声明它,因此该引用指向 CloudFormation 无法解析的内容:改为引用绑定组件发布的内容,在引用它的模板中声明该参数,或从 valuesMapping 中移除该键)
绑定到参数的字面量按照 CloudFormation 在 stack 部署时转换为该参数 Type 传入的同一值的方式进行转换。如果不存在这样的转换,渲染停止:绑定到 Number 或 List<Number> 的非数字值,绑定到只取单个值的参数的列表或映射,以及绑定到 AWS::SSM::Parameter::Value<…> 参数的任何字面量(CloudFormation 从 Parameter Store 而非模板读取其值)。绑定到被模板作为 Fn::Sub 变量引用的参数的列表同样会停止渲染,因为变量替换的是一个字符串。
输出的消息。先给出条件,然后是参数、其模板和类型,以及该值为何不匹配;不引用任何值:
a plugin has no representation for a value it was given(插件无法表示所给的值)
cloudformation-provider: parameter "<parameter>" of template "<template>" is of type <type>, and <why the value does not fit>(模板的参数属于该类型,且值不匹配的原因)
**修复方法:**绑定符合参数类型的值——对于 Parameter Store 类型,则绑定 {{resolve:ssm:…}} 动态引用或内部函数——或不绑定该参数,改由 stack 部署时传入值。
a plugin has no representation for a value it was given(插件无法表示所给的值)
cloudformation-provider: the value bound to parameter "<parameter>" of template "<template>" does not satisfy its <constraint>, which CloudFormation would refuse when the stack deploys; bind a value the parameter admits(绑定到模板参数的值不满足其约束,CloudFormation 会在 stack 部署时拒绝;请绑定参数允许的值)
a plugin has no representation for a value it was given(插件无法表示所给的值)
cloudformation-provider: parameter "<parameter>" of template "<template>" is declared NoEcho, and the value bound to it would be written into the template as it stands; bind a dynamic reference ({{resolve:secretsmanager:…}} or {{resolve:ssm-secure:…}}) or an intrinsic function instead, or leave the parameter unbound for a deploy-time value(模板的参数声明为 NoEcho,绑定到它的值会原样写入模板;请改为绑定动态引用或内部函数,或不绑定该参数以使用部署时的值)
cloudformation-provider: the Recipe’s or FeatureRecipe’s valuesMapping reads a value declared sensitive, so a literal it produces is refused, and binding parameter(s) "<parameter>", … would write a literal into the template as it stands; …(Recipe 或 FeatureRecipe 的 valuesMapping 读取了声明为敏感的值,因此其产生的字面量被拒绝,绑定这些参数会将字面量原样写入模板;……)
a plugin has no representation for a value it was given (插件无法表示给定的某个值)
cloudformation-provider: the value bound to parameter "<parameter>" is a dynamic reference, and template "<template>" references the parameter in <where>, where CloudFormation does not resolve a dynamic reference or shows it to whoever reads the stack; bind an intrinsic function instead, or leave the parameter unbound for a deploy-time value (cloudformation-provider:绑定到该参数的值是一个动态引用,而该模板在 CloudFormation 不解析动态引用或会将其展示给任何读取栈的人的位置引用了该参数;请改为绑定一个内部函数,或不绑定该参数以使用部署时传入的值)
A rule reads a bound CloudFormation parameter by name(规则按名称读取已绑定的 CloudFormation 参数)
模板 Rules 中的 Fn::ValueOf 通过逻辑 ID 而非 Ref 指定参数,并读取堆栈部署时为其传入的值。绑定该参数会从该来源的每个模板中移除其声明,这会使规则(无论位于哪个模板中)指向不存在的内容,因此渲染会停止。
输出的消息。先是该情况,然后是规则、其模板和参数:
a plugin has no expression for a construct this build declares (插件无法表达本次构建声明的某个构造)
cloudformation-provider: rule "<rule>" of template "<template>" reads parameter "<parameter>" through Fn::ValueOf, which names a declared parameter by its logical ID, and binding the parameter removes its declaration from the source; leave the parameter unbound so the rule can read it at deploy (cloudformation-provider:该模板的规则通过 Fn::ValueOf 读取该参数,Fn::ValueOf 按逻辑 ID 指名一个已声明的参数,而绑定该参数会从来源中移除其声明;请不绑定该参数,以便规则在部署时读取它)
a plugin has no expression for a construct this build declares (插件无法表达本次构建声明的某个构造)
cloudformation-provider: the assembled stack of component "<component>", … cannot carry the transform "<transform>", declared by component "<component>": <why> (cloudformation-provider:由这些组件组装的栈无法承载该组件声明的 transform,原因如上)
a plugin could not resolve something it requires to exactly one value (插件无法将其所需的某项解析为唯一的值)
cloudformation-provider: the transforms "<first>" and "<second>" are ordered both ways — "<first>" before "<second>" by <who>, and "<second>" before "<first>" by <who> — and the assembled stack’s Transform runs them in one order; declare them in one order (cloudformation-provider:这两个 transform 被以相反的两种顺序排列,而组装后栈的 Transform 只按一种顺序运行它们;请按同一种顺序声明它们)
two things a plugin produced occupy one name in its output (插件产出的两项内容在其输出中占用了同一个名称)
cloudformation-provider: two entries an author wrote reach one stack Output name: <the entries that met> reach the Output name "<name>"; an Output name is built by encoding the component and the entry into the letters and digits a logical id admits, rather than by dropping what it does not, so two entries an author wrote apart stay apart — renaming either end clears the build (cloudformation-provider:作者编写的两个条目得到了同一个栈 Output 名称;Output 名称通过将组件和条目编码为逻辑 ID 允许的字母和数字构建,而不是丢弃不允许的字符,因此作者分开编写的两个条目会保持区分——重命名任意一方即可让构建通过)
two things a plugin produced occupy one name in its output (插件产出的两项内容在其输出中占用了同一个名称)
cloudformation-provider: one mapping key is written more than once: the key "<key>" is written at line <first> and again at line <second>; a mapping holds one value per key, so one of the two bodies would be dropped — remove one, or rename one so each key is written once (cloudformation-provider:一个映射键被写入了不止一次;映射中每个键只保存一个值,因此两个主体中的一个会被丢弃——请删除其中一个,或重命名其中一个,使每个键只写入一次)
a plugin could not resolve something it requires to exactly one value
cloudformation-provider: cross-boundary link resolve received no consumer stack template
a plugin has no representation for a value it was given
cloudformation-provider: cross-boundary link value is interpolated into a larger string; only a whole-scalar injection can carry a cross-stack reference: output key "<key>" on socket "<socket>"
two things a plugin produced occupy one name in its output
helm: node "<node>": rendered resources "<one template>" and "<the other>" both derive output "<file>" with differing content: two rendered resources derive the same output filename with differing content
a plugin could not resolve something it requires to exactly one value
synthesized StatefulSet requires a headless governing Service (declare a service with type: Headless); none found: synthesized StatefulSet has no headless governing Service
a plugin could not resolve something it requires to exactly one value
synthesized StatefulSet declares more than one headless Service; the governing Service is ambiguous (declare exactly one type: Headless service): synthesized StatefulSet has more than one headless Service
wasm: guest plugin named a condition the socket does not declare: the guest named "<offered>", and <why it resolves to no condition>; a plugin names a condition this compiler declares, and reaches for one of <the generic conditions and their codes> when it has none better: <the plugin's own sentence>(wasm:guest 插件指定了 socket 未声明的条件:guest 指定的标识符及其无法解析为任何条件的原因;插件应指定本编译器声明的条件,没有更合适的条件时使用所列通用条件之一;随后是插件自己的说明)
a value a cache location is built from would place cached files outside the place it names in the cache (version "../../../etc" for entity "demo/app/web"). a version, a name, a kind or a host names one directory of the cache, so it carries no / or \ and is neither . nor ..; a URL path or a module subdirectory may name directories beneath its place but may not climb above it. Correct the value where it was written, or, where a registry served it, ask its publisher to publish a version that carries a well-formed one(用于构建缓存位置的某个值会把缓存文件放到它在缓存中所指位置之外。版本、名称、种类或主机只指定缓存中的一个目录,因此不能包含路径分隔符,也不能是当前目录或上级目录;URL 路径或模块子目录可以指定其位置之下的目录,但不能向上越出该位置。请在写入该值的地方更正它;如果该值由注册表提供,请让其发布者发布一个带有格式正确的值的版本)
a path this operation writes or deletes leads through a link out of the directory it must stay inside (removing <workspace>/dist/boundaries, which must stay inside <workspace>, the link <workspace>/dist leads to <elsewhere>/dist-target). nothing was written to or removed from that path. Remove the link, or make it lead to a place inside <workspace>, and run the operation again(此操作写入或删除的路径经由一个链接通向它必须留在其中的目录之外(括号中依次给出正在删除的路径、它必须留在其中的目录、该链接及其指向的位置)。该路径未被写入或删除任何内容。请移除该链接,或使其指向工作区内的某个位置,然后重新运行该操作)
a name this operation writes holds a path segment Windows cannot hold as written (the name "aux/x.yaml", its segment "aux", beneath <directory>). It was not written. Windows reserves device names such as CON, PRN, AUX, NUL, COM1 and LPT1, in any letter case and whatever extension follows, and does not hold a segment ending in a full stop or a space as written; rename that segment where the name is produced(此操作写入的名称包含一个 Windows 无法按原样保存的路径段(即上述名称、其中的路径段以及其所在的目录)。该名称未被写入。Windows 保留 CON、PRN、AUX、NUL、COM1 和 LPT1 等设备名,不区分字母大小写,也不论其后跟随何种扩展名;并且不会按原样保存以句点或空格结尾的路径段。请在生成该名称之处重命名该路径段)
annotation binding declares one path in both pillar lists(注解绑定在两个支柱列表中声明了同一路径)
它会在构建遇到上文“An annotation routes through a pillar its authoring side may not use(注解经由其编写方不得使用的支柱进行路由)”中描述的中止之前向你发出警告——提示是早期的呈现面,而那个中止则是执行面。该 lint 在 warnings.md 的“Binding-map-overlap lint”下讲解。
附件名称与某个已声明的槽只差一次编辑
提示。某个组件以一个名称附加了 Feature,该名称不是其类型声明的槽之一,但与其中某个槽只差一次编辑——这正是槽名拼写错误的样子。以未被任何槽声明的名称进行附加是合法的,因此不会中止;该提示指出的是其后果:该附件是一个自由附件,而不是填充你本意要填的槽,该槽仍保持为空。在连接上,同样的拼写错误不合法,会改为中止并指出相近的槽;参见“A connection carries an attachment under a name its socket declares no slot for(连接以其插座未声明槽的名称携带附件)”。如果该附件的 Feature 满足相近槽的 selector:,则不会发出该提示:这种配对由“An attachment written under another name fits a slot its component leaves empty(以另一名称编写的附件适合其组件留空的槽)”下的中止来判断,它会在该槽留空时报告。
其消息开头为:
attachment name is a near miss for a declared slot(附件名称与某个已声明的槽相近)
它只给出建议而不中止构建,是因为构建无法确定。绑定为整个工作区编写一次,而一次构建只针对一个 Release,因此提供该能力的插件可能只有另一个 Release 会读取。指定了插件的条目则按不同方式判断,并在确定有误时中止——见上文“A plugins.providers binding names a plugin that does not serve the capability(plugins.providers 绑定指定的插件不提供该能力)”。
其消息开头为:
plugins.providers entry names a capability no provider-rendering plugin the build reads serves(plugins.providers 条目指定了构建所读取的任何 provider 渲染插件都不提供的能力)
<file> at <authored key>: annotation contribution overridden by an explicit value ("<annotation-key>", component "<component>", attachment "<attachment>", pillar "<pillar>", key "<the key at issue>", annotation declared at "<where the annotation was written>")
cross-boundary link between endpoints rendered by different providers is not supported(不支持由不同 provider 渲染的端点之间的跨边界链接) ("<target-component>", socket "<socket>", consumer provider "<provider>", target provider "<provider>")
workspaceconfig: registry alias "<alias>" is already used by host "<host>"; choose a different alias or address that host directly: registry alias is already used by another host(workspaceconfig:该 registry 别名已被该主机使用;请选择其他别名,或直接使用该主机地址:registry 别名已被另一主机使用)
registrytrust: advertised trust config is malformed: <what the decoder reported>(registrytrust:所发布的信任配置格式错误:解码器报告的内容)
身份条目没有可匹配的内容:
registrytrust: advertised trust config is malformed: <list>[<index>]: an identity entry must set identity or identity_regexp(registrytrust:所发布的信任配置格式错误:列表中对应索引的条目:身份条目必须设置 identity 或 identity_regexp)
以及没有签发者的条目:
registrytrust: advertised trust config is malformed: <list>[<index>]: an identity entry must set issuer(registrytrust:所发布的信任配置格式错误:列表中对应索引的条目:身份条目必须设置 issuer)
Notice: <host> publishes no trust policy (HTTP 404); pin its trust by hand with —identity or —key(提示:该主机未发布信任策略(HTTP 404);请使用 —identity 或 —key 手动固定其信任)
它所记录的情况是 registrytrust: registry advertises no trust config。
a registry other than the official hub is not registered offline without a trust policy supplied by hand, because the policy it advertises cannot be fetched; register it once while online, or pin its trust by hand with aggrega registry add <host> --identity <identity>=<issuer> or --key <public-key-file>(离线时,除官方 hub 外的注册表若没有手动提供的信任策略则不会被注册,因为无法获取其公布的策略;请在联网时注册一次,或使用上述 identity 或 key 参数手动固定其信任)
aggrega push: <reference>:<version> is already published as <existing digest>; refusing to overwrite with <proposed digest> — publish a new version (aggrega lint —pre-publish verifies the bump): oci: tag already published with different content(该引用的此版本已以现有摘要发布;拒绝用提议的摘要覆盖——请发布新版本(aggrega lint —pre-publish 会验证版本提升):oci:该标签已以不同内容发布)
发布数据制品时:
aggrega push-artifact: <reference>:<version> is already published as <existing digest>; refusing to overwrite with <proposed digest> — publish a new version: oci: tag already published with different content(该引用的此版本已以现有摘要发布;拒绝用提议的摘要覆盖——请发布新版本:oci:该标签已以不同内容发布)
the entity shares its directory with another entity, and an entity of its kind has a directory of its own (Recipe "<name>", beside it: Recipe "<name>" in <file>). remediation: give each entity a directory of its own — move <file> into a directory of its own, together with any file only that entity reads; only the Aggregate, Manifest and Release kinds may share a directory with other entities(该实体与另一个实体共用目录,而该类型的实体应拥有自己的目录。修复方法:为每个实体提供独立目录——将所列文件连同仅该实体读取的文件一起移入独立目录;只有 Aggregate、Manifest 和 Release 类型可以与其他实体共用目录)
A published archive carries an entry Windows cannot use(发布的归档包含 Windows 无法使用的条目)
这是发布实体时发出的提示;它从不阻止任何操作,构建也不会发出它。在文档之外还携带文件的实体会以归档形式发布,归档中的每个名称(先是实体文档自身的文件名,然后是它携带的每个文件)都按照上文停止项“A name the operation writes holds a part Windows cannot hold(操作写入的名称包含 Windows 无法容纳的部分)”在 Windows 上所采用的规则进行判断:Windows 为设备保留的部分(不区分大小写,无论后跟什么扩展名),或以句点或空格结尾的部分。因此 aux/x.yaml 会因其目录 aux 触发该提示,report. 会因结尾的句点触发,名为 con.yaml 且导入了 schema 文件的文档会因其自身名称触发。不携带任何文件的实体仅以其文档发布,放在产品选定的名称下,而 Plugin 不发布归档,因此两者都不会触发。
**它在所有平台上都会发出,且不拒绝任何操作。**Windows 上的工作区会在该停止项下拒绝布置此类条目,因此无法使用该版本;这条提示让发布者在 Windows 用户发现之前就得知此事。发布或其试运行会照常继续或停止,与没有该提示时完全相同。
signing: keyless signing requires a live identity provider, Fulcio, and Rekor: an identity token source is required(signing:无密钥签名需要可用的身份提供方、Fulcio 和 Rekor:需要一个身份令牌来源)
以及来源未产生任何内容:
signing: keyless signing requires a live identity provider, Fulcio, and Rekor: an identity token is required(signing:无密钥签名需要可用的身份提供方、Fulcio 和 Rekor:需要一个身份令牌)
aggrega push: registry "<host>" requires signatures; re-run signing the artifact (there is no flag to push unsigned content here): signing: registry requires signatures; refusing to push unsigned content(aggrega push:该 registry 要求签名;请对制品签名后重新运行(此处没有用于推送未签名内容的标志):signing:registry 要求签名;拒绝推送未签名内容)
工作区策略的要求,它会指明使该制品纳入范围的类型:
aggrega push: the signing policy requires a signature for kind "<kind>"; re-run signing the artifact (there is no flag to push unsigned content here): signing: signing policy requires a signature for this artifact kind; refusing to push unsigned content(aggrega push:签名策略要求该 kind 必须签名;请对制品签名后重新运行(此处没有用于推送未签名内容的标志):signing:签名策略要求此制品类型必须签名;拒绝推送未签名内容)
aggrega push: sign <reference>:<version>: the identity token carries no verified email or subject claim — the OIDC flow/client did not return an email-scoped identity (re-exporting or re-acquiring the token will not help); configure the identity provider/client/scope to return one: <the underlying failure>: signing: registry requires signatures; refusing to push unsigned content(aggrega push:对该引用及版本签名:身份令牌不含经过验证的 email 或 subject 声明——OIDC 流程/客户端没有返回带 email 作用域的身份(重新导出或重新获取令牌无济于事);请配置身份提供方/客户端/作用域以返回此类身份:底层失败:signing:registry 要求签名;拒绝推送未签名内容)
aggrega sign: signing: the references named together need different signing credentials, so nothing was signed (<registry> signs with the held key signing.key_path names, <registry> signs keyless: no signing.key_path applies). remediation: sign them in separate runs, one per credential: the references on <registry>, then the references on <registry>; each run signs as it would on its own(aggrega sign:签名:一起指定的引用需要不同的签名凭据,因此未签名任何内容(一个 registry 使用 signing.key_path 指定的持有密钥签名,另一个 registry 无密钥签名:没有适用的 signing.key_path)。修复方法:按凭据分开运行签名,每个凭据一次:先签名一个 registry 上的引用,再签名另一个 registry 上的引用;每次运行的签名方式与单独运行时相同)
以及当批次中某个注册表要求签名时,在补救办法末尾指出它:
aggrega sign: signing: the references named together need different signing credentials, so nothing was signed (<registry> signs with the held key signing.key_path names, <registry> signs keyless: no signing.key_path applies). remediation: sign them in separate runs, one per credential: the references on <registry>, then the references on <registry>; each run signs as it would on its own, and <registry> requires signatures, so this refusal holds back signing that would otherwise have gone ahead rather than signing that cannot be done(aggrega sign:签名:一起指定的引用需要不同的签名凭据,因此未签名任何内容(一个 registry 使用 signing.key_path 指定的持有密钥签名,另一个 registry 无密钥签名:没有适用的 signing.key_path)。修复方法:按凭据分开运行签名,每个凭据一次:先签名一个 registry 上的引用,再签名另一个 registry 上的引用;每次运行的签名方式与单独运行时相同,且所指 registry 要求签名,因此此次拒绝阻止的是本可进行的签名,而非无法完成的签名)
第二个拥有自己密钥的注册表会被描述为“with a different held key”(使用另一个持有的密钥)签名。密钥的路径从不打印:消息给出的是设置项,也就是你可以更改的内容。
docscache: <reference>@<version> has media type "<what was found>", want "<what a documentation bundle is>": docscache: artifact is not a documentation bundle(docscache:该引用的该版本的媒体类型为所发现的类型,而期望的是文档包的媒体类型:docscache:制品不是文档包)
the edit was refused because the resulting document would not be valid, and nothing was written: document envelope validation failed (<kind>, at <path>); <line>:<column>: <field-path>: … <the schema's own objection>. correct the document to match its kind’s schema(编辑被拒绝,因为生成的文档将无效,且未写入任何内容:文档封装校验失败,后附出错位置、字段路径及 schema 自身的异议。请更正文档,使其符合其类型的 schema)
the entity writes an Aggrega schema extension directly into schema content instead of declaring it under usesSchema or featuresSchema(该实体将 Aggrega schema 扩展直接写入 schema 内容,而不是在上述两个字段之一下声明它)
🔴 **有两个条件描述此情况,它们并不相同。**构建报告的建议记录在上文“A Recipe publishes a provides key its Component does not declare”下;这一条在对照发布约定检查实体时发出,并带有自己的代码。该发现是在两个接口上遇到的同一事实——读取诊断中的代码即可分辨你遇到的是哪一个。
其消息开头为:
the Recipe publishes a provides key the Component it implements does not declare, so a consumer wiring that key is refused(该 Recipe 发布了其所实现的 Component 未声明的 provides 键,因此接线该键的消费者会被拒绝)
a Component’s annotation stating how its metrics authenticate disagrees with whether it declares the provides key saying an instance’s metrics need a credential(Component 说明其指标如何认证的注解,与它是否声明表示实例指标需要凭据的 provides 键不一致)
a connection and the target it reaches do not name one key: they write different locators for it, or only one of them names one(连接与其到达的目标未指向同一个密钥:二者为它写了不同的定位符,或者只有其中一方指定了密钥)
the importer reported a diagnostic that stops the import, so the source was not fully turned into draft authoring files(导入器报告了一个中止导入的诊断,因此源未被完全转换为草稿编写文件)
这与同一格式由不止一个导入器声明的情况不同,后者见上文“A parse or import format is advertised by more than one plugin(一种解析或导入格式由不止一个插件声明)”。在那里格式已确定,服务于它的各导入器相互竞争,因此由 plugins.importer 条目在其中选择;而这里格式本身就不同,因此任何挂接都无法解决,指定格式才能解决。导入器识别某个源时,会将其识别为它声明的每一种格式,因此一个声明了不止一种格式、且其中一个签名匹配的导入器,在这里同样会被拒绝。
其消息开头为:
more than one importer recognises the source
消息的其余部分按导入器的标识与版本顺序列出该源及其被识别成的每种格式,然后给出补救措施:
more than one importer recognises the source (source "<source>", recognised as "<format>", "<format>"). Pass —format to name the one to read it as (for example —format <format> or —format <format>)
no importer recognises the source (directory "<directory>"). Import one of the directory’s files on its own, or pass —format naming a format whose importer reads a directory through the file patterns it declares (for example —format <format> or —format <format>)(没有导入器能识别该源(目录)。请单独导入该目录中的一个文件,或传入 —format 指定一个格式,其导入器通过自己声明的文件模式读取目录(例如 —format 或 —format))
the importer serving the source’s format declares no file patterns, so it reads one file and cannot read a directory
消息的其余部分列出格式、导入器以及你所指定的目录,然后给出补救措施:
the importer serving the source’s format declares no file patterns, so it reads one file and cannot read a directory (format "<format>", importer "importer/<name>", directory "<directory>"). Import one of the directory’s files on its own instead; the importer reads a directory once it declares the file patterns its files are named by
no file in the directory matches the file patterns the importer serving the source’s format declares
消息的其余部分列出格式、导入器、你所指定的目录以及导入器声明的每个模式,然后给出补救措施:
no file in the directory matches the file patterns the importer serving the source’s format declares (format "<format>", importer "importer/<name>", directory "<directory>", file patterns "<pattern>", "<pattern>"). Name a directory holding a file one of those patterns matches, or the format of an importer whose patterns match the files this directory holds
a file read from the directory and a file named in the importer’s with.sources have the same name
消息的其余部分会给出该名称和 with.sources 中的文件,然后给出补救方法:
a file read from the directory and a file named in the importer’s with.sources have the same name (name "<name>", the with.sources file "<path>"). Each source reaches the importer under one name, so rename one of the two files, or leave the file out of the importer’s with.sources
no Recipe in the workspace’s catalog binds to the capability the import’s target names (target "<target>", the catalog’s Recipes bind to "<capability>", "<capability>"). Name one of those capabilities as the target, or leave the target out and no Manifest is drafted; nothing was drafted or written
A command-line plugin runner was built without a way to find plugins(命令行插件运行器在构建时缺少查找插件的途径)
E0003
malformed attachment requirement
Malformed attachment requirement(格式错误的附加要求)
E0004
annotation contribution overridden by an explicit value
An explicit value displaced one an annotation supplied(显式值取代了注解提供的值)
E0005
policy violation
A governance plugin rejected the build(治理插件拒绝了构建)
E0006
required attachment slot unfilled
Required attachment slot not bound(必需的附加槽未绑定)
E0007
selector violation
Cross-node type safety violation via selector:(通过选择器产生的跨节点类型安全违规)
E0008
attachment slot selector unsatisfied
The Feature filling an attachment slot does not satisfy the slot’s selector(填充挂载槽的 Feature 不满足该槽的选择器)
E0009
pipeline step typed-I/O contract violation
A pipeline step’s typed input or output does not satisfy its declared contract(流水线步骤的类型化输入或输出不满足其声明的契约)
E0010
pipeline step failed
A pipeline step failed(流水线步骤失败)
E0011
pipeline patch targets a document not present in the set
A pipeline patch addresses a document the set does not hold, or one with no tree to address(流水线补丁指向集合中不存在的文档,或指向没有可寻址树结构的文档)
E0012
pipeline patch targets an opaque (non-structured) unit
A pipeline patch addresses a document the set does not hold, or one with no tree to address(流水线补丁指向集合中不存在的文档,或指向没有可寻址树结构的文档)
E0013
feature type mismatch between Aggregate and Release
Feature type mismatch between Aggregate and Release(Aggregate 与 Release 之间 Feature 类型不匹配)
E0014
inject entry carries both `value:` and `from:`; schema requires exactly one
An inject: entry carries both a literal and a source key(一个 inject: 条目同时带有字面值和来源键)
E0015
uses-edge inject dictates a delivery mechanism the socket does not permit
uses edge dictates delivery on a socket that allowlists none(uses 边在未设置允许列表的套接字上指定了投递方式); uses edge dictates a delivery mechanism outside the socket’s allowlist(uses 边指定了套接字允许列表之外的投递机制)
E0016
jsonpatch: test operation failed
A patch’s test operation did not match the document(补丁的 test 操作与文档不匹配)
E0017
annotation-transform plugin output was rejected: an injection targets a component coordinate the host did not supply, or carries a value that is not a string or an object of subkeys
An annotation-transform plugin names a component it was not given, or injects a value no annotation takes(注解转换插件指定了未提供给它的组件,或注入了任何注解都不接受的值)
E0018
policy attachment settings do not satisfy the plugin's declared settings schema
A governance attachment’s settings do not match the plugin’s declared schema(治理挂接的设置与插件声明的 schema 不匹配)
E0019
endpoint requires form: reference
A workload: form and the fields beside it do not agree(workload: 的 form 与其旁边的字段不一致)
E0020
schedule is not a valid cron expression
A workload schedule: is not an expression the check accepts(workload 的 schedule: 不是检查所接受的表达式)
E0021
persistentTemplate volume requires form: stateful
A workload: form and the fields beside it do not agree(workload: 的 form 与其旁边的字段不一致)
E0022
pipeline PATCH target is not parseable structured YAML/JSON
A pipeline step addresses documents the node does not have(流水线步骤寻址了节点没有的文档)
E0023
form: reference requires an endpoint
A workload: form and the fields beside it do not agree(workload: 的 form 与其旁边的字段不一致)
E0024
schedule requires form: scheduled
A workload: form and the fields beside it do not agree(workload: 的 form 与其旁边的字段不一致)
E0025
form: scheduled requires a schedule
A workload: form and the fields beside it do not agree(workload: 的 form 与其旁边的字段不一致)
E0026
imported artifact content does not match the digest recorded for it in entity.lock
An imported artifact no longer matches the digest recorded beside its Recipe(导入的制品与其 Recipe 旁记录的摘要不再一致)
E0027
artifacts $import: is not a bare-name artifact-library reference (<Library>#/artifacts/<entry>)
库 $import: 未以裸名称形式书写
E0028
artifacts output filename collision: two artifact outputs carry the same filename
Two artifact outputs of one Recipe carry the same filename(同一 Recipe 的两个 artifact 输出使用了相同的文件名)
E0029
artifact template references a pillar the Recipe does not declare
An artifacts: template reads a pillar the Recipe does not declare(artifacts 模板读取了 Recipe 未声明的支柱)
E0030
artifact-library import references a bundle not present in the ArtifactLibrary
A library $import: names a library or an entry the catalog does not hold(库导入指向的库或条目不在目录中)
E0031
artifact-library import references an ArtifactLibrary not present in the catalog
A library $import: names a library or an entry the catalog does not hold(库导入指向的库或条目不在目录中)
E0032
assembled output collision: two contributors write the same output path
Two contributors write the same output path(两个贡献者写入同一输出路径)
E0033
assertion failed
An assertion stopped the build(断言使构建停止)
E0034
duplicate delivery key across attachment-inject and another inject source
An attachment delivers a key another inject source already claimed(挂载交付的键已被另一个注入来源占用)
E0035
provider expected to assemble its dispatch group provides no boundary assembler
The plugin serving a provider cannot assemble what that provider combines(服务某个 provider 的插件无法组装该 provider 所合并的内容)
E0036
merged-path assembly has conflicting assembly-name annotation values
Chart-name mismatch on a merged helm-chart umbrella(合并的 helm-chart umbrella 上 chart 名称不一致)
E0037
cross-boundary link between endpoints rendered by different providers is not supported
A connection crosses between two different providers’ assembled outputs(连接跨越两个不同 provider 的组装输出)
E0038
derived name collision: one name is derived more than once in one key space
The same name is derived more than once inside the output(输出中同一名称被派生了不止一次)
E0039
FeatureRecipe template references a per-component-only field with executionScope: boundary
FeatureRecipe template references a field outside its scope’s allowlist(FeatureRecipe 模板引用了其作用域允许列表之外的字段)
E0040
library $import: carries a registry host; reference the library by bare-name identity
A library $import: addresses its library by registry location(库导入按注册表位置寻址其库)
E0041
multiple contributors share an instance ID at the same dispatch path
Instance-ID collision across boundaries assembling to the same path(组装到同一路径的多个 boundary 之间发生实例 ID 冲突)
E0042
locals entry references a sibling defined later in the same block
locals: entry references a sibling defined later in the same block (locals 条目引用了同一块中稍后定义的同级条目)
E0043
template references a key the locals block does not declare
locals: key does not exist(键不存在)
E0044
mapping-library import references an entry not present in the MappingLibrary
A library $import: names a library or an entry the catalog does not hold(库导入指向的库或条目不在目录中)
E0045
valuesMapping $import: is not a bare-name mapping-library reference (<Library>#/mappings/<entry>)
库 $import: 未以裸名称形式书写
E0046
mapping-library import references a MappingLibrary not present in the catalog
A library $import: names a library or an entry the catalog does not hold(库导入指向的库或条目不在目录中)
E0047
assembled output retains an unresolved cross-boundary link placeholder
Assembled output still carries a cross-boundary placeholder(组装后的输出仍带有跨边界占位符)
E0048
dispatch path produced multiple provider outputs
Path collision: two contributors emit at incompatible paths(路径冲突:两个贡献者在不兼容的路径上输出)
E0049
path template references a field not in the documented allowlist
Path-template references a variable outside the allowlist(路径模板引用了允许列表之外的变量)
E0050
pipeline /host operation from a step with no host component
A pipeline step addresses documents the node does not have(流水线步骤寻址了节点没有的文档)
E0051
pipeline PATCH targets an assembler provider's pre-assembly fragments
A pipeline patch addresses output that has not been assembled yet(流水线补丁寻址了尚未组装的输出)
E0052
pipeline PATCH targets a document the node did not emit
A pipeline step addresses documents the node does not have(流水线步骤寻址了节点没有的文档)
E0053
pipeline plugin is not compatible with the rendering provider
A pipeline step’s plugin does not claim the provider rendering what it addresses(流水线步骤的插件未声明支持渲染其寻址内容的 provider)
E0054
provider rejected node input
A provider refused a node’s input(provider 拒绝了节点的输入)
E0055
Recipe or FeatureRecipe does not publish a provides key its abstract entity's schema.provides contract declares
A Recipe or FeatureRecipe does not publish a provides key its contract declares(Recipe 或 FeatureRecipe 未发布其契约所声明的键)
E0056
provides template evaluation failed
A provides: template could not be evaluated(provides 模板无法求值)
E0057
provides block references a root outside the self-contained set
provides: template references a non-self-contained root (provides 模板引用了非自包含的根)
E0058
provider render is not deterministic
A provider rendered the same input twice and produced different output(provider 对同一输入渲染两次产生了不同的输出)
E0059
duplicate delivery key across self-inject and uses-inject
Duplicate delivery key across inject sources(跨 inject 来源的重复交付键)
E0060
template references a root the render context does not define
Template references a root the render context does not define(模板引用了渲染上下文未定义的根); Self-inject value template references cross-node data(自注入值模板引用了跨节点数据)
E0061
unknown provider
Unknown provider(未知的 provider)
E0062
custom inject mechanism has no matching key in injectMapping output; add the mechanism's key to the Recipe injectMapping
A component declares an inject mechanism the attached Feature maps nothing to(组件声明了已挂接 Feature 未映射任何内容的注入机制)
E0063
workload-library import references an entry not present in the WorkloadLibrary
A library $import: names a library or an entry the catalog does not hold(库导入指向的库或条目不在目录中)
E0064
workload $import: is not a bare-name workload-library reference (<Library>#/workloads/<entry>)
库 $import: 未以裸名称形式书写
E0065
workload-library import references a WorkloadLibrary not present in the catalog
A library $import: names a library or an entry the catalog does not hold(库导入指向的库或条目不在目录中)
Resolving a source: coordinate registers a narrower function set(解析 source: 坐标时注册的函数集更窄)
E0113
resolve: sub-aggregate inclusion depth exceeded
The chain of module imports is deeper than the pin walk descends(模块导入链的深度超过了固定遍历所能下探的深度)
E0114
resolve: no entity in the catalog matches this URI
A reference names no entity the catalog holds(引用指向的实体不在目录中)
E0115
compactform: ambiguous dispatch — $mode required
紧凑形式的 schema 声明了一个字面名为 type 的字段
E0116
compactform: constraint not valid for declared type
A compact-form constraint does not apply to the type it was written on(紧凑格式约束不适用于其所在的类型)
E0117
compactform: $jsonschema content invalid
$jsonschema: 逃生舱口所含的内容不是 schema
E0118
compactform: cross-document $ref carries a registry host; reference the library by identity
A $ref: addresses a library by registry location($ref: 通过注册表位置寻址库)
E0119
compactform: $ref unresolvable
A $ref: is not written in a form the compiler can resolve($ref: 的写法不是编译器能够解析的形式)
E0120
compactform: unknown keyword
A compact-form schema uses a keyword the compact form does not know(紧凑格式 schema 使用了紧凑格式不认识的关键字)
E0121
compactform: cross-document $ref target not found
A $ref: is not written in a form the compiler can resolve($ref: 的写法不是编译器能够解析的形式)
E0122
deprecation: build consumes a deprecated entity
The build consumes an artifact its publisher has deprecated(构建使用了其发布者已弃用的制品)
E0123
docscache: artifact is not a documentation bundle
解析出的制品不是文档包
E0124
docscache: page not found in documentation bundle
文档包中缺少某个页面
E0125
egress: network access refused because the workspace is offline; remediation: pass `--offline=false` to allow the network for this one run, or clear the top-level `offline` key in the configuration file (or AGGREGA_OFFLINE) to allow it from now on; where the work is a build that needs content the machine does not have, run `aggrega pull --release <release>` from a connected environment first to populate the cache
The workspace is offline and the step needs the network(工作区处于离线状态,而该步骤需要网络)
E0126
externalinputs: acquisition is disabled for unpinned inputs
A render requests an external input the lockfile does not pin(渲染请求了 lockfile 未固定的外部输入)
E0127
externalinputs: fetched bytes mismatch the pinned digest
Fetched bytes do not match a pinned digest(获取的字节与固定的摘要不匹配)
E0128
externalinputs: URL scheme is not allowed
An external input’s URL uses a scheme that is not allowed(外部输入的 URL 使用了不允许的协议)
E0129
externalinputs: store blob mismatches its pinned record
A stored external input no longer matches its record(存储的外部输入与其记录不再匹配)
E0130
lockfile: out of date; it no longer matches what its Release resolves to
The lockfile no longer matches what the release resolves to(lockfile 不再与 release 解析出的结果一致)
E0131
lockfile: file failed schema validation
The lockfile does not satisfy its schema(lockfile 不符合其 schema)
E0132
oci: manifest has multiple layers of the expected content media type
manifest 没有预期类型的层,或有多个
E0133
oci: cached manifest digest mismatch
获取或缓存的字节与为其承诺的摘要不匹配
E0135
oci: content digest mismatch
获取或缓存的字节与为其承诺的摘要不匹配
E0136
oci: network unreachable
The registry could not be reached(无法访问 registry)
E0137
oci: artifact not found at remote source
An artifact is not at the source the build was told to find it(制品不在构建被告知的来源处)
E0138
oci: authentication required or failed
The registry will not serve an artifact without credentials it accepts(没有其接受的凭据,registry 不会提供制品)
E0139
oci: tag already published with different content
tag 已以不同内容发布
E0140
oci: manifest has no layer of the expected content media type
manifest 没有预期类型的层,或有多个
E0141
oci: distinct catalog identities map to the same OCI repository location
Two catalog identities publish to one repository location(两个目录标识发布到同一个仓库位置)
E0142
oci: referrer discovery could not be completed
The registry could not answer what is attached to an artifact(registry 无法回答制品附带了什么)
E0143
oci: unknown entity kind for mediatype dispatch
An entity kind has no artifact media type(实体类型没有制品媒体类型)
E0144
cached signature bundle does not match its recorded digest
A cached signature bundle does not match the digest recorded for it(缓存的签名包与为其记录的摘要不匹配)
E0145
plugin reference is not a Plugin entity
A plugin reference is not a Plugin entity(插件引用不是 Plugin 实体)
E0146
circular reference expansion
A library reference expands into itself(库引用展开为自身)
E0147
registrytrust: advertised trust config is malformed
A registry serves a trust document that cannot be read as one(注册表提供的信任文档无法作为信任文档读取)
E0148
registrytrust: registry advertises no trust config
A registry publishes no trust document(注册表未发布信任文档)
E0149
attachment name is a near miss for a declared slot
附件名称与某个已声明的槽只差一次编辑
E0150
attachment does not conform to its declared slot shape
Attachment does not conform to its declared slot shape(附加项不符合其声明的槽位结构)
E0151
component declared in more than one boundary: declare each component in exactly one boundary
A component is placed in more than one boundary(一个组件被放置在多个边界中)
E0152
duplicate Aggregate/Manifest identity (metadata.name) in the Release directory
The Release directory declares one Aggregate or Manifest twice(Release 目录中重复声明了同一个 Aggregate 或 Manifest)
E0153
feature merge conflict: reconcile the Aggregate and Release declarations for the feature
A feature attached by both the Aggregate and the Release cannot be merged(同时由 Aggregate 和 Release 附加的功能无法合并)
E0154
the compiler's own views of the catalog disagree
A guard needs a catalog entity the build resolved and cannot see(守卫需要一个构建已解析但无法看到的目录实体)
E0155
duplicate delivery key across inject sources
Duplicate delivery key across inject sources(跨 inject 来源的重复交付键)
E0156
invalid inject key: the from-key must name a provides key its source publishes
注入的 from 键不在目标的 provides 中
E0158
invalid parameter reference: check the {{ .parameters.* }} expression names a declared parameter and parses as a Go template
A {{ .parameters.* }} reference cannot be interpolated(无法插值 .parameters.* 引用)
E0160
manifest annotation bindings collide on same Feature path+pillar
Two Manifest annotation bindings compete for one routing slot(两个 Manifest 注解绑定争用同一个路由槽位)
E0161
manifest annotation binding uses reserved prefix
A Manifest annotation binding claims the reserved aggrega.ai/ prefix(Manifest 注解绑定占用了保留的 aggrega.ai/ 前缀)
E0162
missing required feature: attach a Feature of the required type to the component
Required feature not attached(未附加必需的 feature)
E0163
required uses socket not populated
Required uses: socket not populated(必需的 socket 未填充)
E0164
parameter contract violated
Parameter type mismatch / contract violation (参数类型不匹配 / 违反契约)
E0165
required parameter not supplied
Parameter type mismatch / contract violation (参数类型不匹配 / 违反契约)
E0167
Recipe publishes a provides key its Component does not declare
Recipe 发布了其 Component 未声明的 provides 键
E0168
authored pillar does not conform to its declared schema
Authored values or infra do not conform to the declared schema(编写的 values 或 infra 不符合声明的 schema)
E0169
self-inject on component without spec.inject allowlist
Self-inject on a component without an allowlist(在没有允许列表的组件上进行自注入); Self-inject mechanism not in the component’s allowlist(自注入机制不在组件的允许列表中)
E0170
aggregate/manifest reference unresolvable
A Release’s aggregate: or manifest: reference resolves to nothing(Release 的 aggregate: 或 manifest: 引用解析不到任何实体)
E0171
unknown uses socket: name a socket the entity declares in its usesSchema — only a component's own uses block may name one the catalog did not declare
uses: socket not declared in the owning entity’s usesSchema(socket 未在所属实体的 usesSchema 中声明)
An x-aggrega-when: or x-aggrega-validate: predicate cannot be evaluated(x-aggrega-when: 或 x-aggrega-validate: 谓词无法求值)
E0218
validator/jsonschema: schema resolution failed
A declared schema cannot be resolved(声明的 schema 无法解析)
E0220
extends chain exceeds maximum depth
extends: 链超出深度上限
E0221
merger: invalid merge input
schema 合并步骤自身的输入保护
E0222
registry alias matches more than one host
A registry alias matches more than one host(注册表别名匹配多个主机)
E0223
a cross-cutting socket is bound by capability but attaches by uri
A plugin binding sets a key the socket it attaches to does not read(插件绑定设置了其所挂接的插槽不读取的键)
E0224
workspace configuration is invalid
The workspace configuration is invalid(工作区配置无效)
E0225
capability is bound to more than one provider plugin
A capability is bound to more than one provider plugin(一个能力绑定到了多个 provider 插件)
E0226
registry alias is already used by another host
A registry alias is already bound to another host(注册表别名已绑定到另一个主机)
E0227
a governance attachment declares no role or an unknown role
A governance attachment declares no role, or one that is not a known role(治理挂载未声明角色,或声明了未知角色)
E0228
a provider socket binding sets a field with no referent on that socket
A plugin binding sets a key the socket it attaches to does not read(插件绑定设置了其所挂接的插槽不读取的键)
E0229
position out of range
An editor position falls outside the document(编辑器位置超出文档范围)
E0246
the digest recorded as trusted for this plugin does not match the digest its cached manifest reports
A trusted plugin’s recorded digest disagrees with the cached artifact(受信任插件的记录摘要与缓存的制品不一致)
E0247
a plugin recorded as trusted for an accept-or-reject verdict is no longer attached at any verdict role
A plugin recorded as a trusted gate is no longer attached(记录为受信任门禁的插件已不再挂接)
E0248
wasm: guest plugin returned an output that is not the shape the socket reads
A plugin returned something that is not the shape the socket reads(插件返回的内容不是插槽所读取的结构)
E0250
provider named a directory for each contributor's own sub-directory that is not a single directory name
A provider named a directory for a contributor that is not one directory(provider 为贡献者指定的目录不是单个目录)
E0251
recipe source is an empty string, which names neither sourceless mode nor sourced mode
Recipe source: is an empty string(Recipe 的 source 字段为空字符串)
E0252
artifact-library bundle file name does not name a file of its own beneath the artifacts key its output is nested under
An ArtifactLibrary bundle file names no file of its own under the key it was imported at(ArtifactLibrary bundle 文件在其导入所在的键下未指定属于自己的文件)
E0253
annotation binding does not resolve against its target Feature
Annotation binding does not resolve against its target Feature(注解绑定无法针对其目标 Feature 解析)
E0254
annotation subkey does not conform to the target Feature's schema at the routed pillar
A bound annotation value does not conform to the target Feature’s schema(绑定的注解值不符合目标 Feature 的 schema)
E0255
annotation routes through a pillar its authoring side may not use
An annotation routes through a pillar its authoring side may not use(注解经由其编写侧不得使用的支柱进行路由)
E0256
annotation binding declares one path in both pillar lists
注解绑定在两个支柱列表中声明了同一路径
E0257
declared schema contract could not be compiled into a usable schema, so nothing was validated against it: correct the contract where it is declared, or remove it if the configuration it covers needs no validation
A declared schema contract cannot be read as a schema(声明的 schema 契约无法作为 schema 读取)
E0259
attachment binds a FeatureRecipe with executionScope: boundary and no boundary holding the component declares it
A boundary-scope Feature is attached only to a component(边界作用域的 Feature 仅附加在组件上)
E0260
component placed in no boundary: name it under a boundary's `components`, or place the sub-module that contributes it under `aggregates`
A component the composition holds is placed in no boundary(组合中的某个组件未放入任何边界)
E0261
boundary names a component the composition does not hold: correct the name, or remove the entry
边界点名了组合中不存在的组件
E0262
component identity cannot be the name its emitted resources are stamped with: rename the component
Component identity cannot be stamped on what it emits(组件标识无法标记到其发出的资源上)
E0263
the target will not accept a name derived from this component's authored identity: rename the component
The target will not accept a name derived from an authored identity(目标不接受由编写的标识派生的名称)
E0264
provider guest never accepted a component identity the compiler composed for it
A provider never accepted a name the compiler composed(provider 始终不接受编译器组合的名称)
E0265
provider does not support the node's input kind
workload: requires a provider that can synthesize(workload: 需要能够进行合成的 provider)
E0266
a schema `$import:` could not be applied
A schema $import: cannot be applied(无法应用 schema 导入指令)
E0267
a schema block declares a key that names no data pillar
A schema block names a key that is not a data pillar (schema 块中出现了不是数据支柱的键)
E0268
reassemble names a patched unit token the carve did not produce; a conforming codec carves and reassembles a file under the same tokens
A provider’s reassembly is handed a unit its own carve never produced(provider 的重组收到了其自身切分从未产生的单元)
E0269
provider guest returned two output files under one path; a conforming guest returns each output path at most once
A provider returned two output files under one path(提供者在同一路径下返回了两个输出文件)
E0270
link patch names an output file the dispatch group did not emit; a conforming link patch names a file the group's own render returned
A provider’s link wiring names an output file that was never emitted(provider 的链接连线指向一个从未输出的输出文件)
E0271
emit_file side effect carries no file; a conforming emit_file side effect carries a file with its path and content
A pipeline step’s file emission carries no file(流水线步骤的文件输出未携带文件)
E0272
side effect declares a kind the plugin contract does not define; a conforming side effect declares emit_file or emit_crd
A pipeline step declares an emission kind the contract does not define(流水线步骤声明了契约未定义的输出类型)
E0273
template reads the name the target gives the resources it renders for the node, and this node's provider reports no such name; a conforming template reads a value the node's own provider supplies
A template reads a rendered name the node’s provider does not report(模板读取了节点的 provider 未报告的渲染名称)
E0274
the plugin identity recorded as trusted no longer matches what this resolution reports
A gate recorded as trusted resolves to a different identity(记录为受信任的门禁解析到了不同的身份)
E0275
the edit was refused because the resulting document would not be valid, and nothing was written
编辑会生成其 schema 拒绝的文档
E0276
the version being published changes the published predecessor in a way the documented evolution rubric objects to
正在发布的变更超出了演进准则允许的范围
E0277
an annotation key on the entity uses a prefix the platform reserves
注解键使用了平台保留的前缀
E0278
the entity's name does not follow the documented name shape for its kind
实体名称不符合其类型预期的形式
E0279
a schema in the entity uses a dynamic reference construct that cross-document reference resolution cannot follow
schema 使用了无法提前解析的动态引用
E0280
a schema in the entity declares an identifier of its own, where the platform owns that schema's identity
schema 声明了平台所拥有的标识符
E0281
the entity's category label does not match the category directory the entity is filed under
Component 的类别标签与其所在目录指明了不同的类别
E0282
the entity writes an Aggrega schema extension directly into schema content instead of declaring it under usesSchema or featuresSchema
schema 扩展被直接写入 schema 内容
E0283
the Plugin entity declares no runtime resource cap of its own, so the platform defaults apply
Plugin 未固定任何运行时上限,因此采用平台自身的上限
E0284
an attachment slot admits only secret material and does not declare that it handles it
attachment 槽位只接受机密材料,却未声明它会处理机密
E0285
the Recipe publishes a provides key the Component it implements does not declare, so a consumer wiring that key is refused
Recipe 发布了其 Component 未声明的 provides 键,在发布时检查
E0286
the version bump being published is smaller than the evolution check's classification of the change requires
提供的版本升级幅度小于变更所要求的幅度
E0287
the importer reported a diagnostic that stops the import, so the source was not fully turned into draft authoring files
导入在转换源的过程中途停止
E0288
a plugin has no expression for a construct this build declares
A workload declares a form compose cannot express(workload 声明了 compose 无法表达的形式); A container declares a field compose has no primitive for(容器声明了 compose 没有对应原语的字段); An omits entry names a kind or a namespace a compose file does not have(omits 条目指定了 compose 文件中不存在的类型或命名空间); An omits entry names a namespace a CloudFormation template does not have(omits 条目指定了 CloudFormation 模板中不存在的命名空间); A rule reads a bound CloudFormation parameter by name(规则按名称读取已绑定的 CloudFormation 参数); The assembled CloudFormation stack cannot carry a transform(组装出的 CloudFormation 堆栈无法携带 transform)
E0289
a plugin could not resolve something it requires to exactly one value
A health probe cannot be turned into a compose healthcheck(健康探针无法转换为 compose healthcheck); A configmap volume has no file behind it(configmap 卷背后没有文件); What an omits entry left out is still named by the compose file(omits 条目排除的内容仍被 compose 文件引用); What an omits entry left out is still named by a CloudFormation template(omits 条目排除的内容仍被 CloudFormation 模板引用); A valuesMapping key names no parameter of a sourced CloudFormation template(valuesMapping 键未指向所引入 CloudFormation 模板的任何参数); Another component references a CloudFormation parameter a sourced template’s binding filled(另一个组件引用了由所引入模板的绑定填充的 CloudFormation 参数); Two components order one pair of transforms oppositely(两个组件以相反顺序排列同一对 transform); A cross-boundary reference has no consuming stack to be written into(跨边界引用没有可写入的消费堆栈); A synthesized StatefulSet has no single service to govern it(合成的 StatefulSet 没有唯一的 service 来管理它)
E0290
two things a plugin produced occupy one name in its output
An authored export name is one the build derives for a cross-stack reference(编写的导出名称与构建为跨堆栈引用派生的名称相同); The output a cross-stack reference publishes on already carries an Export(跨堆栈引用所发布到的输出已带有 Export); Two entries reach one stack output name(两个条目指向同一个堆栈输出名称); A CloudFormation fragment writes one key twice(CloudFormation 片段将同一个键写入两次); Two rendered resources land at one output file(两个渲染出的资源落在同一个输出文件中)
E0291
a plugin has no representation for a value it was given
A published port declares a transport compose cannot spell(发布的端口声明了 compose 无法表示的传输协议); A resources quantity cannot be converted to a compose value(resources 数量无法转换为 compose 值); A resource quantity the helm provider emits is not a quantity(helm provider 输出的资源数量不是有效数量); A service type the helm provider cannot render(helm provider 无法渲染的 service 类型); A Kubernetes version the helm provider cannot render a chart for(helm provider 无法为其渲染 chart 的 Kubernetes 版本); A value bound to a CloudFormation parameter cannot take the parameter’s type(绑定到 CloudFormation 参数的值无法采用该参数的类型); A value bound to a CloudFormation parameter is one its constraints refuse(绑定到 CloudFormation 参数的值被其约束拒绝); A secret bound to a CloudFormation parameter would be written into the template(绑定到 CloudFormation 参数的 secret 会被写入模板); A dynamic reference is bound where CloudFormation does not resolve it(动态引用被绑定在 CloudFormation 不解析它的位置); A cross-boundary reference was spliced into a longer string(跨边界引用被拼接进了更长的字符串)
E0292
a plugin reported a failure that none of the declared kinds names
A plugin reported a failure it did not classify(插件报告了一个未分类的失败)
E0293
wasm: guest plugin named a condition the socket does not declare
A plugin named a condition the socket does not declare(插件指明了 socket 未声明的条件)
E0294
components in different subsystems take the same identity: rename one of them, since a subsystem contributes nothing to a component's identity
Two subsystems declare a component under one name(两个子系统以同一名称声明组件)
E0295
library reference: a reference to a library entry carries no whitespace or line break
A reference to a library entry carries whitespace(对库条目的引用包含空白)
E0296
release extends chain composes both named boundaries and top-level components: declare one routing shape across the chain, never both
Release 链中的各环节对路由形态的选择不一致
E0297
inherited boundary directory carries no template variable, so it resolves to the path the extended Release writes to
A child Release inherits a boundary directory that resolves where its parent writes(子 Release 继承的边界目录解析到其父级写入的位置)
E0298
oci: published bundle carries no entity document
A published bundle holds no entity, or holds two(已发布的包中没有实体,或有两个实体)
E0299
oci: published bundle carries more than one entity document
A published bundle holds no entity, or holds two(已发布的包中没有实体,或有两个实体)
E0300
oci: published bundle cannot be unpacked
A published artifact cannot be read as an entity(已发布的制品无法作为实体读取)
E0301
oci: published artifact is not an entity document
A published artifact cannot be read as an entity(已发布的制品无法作为实体读取)
E0302
an input the entity reads has no pin recorded for it in the entity.lock beside it
An entity reads an input the lock beside it records no pin for(实体读取了其旁锁文件未记录固定值的输入)
E0303
the entity shares its directory with another entity, and an entity of its kind has a directory of its own
实体与另一个实体共用目录
E0304
a path names content outside the entity's own directory
A path names content outside the entity’s own directory(路径指向实体自身目录之外的内容)
E0305
the files of the entity's local source do not match the pins recorded for them in entity.lock
A local source no longer matches the pins recorded beside its Recipe(本地源与其 Recipe 旁记录的固定值不再匹配)
E0306
plugin artifact not found on this machine
A plugin’s .wasm is not on this machine(插件的 wasm 模块不在本机上)
E0307
a value a cache location is built from would place cached files outside the place it names in the cache
A value would place a cached file outside the cache(某个值会把缓存文件放到缓存之外)
E0308
a Feature reaches a component alongside a Feature it declares a conflict with
Two Features declared to conflict reach one component(两个声明为冲突的 Features 到达同一个组件)
E0309
a symbolic link sits among the files an entity carries
A symbolic link sits among the files an entity carries(实体携带的文件中存在符号链接)
E0310
a registry other than the official hub is not registered offline without a trust policy supplied by hand, because the policy it advertises cannot be fetched; register it once while online, or pin its trust by hand with `aggrega registry add <host> --identity <identity>=<issuer>` or `--key <public-key-file>`
离线添加 registry 时没有可固定的信任策略
E0311
reference carries a malformed version pin
A version pin is none of the forms a pin takes(版本锁定不属于任何一种锁定形式)
E0312
a provider socket binding names a capability containing a colon, which no Recipe can select
A provider binding names a capability containing a colon(provider 绑定指定的能力包含冒号)
E0313
plugins.providers entry names a capability no provider-rendering plugin the build reads serves
provider 绑定指定了构建所读取的任何插件都不提供的能力
E0314
plugin was built from a working tree with uncommitted changes, so no commit reproduces the version it reports
A plugin was built from a working tree with uncommitted changes(插件是从带有未提交更改的工作树构建的)
E0315
a connection carries an attachment under a name its socket declares no slot for
A connection carries an attachment under a name its socket declares no slot for(连接以其插槽未声明槽位的名称携带附件)
E0316
a Release attachment takes the name of an attachment one of a component's connections carries
A Release attachment takes the name of a connection’s attachment(Release 附加项占用了某个连接的附加项名称)
E0317
a Release connection attachment names no Feature type, and the type is required for an attachment only the Release makes
A Release connection attachment names no Feature type(Release 连接附加项未指定 Feature 类型)
E0318
duplicate delivery key across two attachments: an attachment's FeatureRecipe writes a delivery key another attachment already delivered
Two attached Features deliver one key, the later through its FeatureRecipe’s injectMapping(两个挂载的 Feature 交付同一个键,后者通过其 FeatureRecipe 的 injectMapping)
E0319
connection alias is already used by another connection of the same component
Two connections of one component under one alias(同一组件的两个连接使用同一别名)
E0320
a path this operation writes or deletes leads through a link out of the directory it must stay inside
A path the operation writes leads through a link out of the directory it must stay inside(操作写入的路径经由链接通向其必须保持在内的目录之外)
E0321
a file this operation reads leads through a link out of the directory it must stay inside
A file the operation reads leads through a link out of the directory it must stay inside(操作读取的文件通过链接指向了它必须留在其内的目录之外)
E0323
template reads its callers' render facts, but the FeatureRecipe does not set readsCallerRenderFacts
A template reads its callers’ render facts without declaring it(模板读取了调用方的渲染事实但未声明)
E0324
a reference a document makes to another file leads out of the directory it must stay inside
A reference to another file leads out of the directory it must stay inside(对另一文件的引用指向了它必须留在其中的目录之外)
E0325
provider guest reported a render fact whose value is not a list; a conforming guest reports every render fact's value as a JSON array, even with one entry
A provider reported a render fact whose value is not a list(provider 报告的渲染事实的值不是列表)
E0326
pipeline step reads its callers' render facts, but a pipeline step does not read the components connecting to its host; it reads only the host's own render facts
A pipeline step reads its callers’ render facts(流水线步骤读取其调用方的渲染事实)
E0327
template indexes a map with a key the map does not hold
A template indexes a map with a key the map does not hold(模板使用映射中不存在的键索引该映射)
E0328
attachment written under a name no slot declares fits a slot its component leaves empty
An attachment written under another name fits a slot its component leaves empty(以其他名称编写的挂载适合其 component 留空的槽)
E0329
a connection and the target it reaches do not name one key: they write different locators for it, or only one of them names one
连接与其到达的目标未指向同一个密钥
E0330
signing: the references named together need different signing credentials, so nothing was signed
一起签名的引用需要不同的签名凭据
E0331
signing: no verified signature is recorded for an artifact that requires one
No verified signature is recorded for an artifact that requires one (要求签名的制品未记录已验证的签名)
E0332
signing: the recorded signature was made for a different artifact
A recorded signature was made for a different artifact(记录的签名是为另一个制品生成的)
E0333
signing: a recorded signature is not the one a pull would record
A recorded signature is not the one a pull would record(记录的签名不是 pull 将记录的签名)
E0334
an omits entry left out nothing the source rendered
An omits entry left out nothing the source rendered(omits 条目没有排除任何源渲染的内容)
E0335
provider does not support omits
The provider does not support omits(provider 不支持 omits)
E0336
a provider's omitted counts do not match the omits entries it was handed
A provider’s omitted counts do not match the omits entries it was handed(provider 的省略计数与交给它的 omits 条目不匹配)
E0337
no importer plugin version satisfies the plugins.importer entry's version pin
A plugins.importer entry pins a version of its importer the catalog does not hold(该条目固定了目录中不存在的导入器版本)
E0338
importer is attached by more than one plugins.importer entry
An importer is attached by more than one plugins.importer entry(一个导入器被多个 plugins.importer 条目附加)
E0339
more than one importer recognises the source
More than one importer recognises the source(不止一个导入器识别出该源)
E0340
a name this operation writes holds a path segment Windows cannot hold as written
A name the operation writes holds a part Windows cannot hold(操作写入的名称含有 Windows 无法容纳的部分)
E0341
the importer serving the source's format declares no file patterns, so it reads one file and cannot read a directory
An importer that declares no file patterns is handed a directory(未声明文件模式的导入器被交给了一个目录)
E0342
no file in the directory matches the file patterns the importer serving the source's format declares
No file in the directory matches the importer’s file patterns(目录中没有文件匹配导入器的文件模式)
E0343
a file read from the directory and a file named in the importer's `with.sources` have the same name
从目录读取的文件与 importer 的 with.sources 中指定的文件同名
E0344
an entry this publication carries cannot be used on Windows
A published archive carries an entry Windows cannot use(发布的归档包含 Windows 无法使用的条目)
E0345
a container declares one environment variable twice
A container gives one environment variable two values(一个容器为同一个环境变量赋了两个值)
E0346
a Component's annotation stating how its metrics authenticate disagrees with whether it declares the provides key saying an instance's metrics need a credential
Component 的指标注解与其 provides 键不一致
E0347
template reads the render facts of a component its host is wired to, but the FeatureRecipe does not set readsTargetRenderFacts
A template reads its targets’ render facts without declaring it(模板未声明即读取其目标的渲染事实)
E0348
pipeline step reads the render facts of a component its host is wired to, but a pipeline step reads only the host's own render facts
A pipeline step reads its targets’ render facts(流水线步骤读取其目标的渲染事实)
E0349
no Recipe in the workspace's catalog binds to the capability the import's target names
An import’s target names a capability no Recipe in the catalog binds to(导入的目标指定了目录中没有任何 Recipe 绑定的能力)
E0350
no importer recognises the source
No importer recognises the source(没有导入器识别出该源)
E0351
provider does not support boundary artifacts
The provider does not support boundary artifacts(provider 不支持 boundary artifacts)
E0352
boundary output directory does not name a directory beneath the output root
A boundary’s output directory is not a directory beneath the output root(boundary 的输出目录不是输出根目录下的目录)
E0353
boundary-level Feature instance name is not a directory name
A boundary-level Feature is named . or ..(边界级 Feature 的名称为单点或双点)
E0354
a template does more than copy a value it reads off a cross-boundary link
A template did more than copy a value it read off a cross-boundary link(模板对从跨边界链接读取的值所做的不只是复制)
E0355
inject delivery: shape must be a list of entries, each `in:` with exactly one of `from:` or `value:`
An inject: delivery is not a list of entries(注入交付不是条目列表)
E0356
suspend requires form: scheduled
A workload suspend: is set on a form other than scheduled(workload 的暂停字段设置在定时以外的形式上)
E0357
a Manifest name mapping's key names no component instance or attachment in this build, so the entry binds nothing
A Manifest name mapping names nothing in the build(Manifest 的 name 映射未指向构建中的任何内容)
E0358
uses edge target names a component its module does not export
A uses target names a module’s component the module does not export(uses 目标指向了模块未导出的组件)
E0359
no source adapter is registered in this program for the source kind
No source adapter is registered in this program for a source kind(本程序中没有为某个源类型注册 source adapter)
E0360
the netrc file could not be read
The netrc file cannot be read(无法读取 netrc 文件)
E0361
the source URL carries a credential
A source URL carries a credential(源 URL 携带了凭据)
E0362
inject entry on a connection carries `value:`; a connection delivers the target's published keys, each named with `from:`
An inject: entry on a connection carries a literal(连接上的注入条目携带字面值)
E0363
annotation subkey is not routed by the annotation's binding
An annotation subkey is not routed by its binding(注解子键未被其绑定路由)
E0364
a value template failed while it ran
A value template failed while it ran(值模板在运行时失败)
E0365
boundary-level Feature's output is routed to a dispatch path nothing assembles
A boundary-level Feature’s output reaches no assembled file(边界级 Feature 的输出未进入任何组装文件)
E0366
FeatureRecipe injectMapping output could not be read as a dictionary of deliveries
An attached Feature’s injectMapping output cannot be read(已附加 Feature 的 injectMapping 输出无法读取)
E0367
a scalar annotation value does not route to exactly one path of its binding
A bare annotation value does not route to exactly one path of its binding(裸注解值未能路由到其绑定中恰好一条路径)
E0368
FeatureRecipe injectMapping output writes a key no delivery mechanism of the host reads
An attached Feature’s injectMapping output writes deliveries under a key nothing delivers(已附加 Feature 的 injectMapping 输出将交付项写在一个不会交付任何内容的键下)
E0369
template reads a path as a value and iterates it, and the data holds nothing at that path
A template reads and iterates a path that holds nothing(模板读取并迭代一个不包含任何内容的路径)
E0370
a pipeline declares one step id twice
A pipeline declares one step id twice (流水线将同一个步骤 id 声明了两次)
E0371
catalog document declares a kind a catalog does not hold
A catalog document declares a kind a catalog does not hold (catalog 文档声明了 catalog 不包含的种类)
E0372
inject entry on an attachment carries `value:`; an attachment delivers the keys its FeatureRecipe publishes, each named with `from:`, and a literal belongs in the component's own inject block
An inject: entry on an attached Feature carries a literal(附加 Feature 上的注入条目携带了字面值)
E0373
a document declares an API version this compiler no longer reads
A document declares an API version this compiler no longer reads(文档声明了此编译器不再读取的 API 版本)
E0374
a plugin declares a plugin ABI version this compiler no longer speaks
A plugin declares a plugin ABI version this compiler no longer speaks(插件声明了此编译器不再支持的插件 ABI 版本)
E0375
oci: artifact carries a media type this compiler no longer reads
An artifact carries a media type this compiler no longer reads(制品带有此编译器不再读取的媒体类型)
E0376
egress: the server did not answer in time
A server did not answer in time (服务器未及时应答)
E0377
registry: the repository listing did not end in time
A registry’s repository listing did not end in time (注册中心的仓库列表未及时结束)