错误哨兵值——权威参考
编译器发出的每个致命中止都会指明一个条件,每个条件带有三个标识符,因为识别条件、记录条件和引用条件是三项不同的工作。哨兵值是 errors.Is 匹配的 Go 值,通过调用声明包导出的访问器获得:它是 Go 代码用来识别条件的标识符。代码是条件注册时使用的字符串:它用文字为条件本身命名,并且在周围的 Go 包演进时保持不变——它是程序记录的标识符。短代码是字母 E 加四位数字,短到可以口头念出、输入搜索框或粘贴到报告中:它是人引用的标识符。一个条件,三个标识符——匹配哨兵值以在 Go 中识别条件,需要记录或以其为键时读取代码,并通过本页下方列出所有条件的表格解析短代码。
面向用户的诊断信息(即 fatal-halts.md 和 error-translation.md 中收录的带前缀消息)承载面向开发者的说明文字;被包装的哨兵值则是程序化使用方中 errors.Is 进行匹配的对象。
本页是该目录以哨兵值为键的视图。编写 CI 门禁、IDE 集成或需要区分错误类型的构建编排代码的程序员,使用标准的 errors.Is 谓词与此处列出的哨兵值进行匹配。通过阅读输出的错误文本来调试构建的作者,通常需要以消息为键的视图——构建中止错误见 fatal-halts.md,提示性输出见 warnings.md。
下表中的每一行都指明一个访问器——一个不带参数、从该表指明的包中导出、返回哨兵值的函数。导入该包并调用访问器是受支持的集成接口,因此表中每个访问器都带有括号——调用才能产生 errors.Is 可匹配的值,不带括号的名称是一个函数而不是错误:
import ( "errors"
"github.com/aggrega-ai/aggrega-cli/pkg/resolver")
if errors.Is(err, resolver.ErrParameterContractViolation()) { // handle parameter contract violations}三个标识符各自承担稳定性,这种分离正是一个条件同时拥有三者的原因。下列访问器在补丁版本之间保持稳定;重命名或移除会在执行该变更的版本的变更日志条目中公布,而在包内新增访问器属于增量变更,不会破坏现有的匹配代码。代码在其条件发布后即固定不变,因此凡是需要持久地指明条件之处,都应记录代码:重命名访问器不会改变其条件注册时使用的代码,你记录下的代码在 Go 接口重构后依然有效。短代码是三者中最持久的:编号只分配一次随后固定,已退役条件的编号保持退役状态,而不会分配给其他条件,因此旧报告中记录的短代码仍然指向记录时所指的条件。这一点是强制执行的,而不只是一种意图——在已退役编号下声明的条件,会在每次运行时、在编译器读取任何输入之前被拒绝——并且每个已退役编号都与现行编号一起发布在所有条件的表格中。下面的代码列给出代码,它是结构化诊断的客户端无需链接这些包即可读取的值。它是发布出来的而非推断出来的,因为它不必重复所在行的内容——重新导出的名称报告其所转发条件的代码,规则的代码为规则而非访问器命名。消息列是哨兵值呈现的字面文本;面向用户的诊断会在该文本前加上带方括号的头部和源位置。该头部带有条件的短代码,若该次出现有类别,则在旁边附上类别,如 [DEVELOPER_ERROR E0007]——因此读者可以分别解析两者:类别(DEVELOPER_ERROR / OPS_ERROR / CATALOG_ERROR / TRANSLATION_ERROR / FETCH_ERROR / POLICY_ERROR / TRUST_ERROR)在 error-translation.md 中讲解,短代码则在本页所有条件的表格中解析。若条件由插件引发,代码标记会以引发它的插件加以限定——[TRANSLATION_ERROR provider/example:1.0.0/E0007]——短代码是最后一段;error-translation.md 说明了为何存在该限定符,以及为何应解析的是最后一段。
读取条件的代码
代码只命名条件本身,不含其他信息,采用 kebab-case 形式——parameter-contract-violation、lockfile-drift。它不带任何前缀:不带声明它的包,不带引发它的阶段,也不带任何形式的分组。因此,当编译器围绕它重组时,代码保持不变;一个在编译中多处引发的条件仍然只有一个名称。每个条件的名称本身就各不相同,因此无需前缀,而且两个条件不能注册在同一个代码下。使用 github.com/aggrega-ai/aggrega-cli/pkg/errors 中的 CodeOf 从错误中读取代码,它像 errors.Is 一样遍历包装链,因此无论错误在返回给你的途中被包装了多少层,代码都会保留。该包本身也名为 errors,因此需要用导入别名将其与标准库区分开:
package release
import ( "log"
aggregaerrors "github.com/aggrega-ai/aggrega-cli/pkg/errors" "github.com/aggrega-ai/aggrega-cli/pkg/resolver")
// Load reads a Release and reports the code of whatever condition halted it.func Load(path string) error { _, err := resolver.LoadRelease(path) if err == nil { return nil } if code, ok := aggregaerrors.CodeOf(err); ok { // code names the condition in words, such as parameter-contract-violation. log.Printf("%s halted: %s", path, code) } return err}CodeOf 还会报告链中是否有任何错误携带了代码;一条不携带任何代码的链只是关于该链的一个事实,而不是一次失败。如果你更愿意自己匹配该接口,同一个包将其导出为 CodedError,errors.As 会在同样的遍历中找到它。
代码只单向传递。 它是条件所报告的内容,而绝不是让匹配器识别条件的依据:把该字符串写进你自己的代码,得到的只是一个字符串,从字符串无法回到 errors.Is 所匹配的值。匹配哨兵值以识别条件;读取代码以记录条件。
aggrega 在终端上打印的代码是短代码,而不是这个代码。 一条中止诊断以一个方括号头部开头,其中携带条件的短代码,若该次出现有类别,则类别位于其旁——[DEVELOPER_ERROR E0007];若条件由插件引发、代码由引发它的插件限定,则为 [TRANSLATION_ERROR provider/example:1.0.0/E0007];若该失败没有可引导你去的关注方,则为 [E0007]——随后是源位置以及 fatal-halts.md 中收录的消息文本。描述性代码用文字命名条件,对于该位置而言过宽:对于最长的条件,它会在消息开始之前就占满一个窄终端,这正是第二个紧凑标识符存在的全部原因。因此,当你手头只有打印输出时,应以短代码为依据,它可在本页下方的所有条件的表格中解析:从一个可以在电话中读出的编号,你就能找到该条件、其访问器及其消息文本。aggrega explain <code> 在终端中完成这一解析——它接受条件的任一代码,打印该条件以及记录编写修复方法的条目,详见 aggrega explain。若要依据措辞而非标识符排查,仍可使用 fatal-halts.md 中以消息为键的视图。
代码确实会在 Go 之外传递的地方,是编译器即服务守护进程发布的结构化诊断,它作为每个条目中独立的 code 字段出现,而不是被并入消息文本——因此编辑器扩展或该协议的任何其他客户端,无需链接这些包、无需解析文本,即可根据条目所报告的内容进行分支。无论由谁分配,这一个键都携带一个可供机器匹配的代码,而条目会说明是哪一层引发了它。那里的代码有三种来源,其中第三种正是为什么一个能在本页查到的代码,其本身并不表示有任何东西失败:
- 失败所指明的条件的代码,即本页所收录的内容。
- 关于渲染输出的建议的类别代码——
unsupported-field就是其中之一,warnings.md 对其有描述。它在建议被引发的地方分配,而不是作为条件注册,因此在这里没有对应的行。 - 关于所编写文档的建议的注册代码——一个与已声明名称只差一处编辑的名称、一个没有任何东西读取的参数。这类发现以与失败相同的形式指明条件,因此其代码是注册的,并且在本页有对应的行,读取该行即可了解该发现涉及什么。
因此,你会从中止中读到的同一个代码,也可能来自一次已完成的构建,由一个对结果没有任何改变的发现携带。区分二者的是你得到的结果以及条目所指明的层——绝不是代码本身的形式,也绝不是它能否在这里解析。若生成条目的任何环节都没有分配代码,则省略该字段:即未指明任何 Aggrega 自身条件的失败,以及其引发方未分配代码的建议。aggrega serve 记录了条目结构、指明层的键,以及该字段何时出现。
结构化诊断同时携带条件的两个标识符,分清哪个是哪个,决定了你拿到的是可以据以行动的标识符,还是无法据以行动的标识符。 上面的 code 键供程序使用:以连字符连接、用文字命名条件,因此根据它进行分支的扩展读起来就是其含义,它也是 CodeOf 在 Go 中报告的值。其旁的 shortCode 键供人使用——字母 E 加四位数字,与中止诊断在其方括号头部中打印的标记相同。它是你在电话中读出、输入搜索框或粘贴进 issue 的内容,也是所有条件的表格所使用的键。
二者都不是对方的缩写,也都不是对方的后备。根据描述性代码进行匹配;向读者展示短代码。只提供描述性代码的界面,相当于把一个面向匹配器的标识符交给作者;而根据短代码进行匹配的界面,则是在匹配一个对条件毫无说明的编号——这就是为什么两者都会传递,而不是只选其一。
第三个键 codeDescription 携带条件的发布位置,作为一个可打开以进一步了解该诊断的引用。其地址解析到本页所有条件的表格,因此从编辑器跟随它的读者到达时,手中握着该表格所用的短代码。条目要么同时携带短代码和引用,要么两者都不携带:恰好在条目指明一个已注册条件——即在该表格中有对应行的条件——时两者都存在;当代码指明一类建议,或指明来自你自己的、Aggrega 未声明的 linter 中某条约定规则的标识时,两者都不存在,因为这些没有可引用的编号,这里也没有描述它们的内容。
反方向——从你手中的代码到它所指明的条件——下面的表格就是发布的列表。 每一行都在代码旁列出在 Go 中产生同一条件的访问器,因此从结构化诊断中读到的代码,可以解析为一个你可以匹配的名称,以及该条件所渲染的文本。这些表格涵盖访问器可以导入的条件,有两类代码不在其中:类别代码,它指明的是一类建议而非条件,因此没有可列于其旁的访问器;以及其条件仅在你无法导入的包中声明、且未在任何地方重新导出的代码,它没有可列于其旁的可匹配名称。第二类仍然指明一个条件,该条件仍然有短代码——本页下方所有条件的表格以短代码而非可导入名称为键,因此也涵盖了这些条件。
可匹配的接口面,按声明包分组
下面每一节对应一个可导入的包。节标题是相对于模块路径 github.com/aggrega-ai/aggrega-cli 的包路径,因此标题为 pkg/resolver 的一节以 github.com/aggrega-ai/aggrega-cli/pkg/resolver 导入。
条目按声明该 sentinel 的包分组,因为匹配方导入的正是这个包。条件在构建的哪个阶段触发是另一个问题,本页有意不作回答:单个 sentinel 经常从多处触发,还有一些只从模块未导出的代码中触发,因此任何逐条给出的答案都无法对每一行都成立。按消息索引的视图以可观察的方式回答了“在构建中何时触发”的问题,首先是 fatal-halts.md。
少数名称出现在多个包中。它们是同一个共享值的重新导出,而不是两个条件,因此匹配任一名称都会成功;当两个名称都可导入时,表格会注明这一点。两行带有相同的代码,这是在 Go 之外的客户端所持有的标识符上表述的同一事实:一个条件,一个代码,无论有多少名称指向它。
pkg/catalog
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrAllVersionsRetracted() | all-versions-retracted | every published version this reference could select has been withdrawn |
ErrAmbiguousImporterPlugin() | ambiguous-importer-plugin | format is advertised by more than one importer plugin |
ErrAmbiguousParserPlugin() | ambiguous-parser-plugin | format is advertised by more than one parser plugin |
ErrAmbiguousProviderPlugin() | ambiguous-provider-plugin | capability is served by more than one provider plugin; add a plugins.providers entry to select one |
ErrAmbiguousTypeMapping() | ambiguous-type-mapping | manifest maps multiple version-distinct keys to the same base type; the type-to-recipe lookup is ambiguous |
ErrDuplicateEntityIdentity() | duplicate-entity-identity | duplicate entity identity within a single catalog directory |
ErrImporterVersionUnsatisfiable() | importer-version-unsatisfiable | no importer plugin version satisfies the plugins.importer entry's version pin |
ErrManifestImplementsMismatch() | manifest-implements-mismatch | manifest mapping entry's recipe spec.implements does not match the mapped component-type / feature-type key |
ErrNameMappingMatchedNothing() | name-mapping-matched-nothing | a Manifest name mapping's key names no component instance or attachment in this build, so the entry binds nothing |
ErrNoImporterForFormat() | no-importer-for-format | no importer plugin advertises the requested format |
ErrNoParserForFormat() | no-parser-for-format | no parser plugin advertises the requested format |
ErrNoRecipeResolved() | no-recipe-resolved | no recipe resolved for component/feature instance: add an explicit Manifest mapping for its type |
ErrProviderBindingCapabilityUnserved() | provider-binding-capability-unserved | plugins.providers entry names a capability no provider-rendering plugin the build reads serves |
ErrProviderBindingUnsatisfied() | provider-binding-unsatisfied | plugins.providers entry names a plugin no provider-rendering plugin serving the capability matches |
ErrProviderVersionUnsatisfiable() | provider-version-unsatisfiable | no provider-rendering plugin version satisfies the recipe's provider version pin |
ErrQualifiedPluginReference() | plugin-reference-must-not-be-registry-qualified | wasm plugin reference must be the plugin coordinate identity (<pluginType>/<name>:<version>), not a registry-qualified or artifact path |
ErrUnknownCatalogDocumentKind() | unknown-catalog-document-kind | catalog document declares a kind a catalog does not hold |
ErrUnsatisfiableEntityVersion() | unsatisfiable-entity-version | no catalog version satisfies the referenced version constraint |
ErrUnscopedPluginReference() | plugin-reference-must-be-scoped | wasm plugin reference must carry a pluginType scope (<pluginType>/<name>); an empty scope cannot bind to an OCI location |
ErrUnscopedRecipeReference() | recipe-reference-must-be-scoped | recipe reference must be provider-scoped (<provider>/<name>); an empty provider cannot bind to an OCI location |
ErrUnusableSchemaImport() | unusable-schema-import | a schema `$import:` could not be applied |
ErrManifestImplementsMismatch()与pkg/resolver.ErrManifestImplementsMismatch()是同一个值,因此匹配任一名称都会成功。
pkg/closure
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrInvalidLibraryRef() | invalid-library-ref | resolve: invalid library reference URI |
ErrMVSConflict() | version-selection-conflict | resolve: minimal version selection conflict — incompatible library version requirements |
ErrNoAggregateLoader() | catalog-cannot-load-sub-aggregate-bodies | resolve: catalog lookup cannot load resolved sub-aggregate bodies |
ErrNoRecipeLoader() | catalog-cannot-load-recipe-bodies | resolve: catalog lookup cannot load resolved recipe and plugin bodies |
ErrSourceTemplateAtLockTime() | source-template-at-lock-time | resolve: source-template evaluation failure at lock time |
ErrSourceTemplateParse() | source-template-not-parsable | resolve: source-template parse error |
ErrSourceTemplateProvidesRef() | source-template-provides-ref | resolve: source-template references .provides (invalid reverse reference) |
ErrSubAggregateDepth() | sub-aggregate-depth | resolve: sub-aggregate inclusion depth exceeded |
ErrUnresolvableURI() | unresolvable-uri | resolve: no entity in the catalog matches this URI |
pkg/compactform
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrAmbiguousDispatch() | ambiguous-dispatch | compactform: ambiguous dispatch — $mode required |
ErrCircularRef() | reference-cycle | circular reference expansion |
ErrConstraintTypeMismatch() | constraint-type-mismatch | compactform: constraint not valid for declared type |
ErrEscapeContentInvalid() | escape-content-invalid | compactform: $jsonschema content invalid |
ErrHostInLibraryRef() | host-in-library-ref | compactform: cross-document $ref carries a registry host; reference the library by identity |
ErrReferenceUnresolvable() | reference-unresolvable | compactform: $ref unresolvable |
ErrUnknownKeyword() | unknown-keyword | compactform: unknown keyword |
ErrUnresolvedSchemaLibraryRef() | unresolved-schema-library-ref | compactform: cross-document $ref target not found |
ErrCircularRef()与pkg/refcycle.ErrCycle()是同一个值,因此匹配任一名称都会成功。
pkg/deprecation
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrDeprecatedEntity() | deprecated-entity | deprecation: build consumes a deprecated entity |
pkg/docscache
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrFetchNotFound() | fetch-not-found | oci: artifact not found at remote source |
ErrNotDocsBundle() | not-docs-bundle | docscache: artifact is not a documentation bundle |
ErrPageNotFound() | page-not-found | docscache: page not found in documentation bundle |
ErrFetchNotFound()与pkg/oci.ErrFetchNotFound()是同一个值,因此匹配任一名称都会成功。
pkg/egress
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrNoAnswerInTime() | no-answer-in-time | egress: the server did not answer in time |
ErrOfflineEgress() | offline-egress | 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 |
pkg/externalinputs
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrAcquisitionDisabled() | acquisition-disabled | externalinputs: acquisition is disabled for unpinned inputs |
ErrDigestMismatch() | digest-mismatch | externalinputs: fetched bytes mismatch the pinned digest |
ErrSchemeNotAllowed() | scheme-not-allowed | externalinputs: URL scheme is not allowed |
ErrStoreCorrupt() | store-corrupt | externalinputs: store blob mismatches its pinned record |
pkg/lockfile
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrLockfileDrift() | lockfile-drift | lockfile: out of date; it no longer matches what its Release resolves to |
ErrLockfileInvalid() | lockfile-invalid | lockfile: file failed schema validation |
ErrSignatureNotRecorded() | signature-not-recorded | signing: no verified signature is recorded for an artifact that requires one |
pkg/oci
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrAmbiguousContentLayer() | ambiguous-content-layer | oci: manifest has multiple layers of the expected content media type |
ErrBundleAmbiguousEntityDocument() | bundle-ambiguous-entity-document | oci: published bundle carries more than one entity document |
ErrBundleNoEntityDocument() | bundle-no-entity-document | oci: published bundle carries no entity document |
ErrBundleUnreadable() | bundle-unreadable | oci: published bundle cannot be unpacked |
ErrCacheLocationOutsideCache() | cache-location-outside-cache | a value a cache location is built from would place cached files outside the place it names in the cache |
ErrCachedManifestIntegrity() | cached-manifest-integrity | oci: cached manifest digest mismatch |
ErrFetchIntegrity() | fetch-integrity | oci: content digest mismatch |
ErrFetchNetworkUnreachable() | fetch-network-unreachable | oci: network unreachable |
ErrFetchNotFound() | fetch-not-found | oci: artifact not found at remote source |
ErrFetchUnauthorized() | fetch-unauthorized | oci: authentication required or failed |
ErrImmutableTagConflict() | immutable-tag-conflict | oci: tag already published with different content |
ErrNoContentLayer() | no-content-layer | oci: manifest has no layer of the expected content media type |
ErrOCILocationCollision() | oci-location-collision | oci: distinct catalog identities map to the same OCI repository location |
ErrPublishedArtifactNotAnEntity() | published-artifact-not-an-entity | oci: published artifact is not an entity document |
ErrReferrerDiscoveryUnavailable() | referrer-discovery-unavailable | oci: referrer discovery could not be completed |
ErrRegistryTooBusy() | registry-too-busy | oci: the registry kept asking to slow down |
ErrRetiredMediaType() | retired-media-type | oci: artifact carries a media type this compiler no longer reads |
ErrSignatureBundleDigestMismatch() | signature-bundle-digest-mismatch | cached signature bundle does not match its recorded digest |
ErrSignatureForAnotherArtifact() | signature-for-another-artifact | signing: the recorded signature was made for a different artifact |
ErrUnknownEntityKind() | unknown-entity-kind | oci: unknown entity kind for mediatype dispatch |
pkg/pathscope
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrNameWindowsCannotHold() | name-windows-cannot-hold | a name this operation writes holds a path segment Windows cannot hold as written |
pkg/pluginpath
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrPluginArtifactNotFound() | plugin-artifact-not-found | plugin artifact not found on this machine |
ErrPluginEntityNotFound() | plugin-entity-not-found | plugin reference is not a Plugin entity |
pkg/pluginstrust
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrVerdictAttachmentNotConfigured() | verdict-attachment-not-configured | a plugin recorded as trusted for an accept-or-reject verdict is no longer attached at any verdict role |
pkg/plugintest
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrCommandsMismatch() | wasm-command-set-mismatch | wasm: recorded command mirror does not match plugin describe() |
ErrContractMismatch() | wasm-contract-mismatch | wasm: entity contract claim does not match plugin describe() |
ErrHostFunctionsMismatch() | wasm-host-function-set-mismatch | wasm: stamped host-function record does not match .wasm imports |
ErrRejected() | wasm-manifest-rejected | wasm: plugin rejected by the sandbox |
ErrTypeMismatch() | wasm-plugin-type-mismatch | wasm: declared plugin type does not match plugin describe() |
pkg/readscope
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrReadLeadsOutOfWorkspace() | read-leads-out-of-workspace | a file this operation reads leads through a link out of the directory it must stay inside |
ErrReferenceLeadsOutOfWorkspace() | reference-leads-out-of-workspace | a reference a document makes to another file leads out of the directory it must stay inside |
pkg/recipepin
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrEntityNotPinned() | entity-not-pinned | an input the entity reads has no pin recorded for it in the entity.lock beside it |
ErrLocalSourceContentMismatch() | local-source-content-mismatch | the files of the entity's local source do not match the pins recorded for them in entity.lock |
pkg/refcycle
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrCycle() | reference-cycle | circular reference expansion |
pkg/registrytrust
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrMalformedTrust() | malformed-trust-policy | registrytrust: advertised trust config is malformed |
ErrNoTrustAdvertised() | no-trust-advertised | registrytrust: registry advertises no trust config |
ErrOfflineRegistrationWithoutTrustPolicy() | offline-registration-without-trust-policy | 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>` |
pkg/resolver
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrAnnotationBindingPillarOverlap() | annotation-binding-pillar-overlap | annotation binding declares one path in both pillar lists |
ErrAnnotationBindingTargetUnresolved() | annotation-binding-target-unresolved | annotation binding does not resolve against its target Feature |
ErrAnnotationScalarNotRoutable() | annotation-scalar-not-routable | a scalar annotation value does not route to exactly one path of its binding |
ErrAnnotationSidePillarMismatch() | annotation-side-pillar-mismatch | annotation routes through a pillar its authoring side may not use |
ErrAnnotationSubkeyNotBound() | annotation-subkey-not-bound | annotation subkey is not routed by the annotation's binding |
ErrAnnotationSubkeyNotConforming() | annotation-subkey-not-conforming | annotation subkey does not conform to the target Feature's schema at the routed pillar |
ErrAttachmentInjectValue() | attachment-inject-value | 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 |
ErrAttachmentSlotNearMiss() | attachment-slot-near-miss | attachment name is a near miss for a declared slot |
ErrAttachmentSlotShape() | attachment-slot-shape | attachment does not conform to its declared slot shape |
ErrConnectionAttachmentSlotUndeclared() | connection-attachment-slot-undeclared | a connection carries an attachment under a name its socket declares no slot for |
ErrDuplicateBoundaryComponent() | duplicate-boundary-component | component declared in more than one boundary: declare each component in exactly one boundary |
ErrDuplicateTriadIdentity() | duplicate-triad-identity | duplicate Aggregate/Manifest identity (metadata.name) in the Release directory |
ErrFeatureMergeConflict() | feature-merge-conflict | feature merge conflict: reconcile the Aggregate and Release declarations for the feature |
ErrGuardEntityViewInconsistency() | internal-catalog-view-disagreement | the compiler's own views of the catalog disagree |
ErrInheritedBoundaryDirectoryIsLiteral() | inherited-boundary-directory-is-literal | inherited boundary directory carries no template variable, so it resolves to the path the extended Release writes to |
ErrInjectDeliveryShape() | inject-delivery-shape | inject delivery: shape must be a list of entries, each `in:` with exactly one of `from:` or `value:` |
ErrInjectEntryAmbiguous() | inject-entry-ambiguous | inject entry carries both `value:` and `from:`; schema requires exactly one |
ErrInjectKeyCollision() | inject-key-collision | duplicate delivery key across inject sources |
ErrInvalidInjectKey() | invalid-inject-key | invalid inject key: the from-key must name a provides key its source publishes |
ErrInvalidParameterRef() | invalid-parameter-ref | invalid parameter reference: check the {{ .parameters.* }} expression names a declared parameter and parses as a Go template |
ErrMalformedRecipeReference() | malformed-recipe-reference | malformed recipe reference in a Manifest mapping value |
ErrManifestCrossBindingPillarCollision() | manifest-cross-binding-pillar-collision | manifest annotation bindings collide on same Feature path+pillar |
ErrManifestImplementsMismatch() | manifest-implements-mismatch | manifest mapping entry's recipe spec.implements does not match the mapped component-type / feature-type key |
ErrManifestReservedPrefix() | manifest-reserved-prefix | manifest annotation binding uses reserved prefix |
ErrMisnamedSlotFill() | misnamed-slot-fill | attachment written under a name no slot declares fits a slot its component leaves empty |
ErrMissingRequiredFeature() | missing-required-feature | missing required feature: attach a Feature of the required type to the component |
ErrMissingRequiredSocket() | missing-required-socket | required uses socket not populated |
ErrParameterContractViolation() | parameter-contract-violation | parameter contract violated |
ErrParameterMissing() | parameter-missing | required parameter not supplied |
ErrProvidesKeyNotDeclared() | provides-key-not-declared | Recipe publishes a provides key its Component does not declare |
ErrReleaseChainComposesBothRoutingKeys() | release-chain-composes-both-routing-keys | release extends chain composes both named boundaries and top-level components: declare one routing shape across the chain, never both |
ErrSchemaConformance() | schema-conformance | authored pillar does not conform to its declared schema |
ErrSchemaContractCompileFailure() | schema-contract-compile-failure | 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 |
ErrSelfInjectForbidden() | self-inject-forbidden | self-inject on component without spec.inject allowlist |
ErrTriadRefUnresolvable() | triad-ref-unresolvable | aggregate/manifest reference unresolvable |
ErrUnknownUsesSocket() | unknown-uses-socket | 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 |
ErrUnnormalizedRelease() | release-not-in-canonical-form | release reached resolve un-normalized (non-empty root components alongside a synthesized default boundary) |
ErrUnreadParameter() | unread-parameter | declared parameter is read by no reference in the Aggregate |
ErrUsesInjectValue() | uses-inject-value | inject entry on a connection carries `value:`; a connection delivers the target's published keys, each named with `from:` |
ErrUsesSocketNearMiss() | uses-socket-near-miss | uses socket name is a near miss for a declared socket |
ErrVerdictPluginTrustMismatch() | verdict-plugin-trust-mismatch | the digest recorded as trusted for this plugin does not match the digest its cached manifest reports |
ErrYAMLLoad() | document-not-loadable | file load failed: the file could not be read, or its bytes did not parse |
pkg/signing
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrKeylessLive() | keyless-signing-requires-network | signing: keyless signing requires a live identity provider, Fulcio, and Rekor |
ErrMixedSigningCredentials() | mixed-signing-credentials | signing: the references named together need different signing credentials, so nothing was signed |
ErrNoSignatureFound() | no-signature-found | signing: no signature found for an artifact that requires one |
ErrNoTrustedIdentities() | no-trusted-identities | signing: keyless verification requires at least one trusted identity |
ErrSignatureInvalid() | signature-invalid | signing: signature does not verify |
ErrSignatureVerificationFailed() | signature-verification-failed | signing: signature bundle does not verify |
ErrSigningPolicyRequiresSignature() | signing-policy-requires-signature | signing: signing policy requires a signature for this artifact kind; refusing to push unsigned content |
ErrTrustRootLoad() | trust-root-not-loadable | signing: cannot load pinned trust root |
ErrUnsignedPushRefused() | unsigned-push-refused | signing: registry requires signatures; refusing to push unsigned content |
ErrUnsupportedKey() | unsupported-key | signing: unsupported held-key type |
ErrUntrustedIdentity() | untrusted-identity | signing: signature identity is not trusted for this registry |
pkg/sourcecache
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrFetchIntegrity() | fetch-integrity | oci: content digest mismatch |
ErrFetchNotFound() | fetch-not-found | oci: artifact not found at remote source |
ErrFetchIntegrity()与pkg/oci.ErrFetchIntegrity()是同一个值,因此匹配任一名称都会成功。ErrFetchNotFound()与pkg/oci.ErrFetchNotFound()是同一个值,因此匹配任一名称都会成功。
pkg/sourcekind
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrUnknownKind() | unknown-source-kind | no source adapter serves the source kind |
pkg/sourceresolver
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrFetchIntegrity() | fetch-integrity | oci: content digest mismatch |
ErrFetchNetworkUnreachable() | fetch-network-unreachable | oci: network unreachable |
ErrFetchNotFound() | fetch-not-found | oci: artifact not found at remote source |
ErrFetchUnauthorized() | fetch-unauthorized | oci: authentication required or failed |
ErrNoAdapterRegistered() | source-adapter-not-registered | no source adapter is registered in this program for the source kind |
ErrFetchIntegrity()与pkg/oci.ErrFetchIntegrity()是同一个值,因此匹配任一名称都会成功。ErrFetchNetworkUnreachable()与pkg/oci.ErrFetchNetworkUnreachable()是同一个值,因此匹配任一名称都会成功。ErrFetchNotFound()与pkg/oci.ErrFetchNotFound()是同一个值,因此匹配任一名称都会成功。ErrFetchUnauthorized()与pkg/oci.ErrFetchUnauthorized()是同一个值,因此匹配任一名称都会成功。
pkg/sourceresolver/cacheslot
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrEmptyWorkspaceRoot() | empty-workspace-root | cacheslot: empty workspaceRoot |
pkg/sourceresolver/netrc
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrNetrcFileUnreadable() | netrc-file-unreadable | the netrc file could not be read |
ErrSourceURLCarriesCredential() | source-url-carries-credential | the source URL carries a credential |
pkg/types
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrArtifactEntryShape() | artifact-entry-shape | artifacts entry: shape must be a string scalar or {$import: <local-path>} |
ErrArtifactLibraryEntryShape() | artifact-library-entry-shape | artifactlibrary: entry must be a mapping of filename to a string body |
ErrForbiddenKeyword() | forbidden-keyword | schemalibrary: forbidden JSON Schema keyword |
ErrLibraryReferenceWhitespace() | library-reference-whitespace | library reference: a reference to a library entry carries no whitespace or line break |
ErrMalformedVersionPin() | malformed-version-pin | reference carries a malformed version pin |
ErrMappingEntryNotScalar() | mapping-entry-not-scalar | mappinglibrary: entry body must be a string scalar |
ErrOrderedMapDecodeDepthExceeded() | document-nesting-depth-exceeded | a document nests too many levels deep |
ErrParametersShape() | parameters-shape | parameters: shape must be an inline object or {$import: <local-path>} |
ErrTemplateNotFound() | template-not-found | schemalibrary: template not found |
ErrTemplateParamMissing() | template-param-missing | schemalibrary: template parameter missing |
ErrTemplateParamTypeMismatch() | template-param-type-mismatch | schemalibrary: template parameter type mismatch |
ErrValuesMappingShape() | values-mapping-shape | valuesmapping: shape must be a string scalar or {$import: <path-or-library-identity>} |
ErrWellKnownAnnotationScope() | well-known-annotation-scope | wellKnownAnnotations: a key is declared at a scope the provider's contract does not render |
ErrWorkloadEntryNotScalar() | workload-entry-not-scalar | workloadlibrary: entry body must be a string scalar |
ErrWorkloadTemplateShape() | workload-template-shape | workload: shape must be a string scalar or {$import: <path-or-library-identity>} |
pkg/usesedge
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrDanglingUsesTarget() | dangling-uses-target | uses edge target does not exist |
ErrReleaseEdgeRetarget() | release-edge-retarget | release edge retargets a developer-declared edge |
pkg/validator
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrAssertionNameCollision() | assertion-name-collision | assertion name declared twice across the extends chain |
ErrCyclicExtension() | cyclic-extension | cyclic extends chain |
ErrDuplicateContainerEnvironmentVariable() | duplicate-container-environment-variable | a container declares one environment variable twice |
ErrEmptySource() | recipe-source-is-empty | recipe source is an empty string, which names neither sourceless mode nor sourced mode |
ErrExtendsChainTooDeep() | extends-chain-too-deep | extends chain exceeds maximum depth |
ErrFeatureRecipeValuesMappingRequiresSource() | feature-recipe-values-mapping-requires-source | FeatureRecipe: valuesMapping requires source |
ErrInheritanceMerge() | extends-merge-failed | inheritance merge failed |
ErrRecipeFilenameCollisionAcrossInputKinds() | recipe-filename-collision-across-input-kinds | filename collision across input kinds: two input-kind blocks produced a file under one output name |
ErrRecipeNoInputKind() | recipe-no-input-kind | Recipe: at least one input kind required |
ErrRecipeOutputComponentLabelCollision() | recipe-output-component-label-collision | recipe output-component-labels constraint: key is also declared in outputLabels |
ErrRecipeOutputLabelReservedNamespace() | recipe-output-label-reserved-namespace | recipe output-labels constraint: key uses a reserved namespace |
ErrRecipeValuesMappingRequiresSource() | recipe-values-mapping-requires-source | Recipe: valuesMapping requires source |
ErrSlotNotReferenceable() | slot-not-referenceable | workload attachment slot is not referenceable |
ErrUnknownSchemaPillar() | unknown-schema-pillar | a schema block declares a key that names no data pillar |
ErrWorkloadFeaturesSchema() | workload-features-schema | workload featuresSchema cross-check failed |
ErrWorkloadValidation() | workload-not-valid | workload validation failed |
pkg/validator/envelope
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrDuplicatePipelineStepID() | duplicate-pipeline-step-id | a pipeline declares one step id twice |
ErrEntityEnvelope() | entity-envelope-invalid | document envelope validation failed |
ErrRetiredABIVersion() | retired-abi-version | a plugin declares a plugin ABI version this compiler no longer speaks |
ErrRetiredAPIVersion() | retired-api-version | a document declares an API version this compiler no longer reads |
pkg/validator/jsonschema
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrExtensionEval() | schema-extension-evaluation-failed | validator/jsonschema: x-aggrega extension evaluation failed |
ErrSchemaResolve() | schema-not-resolvable | validator/jsonschema: schema resolution failed |
pkg/validator/merger
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrMergeInvalid() | schema-merge-input-invalid | merger: invalid merge input |
pkg/workspaceconfig
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrAmbiguousRegistryAlias() | ambiguous-registry-alias | registry alias matches more than one host |
ErrCapabilityOnCrossCuttingSocket() | capability-on-cross-cutting-socket | a cross-cutting socket is bound by capability but attaches by uri |
ErrColonInProviderBindingCapability() | colon-in-provider-binding-capability | a provider socket binding names a capability containing a colon, which no Recipe can select |
ErrConfigInvalid() | workspace-config-invalid | workspace configuration is invalid |
ErrDuplicateImporterAttachment() | duplicate-importer-attachment | importer is attached by more than one plugins.importer entry |
ErrDuplicateProviderTarget() | duplicate-provider-target | capability is bound to more than one provider plugin |
ErrDuplicateRegistryAlias() | duplicate-registry-alias | registry alias is already used by another host |
ErrGovernanceRoleInvalid() | governance-role-invalid | a governance attachment declares no role or an unknown role |
ErrInertFieldOnProviderSocket() | inert-field-on-provider-socket | a provider socket binding sets a field with no referent on that socket |
pkg/writescope
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrWriteLeadsOutOfWorkspace() | write-leads-out-of-workspace | a path this operation writes or deletes leads through a link out of the directory it must stay inside |
pkg/yamlpos
| Sentinel | 代码 | 消息 |
|---|---|---|
ErrPositionOutOfRange() | position-out-of-range | position out of range |
携带另一个 sentinel 的 sentinel
ErrCacheMetadataInvalid(pkg/sourceresolver/metadata)报告一个已损坏的源制品缓存槽。它被声明为 ErrFetchIntegrity() 的包装,而不是自身独立的标识,因此它不出现在上面的表格中,并且针对 ErrFetchIntegrity() 的匹配对它同样成功。由于它包装了一个 sentinel 而不是声明一个 sentinel,它以值而不是函数的形式导出:按 ErrCacheMetadataInvalid 匹配它,不带括号。需要该特定条件时匹配这个包装,需要整个完整性类别时匹配被包装的 sentinel。
在同一个包中可通过第二个名称访问的哨兵错误
当一个包为同一个条件导出两个访问器(第二个声明为对第一个的转发)时,上面的表格列出声明它的访问器,而不列出转发名称。两个名称都从同一个包导出,因此能访问其中任一名称的导入也已经能访问另一个;再加一行只会把同一个条件以一个不会匹配到任何新内容的名称重复列出。匹配任一名称都会成功:转发返回的值与声明它的访问器返回的值相同。
这与跨包的情况不同。从另一个包重新导出的哨兵错误在每个包的表格中各占一行,因为导入其中一个包的匹配代码若不同时导入另一个包,就无法访问另一个包中的名称;而单个包内的转发不需要第二行,因为一次导入即可访问两个名称。
pkg/catalog 中的 ErrDuplicateRecipeIdentity() 就是这样一个转发:它返回 ErrDuplicateEntityIdentity(),后者是该包表格中列出的名称。
没有可匹配 sentinel 的条件
某些编译阶段在编译器未导出的包中声明其 sentinel,因此 errors.Is 没有可引用的对象,也无法针对它们编写匹配器。这里对它们进行描述而非列表,因为本页中的表格承诺其左侧列可以被解引用。
它们的诊断信息会通过输出的错误文本以及按消息索引的视图(尤其是 fatal-halts.md)完整地呈现给你,这是识别它们的受支持方式:
- 拓扑构建(图构建与 sub-aggregate 展平)会报告:无法加载的 sub-Aggregate,并指明无法访问的 Aggregate URI;结构形态与 schema 不符的
uses:声明;超出嵌套深度;以及展平后的节点 ID 冲突,即两个 sub-Aggregates 编译为同一节点 ID,必须重命名其中一个实例名以消除歧义。 - 图最终化(跨 Aggregate 与 Release 两个层面合并 Feature)会报告在两者之间声明不一致的 Feature 类型。
- 静态分析(选择器求值与跨节点类型安全检查)会报告:
selector:违规;无法越过的目录解析缺失,并指明不可达的实体;以及策略拒绝,即挂载在治理裁决角色上的插件拒绝了组装好的构建。策略拒绝带有POLICY_ERROR类别、执行拒绝的插件名称,以及该插件提供的规则消息。 - 渲染(provider 分派与按 provider 渲染)会报告未知的 provider。
- 嵌入式 Wasm 宿主加载器会发出它自己的防护 sentinel:manifest 被拒绝防护(插件请求了 AOT 纯度防火墙所拒绝的运行时访问能力)、guest panic 恢复,以及确定性的插件退出陷阱。运行插件时(例如通过
aggrega lint),这些情况会出现在面向用户的诊断中。Plugin 作者在宿主上测试 guest 时,可以通过上文列出的pkg/plugintest以可导入的名称访问相同的情况。
若要专门针对策略拒绝来控制流水线,应匹配诊断信息中的 POLICY_ERROR 类别前缀,而非 sentinel;该类别是错误接口中有文档说明的部分,详见 error-translation.md。
按短代码列出的所有条件
下表按相反方向进行查找:左列是短代码,旁边是该代码所指的条件以及该条件输出的文本。它涵盖 aggrega 可能报告的所有条件,包括上文各节无法列出的条件。
这种更广的覆盖范围正是此表的目的,而非偶然。上文各节以你可以导入的名称为键,因此一个仅在你无法导入的包中声明、且也未在任何你可导入之处重新导出的条件,在它们的左列中无可填写。此表以短代码为键,而每个条件都有短代码,因此任何可报告的条件都不会落在表外。你手中的短代码在此都能解析,无论其背后的条件是否还有可供匹配的访问器。
一个条件能列入此表,是因为编译器确实能够报告它。 表中各行由代码推导而来,而非抄录进代码:某个条件出现在此,是因为编译器中有某处会引发它,因此左列中的每个代码都是 aggrega 可能打印的代码。这就是此表作出的承诺,也正因如此,你可以把每一行当作一项确实会运行的检查来阅读。
有意为之的例外是在报告它的代码存在之前就已声明的条件,以便代码和措辞事先固定,不会在已引用它们的读者面前发生变化。这样的条件会在表格正下方以注释说明。它被列出而非隐藏——你手中的代码应当总能解析——旁边的注释会明确告诉你目前尚无构建引发它,以及需要具备什么才会引发。
已停用的编号也会列出,位于表格下方单独的一组注释中,并永久保留。 条件偶尔会被撤销——被覆盖范围更广的条件取代,或者从未有任何东西报告过它——从那一刻起,其编号即被停用:它永远不会分配给其他条件,因此你从旧报告中引用的短代码只能指代报告写成时它所指的内容。这一承诺是机制性的,而非编辑性的。在已停用编号下声明的条件会在编译器读取任何输入之前、在每次运行时被拒绝,因此任何 release 都不可能携带这样的条件——这与两个现行条件试图共用一个编号时所遇到的拒绝属于同一类,其措辞让你能分辨遇到的是哪一种。已停用代码的注释会告诉你(在停用时有记录的情况下)该代码曾指代什么,以及在该条件被取代的情况下,现在由哪个代码报告这一范围。
从不重用编号,也使编号序列留下了永久的空缺,而注释让这些空缺变得可读。缺失的编号本身并不能证明任何事: 它可能已停用,也同样可能是尚未被用到的编号。注释记录了哪些编号已停用,以及(在有记录的情况下)各自曾指代什么,因此一个既不对应任何行也不对应任何注释的代码,是本编译器从未发出过的代码。
短代码有意设计为不透明:四位数字本身不说明条件的任何信息,这是标识符足够短、便于念出、输入搜索或粘贴到报告中所付出的代价。下面的对应关系使其变得可用。编号从单一的递增序列中只分配一次,此后固定不变;它不说明所指条件的任何信息。因此短代码只是一个标识符,仅此而已——它的值不是一种分类,它本身以及你在表中可能注意到的任何分组,都不能指示条件位于何处或与什么相关。
此表没有类别列,这并非遗漏:类别是某次具体失败的属性,而非其背后条件的属性。 有些条件在构造上就属于某一类别。对于其他条件,类别取决于失败所涉及的实体种类,因此同一个这样的条件,一次针对 Aggregate 报告、一次针对 Release 报告时,每次携带的类别都不同——若在此处为条件写上单一的值,对第二类的每个条件都会是错的。
类别的讲解位于 error-translation.md——每个类别、其含义以及修复方法所在之处。类别和短代码回答的是关于同一次失败的不同问题:类别指出修复应落在哪个层面,短代码指出是哪个条件中止了构建。两者都无法从对方推导出来,因此各有一份公开的列表——这也是为什么一个没有可指明的编写层面的失败,仍然带有一个你可以在此查找的代码。
| 代码 | 条件 | 消息 |
|---|---|---|
E0001 | no-plugin-resolution-configured | cliplugin: no plugin resolver configured |
E0003 | malformed-attachment-requirement | malformed attachment requirement |
E0004 | overridden-annotation | annotation contribution overridden by an explicit value |
E0005 | policy-violation | policy violation |
E0006 | required-slot-unfilled | required attachment slot unfilled |
E0007 | selector-violation | selector violation |
E0008 | slot-selector-unsatisfied | attachment slot selector unsatisfied |
E0009 | pipeline-contract-violation | pipeline step typed-I/O contract violation |
E0010 | pipeline-step-failed | pipeline step failed |
E0011 | pipeline-target-absent | pipeline patch targets a document not present in the set |
E0012 | pipeline-target-opaque | pipeline patch targets an opaque (non-structured) unit |
E0013 | feature-type-mismatch | feature type mismatch between Aggregate and Release |
E0014 | inject-entry-ambiguous | inject entry carries both `value:` and `from:`; schema requires exactly one |
E0015 | uses-inject-forbidden | uses-edge inject dictates a delivery mechanism the socket does not permit |
E0016 | patch-test-operation-failed | jsonpatch: test operation failed |
E0017 | annotation-injection-rejected | 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 |
E0018 | policy-settings-invalid | policy attachment settings do not satisfy the plugin's declared settings schema |
E0019 | endpoint-requires-reference-form | endpoint requires form: reference |
E0020 | invalid-cron-schedule | schedule is not a valid cron expression |
E0021 | persistent-template-requires-stateful-form | persistentTemplate volume requires form: stateful |
E0022 | pipeline-patch-target-not-structured | pipeline PATCH target is not parseable structured YAML/JSON |
E0023 | reference-form-requires-endpoint | form: reference requires an endpoint |
E0024 | schedule-requires-scheduled-form | schedule requires form: scheduled |
E0025 | scheduled-form-requires-schedule | form: scheduled requires a schedule |
E0026 | artifact-content-mismatch | imported artifact content does not match the digest recorded for it in entity.lock |
E0027 | artifact-import-shape | artifacts $import: is not a bare-name artifact-library reference (<Library>#/artifacts/<entry>) |
E0028 | artifact-output-collision | artifacts output filename collision: two artifact outputs carry the same filename |
E0029 | artifact-pillar-not-declared | artifact template references a pillar the Recipe does not declare |
E0030 | artifact-library-entry-not-found | artifact-library import references a bundle not present in the ArtifactLibrary |
E0031 | artifact-library-not-found | artifact-library import references an ArtifactLibrary not present in the catalog |
E0032 | assembled-output-collision | assembled output collision: two contributors write the same output path |
E0033 | authored-assertion-failed | assertion failed |
E0034 | attachment-inject-key-collision | duplicate delivery key across attachment-inject and another inject source |
E0035 | boundary-assembly-not-provided | provider expected to assemble its dispatch group provides no boundary assembler |
E0036 | chart-name-mismatch | merged-path assembly has conflicting assembly-name annotation values |
E0037 | cross-provider-link-unsupported | cross-boundary link between endpoints rendered by different providers is not supported |
E0038 | derived-key-collision | derived name collision: one name is derived more than once in one key space |
E0039 | featurerecipe-template-invalid-field | FeatureRecipe template references a per-component-only field with executionScope: boundary |
E0040 | host-in-library-import | library $import: carries a registry host; reference the library by bare-name identity |
E0041 | instance-id-collision | multiple contributors share an instance ID at the same dispatch path |
E0042 | locals-forward-reference | locals entry references a sibling defined later in the same block |
E0043 | locals-unknown-reference | template references a key the locals block does not declare |
E0044 | mapping-entry-not-found | mapping-library import references an entry not present in the MappingLibrary |
E0045 | mapping-import-shape | valuesMapping $import: is not a bare-name mapping-library reference (<Library>#/mappings/<entry>) |
E0046 | mapping-library-not-found | mapping-library import references a MappingLibrary not present in the catalog |
E0047 | orphan-cross-boundary-link-placeholder | assembled output retains an unresolved cross-boundary link placeholder |
E0048 | path-collision | dispatch path produced multiple provider outputs |
E0049 | path-template-invalid-field | path template references a field not in the documented allowlist |
E0050 | pipeline-host-scope-unavailable | pipeline /host operation from a step with no host component |
E0051 | pipeline-patch-targets-unassembled-fragments | pipeline PATCH targets an assembler provider's pre-assembly fragments |
E0052 | pipeline-target-not-emitted | pipeline PATCH targets a document the node did not emit |
E0053 | plugin-provider-incompatible | pipeline plugin is not compatible with the rendering provider |
E0054 | provider-node-input-invalid | provider rejected node input |
E0055 | provides-contract-unfulfilled | Recipe or FeatureRecipe does not publish a provides key its abstract entity's schema.provides contract declares |
E0056 | provides-evaluation-failed | provides template evaluation failed |
E0057 | provides-self-containment | provides block references a root outside the self-contained set |
E0058 | render-nondeterministic | provider render is not deterministic |
E0059 | self-inject-key-collision | duplicate delivery key across self-inject and uses-inject |
E0060 | template-unknown-root | template references a root the render context does not define |
E0061 | unknown-provider | unknown provider |
E0062 | custom-mechanism-has-no-mapping | custom inject mechanism has no matching key in injectMapping output; add the mechanism's key to the Recipe injectMapping |
E0063 | workload-entry-not-found | workload-library import references an entry not present in the WorkloadLibrary |
E0064 | workload-import-shape | workload $import: is not a bare-name workload-library reference (<Library>#/workloads/<entry>) |
E0065 | workload-library-not-found | workload-library import references a WorkloadLibrary not present in the catalog |
E0066 | dangling-uses-target | uses edge target does not exist |
E0067 | active-toggle-not-a-boolean | active toggle did not resolve to a boolean |
E0068 | sub-aggregate-nesting-depth-exceeded | max sub-aggregate nesting depth exceeded |
E0069 | mutator-patch-rejected | mutator patch rejected |
E0070 | reexport-cycle | re-exported component alias forms a cycle |
E0071 | release-edge-retarget | release edge retargets a developer-declared edge |
E0072 | sub-aggregate-not-loadable | sub-aggregate load failed |
E0073 | sub-aggregate-name-collision | flattened node ID collision: rename one of the colliding instances so their flattened IDs differ |
E0074 | unbound-release-edge-config | release per-edge configuration has no edge to apply to |
E0075 | aggregate-not-in-canonical-form | aggregate reached topology un-normalized (non-empty root components alongside a synthesized default subsystem) |
E0076 | unplaced-sub-module | sub-module placed in no boundary: route it into a boundary under `aggregates`, or name its components there under `components` |
E0077 | uses-target-not-active | uses edge target was pruned because its active toggle resolved to false |
E0078 | wasm-nested-producer-consumption-denied | producer-consumption re-entry denied: a producer reached through the host may not issue a further producer-consumption call |
E0079 | wasm-command-set-mismatch | wasm: recorded command mirror does not match plugin describe() |
E0080 | wasm-contract-mismatch | wasm: entity contract claim does not match plugin describe() |
E0081 | wasm-diagnostic-severity-invalid | wasm: guest plugin returned a diagnostic whose severity the contract does not declare |
E0082 | wasm-guest-error | wasm: guest plugin reported an error |
E0083 | wasm-guest-panic | wasm: guest plugin panicked during call |
E0084 | wasm-host-function-set-mismatch | wasm: stamped host-function record does not match .wasm imports |
E0085 | wasm-manifest-rejected | wasm: plugin rejected by the sandbox |
E0086 | wasm-plugin-exited | wasm: plugin invoked proc_exit |
E0087 | wasm-plugin-type-mismatch | wasm: declared plugin type does not match plugin describe() |
E0088 | wasm-plugin-version-mismatch | wasm: entity metadata.version does not match plugin describe() |
E0089 | all-versions-retracted | every published version this reference could select has been withdrawn |
E0090 | ambiguous-importer-plugin | format is advertised by more than one importer plugin |
E0091 | ambiguous-parser-plugin | format is advertised by more than one parser plugin |
E0092 | ambiguous-provider-plugin | capability is served by more than one provider plugin; add a plugins.providers entry to select one |
E0093 | ambiguous-type-mapping | manifest maps multiple version-distinct keys to the same base type; the type-to-recipe lookup is ambiguous |
E0094 | duplicate-entity-identity | duplicate entity identity within a single catalog directory |
E0095 | malformed-recipe-reference | malformed recipe reference in a Manifest mapping value |
E0096 | manifest-implements-mismatch | manifest mapping entry's recipe spec.implements does not match the mapped component-type / feature-type key |
E0097 | no-importer-for-format | no importer plugin advertises the requested format |
E0098 | no-parser-for-format | no parser plugin advertises the requested format |
E0099 | no-recipe-resolved | no recipe resolved for component/feature instance: add an explicit Manifest mapping for its type |
E0100 | provider-binding-unsatisfied | plugins.providers entry names a plugin no provider-rendering plugin serving the capability matches |
E0101 | provider-version-unsatisfiable | no provider-rendering plugin version satisfies the recipe's provider version pin |
E0102 | plugin-reference-must-not-be-registry-qualified | wasm plugin reference must be the plugin coordinate identity (<pluginType>/<name>:<version>), not a registry-qualified or artifact path |
E0103 | unsatisfiable-entity-version | no catalog version satisfies the referenced version constraint |
E0104 | plugin-reference-must-be-scoped | wasm plugin reference must carry a pluginType scope (<pluginType>/<name>); an empty scope cannot bind to an OCI location |
E0105 | recipe-reference-must-be-scoped | recipe reference must be provider-scoped (<provider>/<name>); an empty provider cannot bind to an OCI location |
E0106 | invalid-library-ref | resolve: invalid library reference URI |
E0107 | version-selection-conflict | resolve: minimal version selection conflict — incompatible library version requirements |
E0108 | catalog-cannot-load-sub-aggregate-bodies | resolve: catalog lookup cannot load resolved sub-aggregate bodies |
E0109 | catalog-cannot-load-recipe-bodies | resolve: catalog lookup cannot load resolved recipe and plugin bodies |
E0110 | source-template-at-lock-time | resolve: source-template evaluation failure at lock time |
E0111 | source-template-not-parsable | resolve: source-template parse error |
E0112 | source-template-provides-ref | resolve: source-template references .provides (invalid reverse reference) |
E0113 | sub-aggregate-depth | resolve: sub-aggregate inclusion depth exceeded |
E0114 | unresolvable-uri | resolve: no entity in the catalog matches this URI |
E0115 | ambiguous-dispatch | compactform: ambiguous dispatch — $mode required |
E0116 | constraint-type-mismatch | compactform: constraint not valid for declared type |
E0117 | escape-content-invalid | compactform: $jsonschema content invalid |
E0118 | host-in-library-ref | compactform: cross-document $ref carries a registry host; reference the library by identity |
E0119 | reference-unresolvable | compactform: $ref unresolvable |
E0120 | unknown-keyword | compactform: unknown keyword |
E0121 | unresolved-schema-library-ref | compactform: cross-document $ref target not found |
E0122 | deprecated-entity | deprecation: build consumes a deprecated entity |
E0123 | not-docs-bundle | docscache: artifact is not a documentation bundle |
E0124 | page-not-found | docscache: page not found in documentation bundle |
E0125 | offline-egress | 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 |
E0126 | acquisition-disabled | externalinputs: acquisition is disabled for unpinned inputs |
E0127 | digest-mismatch | externalinputs: fetched bytes mismatch the pinned digest |
E0128 | scheme-not-allowed | externalinputs: URL scheme is not allowed |
E0129 | store-corrupt | externalinputs: store blob mismatches its pinned record |
E0130 | lockfile-drift | lockfile: out of date; it no longer matches what its Release resolves to |
E0131 | lockfile-invalid | lockfile: file failed schema validation |
E0132 | ambiguous-content-layer | oci: manifest has multiple layers of the expected content media type |
E0133 | cached-manifest-integrity | oci: cached manifest digest mismatch |
E0135 | fetch-integrity | oci: content digest mismatch |
E0136 | fetch-network-unreachable | oci: network unreachable |
E0137 | fetch-not-found | oci: artifact not found at remote source |
E0138 | fetch-unauthorized | oci: authentication required or failed |
E0139 | immutable-tag-conflict | oci: tag already published with different content |
E0140 | no-content-layer | oci: manifest has no layer of the expected content media type |
E0141 | oci-location-collision | oci: distinct catalog identities map to the same OCI repository location |
E0142 | referrer-discovery-unavailable | oci: referrer discovery could not be completed |
E0143 | unknown-entity-kind | oci: unknown entity kind for mediatype dispatch |
E0144 | signature-bundle-digest-mismatch | cached signature bundle does not match its recorded digest |
E0145 | plugin-entity-not-found | plugin reference is not a Plugin entity |
E0146 | reference-cycle | circular reference expansion |
E0147 | malformed-trust-policy | registrytrust: advertised trust config is malformed |
E0148 | no-trust-advertised | registrytrust: registry advertises no trust config |
E0149 | attachment-slot-near-miss | attachment name is a near miss for a declared slot |
E0150 | attachment-slot-shape | attachment does not conform to its declared slot shape |
E0151 | duplicate-boundary-component | component declared in more than one boundary: declare each component in exactly one boundary |
E0152 | duplicate-triad-identity | duplicate Aggregate/Manifest identity (metadata.name) in the Release directory |
E0153 | feature-merge-conflict | feature merge conflict: reconcile the Aggregate and Release declarations for the feature |
E0154 | internal-catalog-view-disagreement | the compiler's own views of the catalog disagree |
E0155 | inject-key-collision | duplicate delivery key across inject sources |
E0156 | invalid-inject-key | invalid inject key: the from-key must name a provides key its source publishes |
E0158 | invalid-parameter-ref | invalid parameter reference: check the {{ .parameters.* }} expression names a declared parameter and parses as a Go template |
E0160 | manifest-cross-binding-pillar-collision | manifest annotation bindings collide on same Feature path+pillar |
E0161 | manifest-reserved-prefix | manifest annotation binding uses reserved prefix |
E0162 | missing-required-feature | missing required feature: attach a Feature of the required type to the component |
E0163 | missing-required-socket | required uses socket not populated |
E0164 | parameter-contract-violation | parameter contract violated |
E0165 | parameter-missing | required parameter not supplied |
E0167 | provides-key-not-declared | Recipe publishes a provides key its Component does not declare |
E0168 | schema-conformance | authored pillar does not conform to its declared schema |
E0169 | self-inject-forbidden | self-inject on component without spec.inject allowlist |
E0170 | triad-ref-unresolvable | aggregate/manifest reference unresolvable |
E0171 | unknown-uses-socket | 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 |
E0172 | release-not-in-canonical-form | release reached resolve un-normalized (non-empty root components alongside a synthesized default boundary) |
E0173 | unread-parameter | declared parameter is read by no reference in the Aggregate |
E0174 | uses-socket-near-miss | uses socket name is a near miss for a declared socket |
E0175 | document-not-loadable | file load failed: the file could not be read, or its bytes did not parse |
E0176 | keyless-signing-requires-network | signing: keyless signing requires a live identity provider, Fulcio, and Rekor |
E0177 | no-signature-found | signing: no signature found for an artifact that requires one |
E0178 | no-trusted-identities | signing: keyless verification requires at least one trusted identity |
E0179 | signature-invalid | signing: signature does not verify |
E0180 | signature-verification-failed | signing: signature bundle does not verify |
E0181 | signing-policy-requires-signature | signing: signing policy requires a signature for this artifact kind; refusing to push unsigned content |
E0182 | trust-root-not-loadable | signing: cannot load pinned trust root |
E0183 | unsigned-push-refused | signing: registry requires signatures; refusing to push unsigned content |
E0184 | unsupported-key | signing: unsupported held-key type |
E0185 | untrusted-identity | signing: signature identity is not trusted for this registry |
E0186 | unknown-source-kind | no source adapter serves the source kind |
E0187 | empty-workspace-root | cacheslot: empty workspaceRoot |
E0188 | artifact-entry-shape | artifacts entry: shape must be a string scalar or {$import: <local-path>} |
E0189 | artifact-library-entry-shape | artifactlibrary: entry must be a mapping of filename to a string body |
E0190 | forbidden-keyword | schemalibrary: forbidden JSON Schema keyword |
E0191 | mapping-entry-not-scalar | mappinglibrary: entry body must be a string scalar |
E0192 | document-nesting-depth-exceeded | a document nests too many levels deep |
E0193 | parameters-shape | parameters: shape must be an inline object or {$import: <local-path>} |
E0194 | template-not-found | schemalibrary: template not found |
E0195 | template-param-missing | schemalibrary: template parameter missing |
E0196 | template-param-type-mismatch | schemalibrary: template parameter type mismatch |
E0197 | values-mapping-shape | valuesmapping: shape must be a string scalar or {$import: <path-or-library-identity>} |
E0198 | well-known-annotation-scope | wellKnownAnnotations: a key is declared at a scope the provider's contract does not render |
E0199 | workload-entry-not-scalar | workloadlibrary: entry body must be a string scalar |
E0200 | workload-template-shape | workload: shape must be a string scalar or {$import: <path-or-library-identity>} |
E0201 | assertion-name-collision | assertion name declared twice across the extends chain |
E0202 | cyclic-extension | cyclic extends chain |
E0204 | feature-recipe-values-mapping-requires-source | FeatureRecipe: valuesMapping requires source |
E0205 | extends-merge-failed | inheritance merge failed |
E0207 | recipe-output-component-label-collision | recipe output-component-labels constraint: key is also declared in outputLabels |
E0208 | recipe-output-label-reserved-namespace | recipe output-labels constraint: key uses a reserved namespace |
E0209 | recipe-values-mapping-requires-source | Recipe: valuesMapping requires source |
E0210 | recipe-no-input-kind | Recipe: at least one input kind required |
E0211 | recipe-filename-collision-across-input-kinds | filename collision across input kinds: two input-kind blocks produced a file under one output name |
E0212 | slot-not-referenceable | workload attachment slot is not referenceable |
E0213 | workload-features-schema | workload featuresSchema cross-check failed |
E0214 | workload-not-valid | workload validation failed |
E0215 | entity-envelope-invalid | document envelope validation failed |
E0216 | schema-extension-evaluation-failed | validator/jsonschema: x-aggrega extension evaluation failed |
E0218 | schema-not-resolvable | validator/jsonschema: schema resolution failed |
E0220 | extends-chain-too-deep | extends chain exceeds maximum depth |
E0221 | schema-merge-input-invalid | merger: invalid merge input |
E0222 | ambiguous-registry-alias | registry alias matches more than one host |
E0223 | capability-on-cross-cutting-socket | a cross-cutting socket is bound by capability but attaches by uri |
E0224 | workspace-config-invalid | workspace configuration is invalid |
E0225 | duplicate-provider-target | capability is bound to more than one provider plugin |
E0226 | duplicate-registry-alias | registry alias is already used by another host |
E0227 | governance-role-invalid | a governance attachment declares no role or an unknown role |
E0228 | inert-field-on-provider-socket | a provider socket binding sets a field with no referent on that socket |
E0229 | position-out-of-range | position out of range |
E0246 | verdict-plugin-trust-mismatch | the digest recorded as trusted for this plugin does not match the digest its cached manifest reports |
E0247 | verdict-attachment-not-configured | a plugin recorded as trusted for an accept-or-reject verdict is no longer attached at any verdict role |
E0248 | wasm-output-shape | wasm: guest plugin returned an output that is not the shape the socket reads |
E0250 | nest-segment-not-one-directory | provider named a directory for each contributor's own sub-directory that is not a single directory name |
E0251 | recipe-source-is-empty | recipe source is an empty string, which names neither sourceless mode nor sourced mode |
E0252 | artifact-library-file-escapes-key | artifact-library bundle file name does not name a file of its own beneath the artifacts key its output is nested under |
E0253 | annotation-binding-target-unresolved | annotation binding does not resolve against its target Feature |
E0254 | annotation-subkey-not-conforming | annotation subkey does not conform to the target Feature's schema at the routed pillar |
E0255 | annotation-side-pillar-mismatch | annotation routes through a pillar its authoring side may not use |
E0256 | annotation-binding-pillar-overlap | annotation binding declares one path in both pillar lists |
E0257 | schema-contract-compile-failure | 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 |
E0259 | boundary-scope-attachment-not-declared-at-a-boundary | attachment binds a FeatureRecipe with executionScope: boundary and no boundary holding the component declares it |
E0260 | unplaced-component | component placed in no boundary: name it under a boundary's `components`, or place the sub-module that contributes it under `aggregates` |
E0261 | unresolved-boundary-component | boundary names a component the composition does not hold: correct the name, or remove the entry |
E0262 | unusable-component-identity | component identity cannot be the name its emitted resources are stamped with: rename the component |
E0263 | component-identity-target-refuses | the target will not accept a name derived from this component's authored identity: rename the component |
E0264 | provider-refused-every-component-identity | provider guest never accepted a component identity the compiler composed for it |
E0265 | unsupported-input-kind | provider does not support the node's input kind |
E0266 | unusable-schema-import | a schema `$import:` could not be applied |
E0267 | unknown-schema-pillar | a schema block declares a key that names no data pillar |
E0268 | pipeline-patch-unit-not-carved | reassemble names a patched unit token the carve did not produce; a conforming codec carves and reassembles a file under the same tokens |
E0269 | provider-render-duplicate-path | provider guest returned two output files under one path; a conforming guest returns each output path at most once |
E0270 | link-patch-file-not-emitted | 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 |
E0271 | pipeline-emit-file-absent | emit_file side effect carries no file; a conforming emit_file side effect carries a file with its path and content |
E0272 | pipeline-side-effect-kind-undefined | side effect declares a kind the plugin contract does not define; a conforming side effect declares emit_file or emit_crd |
E0273 | rendered-name-unavailable | 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 |
E0274 | verdict-plugin-identity-changed | the plugin identity recorded as trusted no longer matches what this resolution reports |
E0275 | edit-refused-invalid-result | the edit was refused because the resulting document would not be valid, and nothing was written |
E0276 | schema-evolution | the version being published changes the published predecessor in a way the documented evolution rubric objects to |
E0277 | annotation-prefix | an annotation key on the entity uses a prefix the platform reserves |
E0278 | name-shape | the entity's name does not follow the documented name shape for its kind |
E0279 | dynamic-refs | a schema in the entity uses a dynamic reference construct that cross-document reference resolution cannot follow |
E0280 | id-overrides | a schema in the entity declares an identifier of its own, where the platform owns that schema's identity |
E0281 | category-matches-directory | the entity's category label does not match the category directory the entity is filed under |
E0282 | x-aggrega-discouragement | the entity writes an Aggrega schema extension directly into schema content instead of declaring it under usesSchema or featuresSchema |
E0283 | plugin-default-limits | the Plugin entity declares no runtime resource cap of its own, so the platform defaults apply |
E0284 | secret-slot-declares-sensitive | an attachment slot admits only secret material and does not declare that it handles it |
E0285 | provides-declared-by-component | the Recipe publishes a provides key the Component it implements does not declare, so a consumer wiring that key is refused |
E0286 | publish-bump-below-classification | the version bump being published is smaller than the evolution check's classification of the change requires |
E0287 | import-halting-diagnostic | the importer reported a diagnostic that stops the import, so the source was not fully turned into draft authoring files |
E0288 | plugin-cannot-express-input | a plugin has no expression for a construct this build declares |
E0289 | plugin-required-input-unresolved | a plugin could not resolve something it requires to exactly one value |
E0290 | plugin-output-name-collision | two things a plugin produced occupy one name in its output |
E0291 | plugin-value-not-representable | a plugin has no representation for a value it was given |
E0292 | plugin-failure-unclassified | a plugin reported a failure that none of the declared kinds names |
E0293 | wasm-guest-condition-undeclared | wasm: guest plugin named a condition the socket does not declare |
E0294 | subsystem-component-identity-collision | components in different subsystems take the same identity: rename one of them, since a subsystem contributes nothing to a component's identity |
E0295 | library-reference-whitespace | library reference: a reference to a library entry carries no whitespace or line break |
E0296 | release-chain-composes-both-routing-keys | release extends chain composes both named boundaries and top-level components: declare one routing shape across the chain, never both |
E0297 | inherited-boundary-directory-is-literal | inherited boundary directory carries no template variable, so it resolves to the path the extended Release writes to |
E0298 | bundle-no-entity-document | oci: published bundle carries no entity document |
E0299 | bundle-ambiguous-entity-document | oci: published bundle carries more than one entity document |
E0300 | bundle-unreadable | oci: published bundle cannot be unpacked |
E0301 | published-artifact-not-an-entity | oci: published artifact is not an entity document |
E0302 | entity-not-pinned | an input the entity reads has no pin recorded for it in the entity.lock beside it |
E0303 | entity-shares-its-directory | the entity shares its directory with another entity, and an entity of its kind has a directory of its own |
E0304 | content-outside-entity-directory | a path names content outside the entity's own directory |
E0305 | local-source-content-mismatch | the files of the entity's local source do not match the pins recorded for them in entity.lock |
E0306 | plugin-artifact-not-found | plugin artifact not found on this machine |
E0307 | cache-location-outside-cache | a value a cache location is built from would place cached files outside the place it names in the cache |
E0308 | conflicting-features-reach-one-component | a Feature reaches a component alongside a Feature it declares a conflict with |
E0309 | symbolic-link-in-entity-files | a symbolic link sits among the files an entity carries |
E0310 | offline-registration-without-trust-policy | 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>` |
E0311 | malformed-version-pin | reference carries a malformed version pin |
E0312 | colon-in-provider-binding-capability | a provider socket binding names a capability containing a colon, which no Recipe can select |
E0313 | provider-binding-capability-unserved | plugins.providers entry names a capability no provider-rendering plugin the build reads serves |
E0314 | plugin-built-from-uncommitted-changes | plugin was built from a working tree with uncommitted changes, so no commit reproduces the version it reports |
E0315 | connection-attachment-slot-undeclared | a connection carries an attachment under a name its socket declares no slot for |
E0316 | connection-attachment-written-off-its-connection | a Release attachment takes the name of an attachment one of a component's connections carries |
E0317 | release-connection-attachment-untyped | a Release connection attachment names no Feature type, and the type is required for an attachment only the Release makes |
E0318 | attachment-inject-mapping-key-collision | duplicate delivery key across two attachments: an attachment's FeatureRecipe writes a delivery key another attachment already delivered |
E0319 | duplicate-connection-alias | connection alias is already used by another connection of the same component |
E0320 | write-leads-out-of-workspace | a path this operation writes or deletes leads through a link out of the directory it must stay inside |
E0321 | read-leads-out-of-workspace | a file this operation reads leads through a link out of the directory it must stay inside |
E0323 | caller-render-facts-not-declared | template reads its callers' render facts, but the FeatureRecipe does not set readsCallerRenderFacts |
E0324 | reference-leads-out-of-workspace | a reference a document makes to another file leads out of the directory it must stay inside |
E0325 | provider-render-fact-not-list | 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 |
E0326 | pipeline-step-reads-caller-render-facts | 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 |
E0327 | index-of-absent-map-key | template indexes a map with a key the map does not hold |
E0328 | misnamed-slot-fill | attachment written under a name no slot declares fits a slot its component leaves empty |
E0329 | connection-credential-matches-target-key | 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 | mixed-signing-credentials | signing: the references named together need different signing credentials, so nothing was signed |
E0331 | signature-not-recorded | signing: no verified signature is recorded for an artifact that requires one |
E0332 | signature-for-another-artifact | signing: the recorded signature was made for a different artifact |
E0333 | recorded-signature-out-of-date | signing: a recorded signature is not the one a pull would record |
E0334 | omit-matched-nothing | an omits entry left out nothing the source rendered |
E0335 | unsupported-omits | provider does not support omits |
E0336 | omit-report-mismatch | a provider's omitted counts do not match the omits entries it was handed |
E0337 | importer-version-unsatisfiable | no importer plugin version satisfies the plugins.importer entry's version pin |
E0338 | duplicate-importer-attachment | importer is attached by more than one plugins.importer entry |
E0339 | ambiguous-import-format | more than one importer recognises the source |
E0340 | name-windows-cannot-hold | a name this operation writes holds a path segment Windows cannot hold as written |
E0341 | importer-declares-no-file-patterns | the importer serving the source's format declares no file patterns, so it reads one file and cannot read a directory |
E0342 | import-directory-matched-nothing | no file in the directory matches the file patterns the importer serving the source's format declares |
E0343 | import-source-name-collision | a file read from the directory and a file named in the importer's `with.sources` have the same name |
E0344 | windows-unusable-entry | an entry this publication carries cannot be used on Windows |
E0345 | duplicate-container-environment-variable | a container declares one environment variable twice |
E0346 | metrics-credential-annotation-matches-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 |
E0347 | target-render-facts-not-declared | template reads the render facts of a component its host is wired to, but the FeatureRecipe does not set readsTargetRenderFacts |
E0348 | pipeline-step-reads-target-render-facts | 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 |
E0349 | import-target-unbound | no Recipe in the workspace's catalog binds to the capability the import's target names |
E0350 | unrecognised-import-format | no importer recognises the source |
E0351 | unsupported-boundary-artifacts | provider does not support boundary artifacts |
E0352 | boundary-directory-not-beneath-output-root | boundary output directory does not name a directory beneath the output root |
E0353 | boundary-feature-name-not-a-directory | boundary-level Feature instance name is not a directory name |
E0354 | cross-boundary-link-value-not-copied | a template does more than copy a value it reads off a cross-boundary link |
E0355 | inject-delivery-shape | inject delivery: shape must be a list of entries, each `in:` with exactly one of `from:` or `value:` |
E0356 | suspend-requires-scheduled-form | suspend requires form: scheduled |
E0357 | name-mapping-matched-nothing | a Manifest name mapping's key names no component instance or attachment in this build, so the entry binds nothing |
E0358 | uses-target-not-exported | uses edge target names a component its module does not export |
E0359 | source-adapter-not-registered | no source adapter is registered in this program for the source kind |
E0360 | netrc-file-unreadable | the netrc file could not be read |
E0361 | source-url-carries-credential | the source URL carries a credential |
E0362 | uses-inject-value | inject entry on a connection carries `value:`; a connection delivers the target's published keys, each named with `from:` |
E0363 | annotation-subkey-not-bound | annotation subkey is not routed by the annotation's binding |
E0364 | value-template-execution-failed | a value template failed while it ran |
E0365 | boundary-contribution-not-assembled | boundary-level Feature's output is routed to a dispatch path nothing assembles |
E0366 | inject-mapping-output-not-parsable | FeatureRecipe injectMapping output could not be read as a dictionary of deliveries |
E0367 | annotation-scalar-not-routable | a scalar annotation value does not route to exactly one path of its binding |
E0368 | inject-mapping-output-key-not-delivered | FeatureRecipe injectMapping output writes a key no delivery mechanism of the host reads |
E0369 | absent-path-read-and-iterated | template reads a path as a value and iterates it, and the data holds nothing at that path |
E0370 | duplicate-pipeline-step-id | a pipeline declares one step id twice |
E0371 | unknown-catalog-document-kind | catalog document declares a kind a catalog does not hold |
E0372 | attachment-inject-value | 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 |
E0373 | retired-api-version | a document declares an API version this compiler no longer reads |
E0374 | retired-abi-version | a plugin declares a plugin ABI version this compiler no longer speaks |
E0375 | retired-media-type | oci: artifact carries a media type this compiler no longer reads |
E0376 | no-answer-in-time | egress: the server did not answer in time |
E0377 | repository-listing-too-long | registry: the repository listing did not end in time |
E0378 | registry-too-busy | oci: the registry kept asking to slow down |
E0002已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。它曾指代在检查图的静态契约时失败的目录查找——这是编译器的故障,而非编写的文档中的故障——而当构建解析的组件类型在其当时读取的目录中没有条目时所引发的条件,现在负责报告这一状态,其代码为E0154。E0134已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。它曾指代一个可发布实体,其目录未以该实体声明的版本命名;发布不检查目录名称,而当某实体的种类拥有独立目录、该实体却与另一实体共用目录时所引发的条件是E0303。E0157已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。它曾指代不符合编写名称模式的 Aggregate 键——组件、功能、子系统或嵌套模块的实例名称。所有这些键的层面都由 Aggregate schema 约束为同样的拼写,该 schema 会在验证文档外壳时拒绝该文档,并报告出错的键及其行号和列号;该条件的代码为E0215。E0159已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。它曾指代一个目标引用,其以点分隔的各段并非全部符合实例名称模式;在该条件被撤销之前,没有任何构建报告过它。E0166已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。它曾指代 Release 的parameters: { $import: … }所指向的文件无法读取或其字节无法解析的情况;无论路径写在何处,不产生文档的文件都属于同一个条件,其代码为E0175。E0203已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。它曾指代一个使用eval能力、却声明了源、values 覆盖层、workload 或 artifacts 的 FeatureRecipe;该能力已被撤销,现在也没有任何东西报告这种状态。E0206已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。它曾指代一个使用eval能力、却声明了源、workload、artifacts 或 values 覆盖层的 Recipe;该能力已被撤销,而一个未声明其中任何一项的 Recipe 在任何能力上都会以E0210被拒绝。E0217已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。它曾指代无法针对某个特定字段报告的 schema 验证失败;在该条件被撤销之前,没有任何构建报告过它。E0219已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。它曾指代循环的extends链,由独立于 schema 合并组合步骤的链遍历报告;单次链遍历会报告所有循环链,其代码为E0202。E0230已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。该编号所指的条件已被撤销,没有任何构建报告它。E0231已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。该编号所指的条件已被撤销,没有任何构建报告它。E0232已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。该编号所指的条件已被撤销,没有任何构建报告它。E0233已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。该编号所指的条件已被撤销,没有任何构建报告它。E0234已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。它指的是通过 compose provider 渲染时报告的、为空字符串的 Recipe 源;现在由一个涵盖所有 provider 的条件报告该情况,其代码为E0251。E0235已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。此编号所指的条件已被撤销,没有任何构建会报告它。E0236已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。此编号所指的条件已被撤销,没有任何构建会报告它。E0237已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。此编号所指的条件已被撤销,没有任何构建会报告它。E0238已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。此编号所指的条件已被撤销,没有任何构建会报告它。E0239已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。此编号所指的条件已被撤销,没有任何构建会报告它。E0240已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。此编号所指的条件已被撤销,没有任何构建会报告它。E0241已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。此编号所指的条件已被撤销,没有任何构建会报告它。E0242已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。它指的是通过 Helm provider 渲染时报告的、为空字符串的 Recipe 源;现在由一个涵盖所有 provider 的条件报告该情况,其代码为E0251。E0243已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。此编号所指的条件已被撤销,没有任何构建会报告它。E0244已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。此编号所指的条件已被撤销,没有任何构建会报告它。E0245已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。此编号所指的条件已被撤销,没有任何构建会报告它。E0249已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。此编号所指的条件已被撤销,没有任何构建会报告它。E0258已停用:现在没有任何内容报告它,且该编号永远不会分配给其他条件。此编号所指的条件已被撤销,没有任何构建会报告它。E0322已停用:现在不再有任何东西报告它,该编号也永远不会分配给其他条件。它曾指代挂载在边界上的 Feature 为某个 component 的环境计算、而所在键已由另一个挂载交付的值。挂载在边界上的 Feature 只能通过其 FeatureRecipe 的 injectMapping 向 component 交付,而写入另一个挂载已交付的键的映射会以E0318报告。
匹配指南
errors.Is 谓词会遍历包装链,因此即使错误在返回给你的途中被包装了多次,哨兵匹配仍然有效。请针对导出函数返回的错误进行匹配:
package release
import ( "errors" "fmt"
"github.com/aggrega-ai/aggrega-cli/pkg/resolver" "github.com/aggrega-ai/aggrega-cli/pkg/validator/envelope")
// Load reads a Release and reports the distinct failures a caller handles// differently.func Load(path string) error { _, err := resolver.LoadRelease(path) switch { case errors.Is(err, envelope.ErrEntityEnvelope()): return fmt.Errorf("%s is not a Release: %w", path, err) case errors.Is(err, resolver.ErrYAMLLoad()): return fmt.Errorf("%s could not be read as YAML: %w", path, err) case err != nil: return err } return nil}没有可运行整个构建的导出入口点,因此 errors.Is 匹配适用于直接调用这些包的代码。若要根据构建结果控制 CI,请运行 aggrega build,并读取其退出状态和诊断信息:诊断的消息文本收录在 fatal-halts.md 中,其类别收录在 error-translation.md 中,而其方括号开头中的短代码可在本页的所有条件的表格中查到。
之所以存在两种控制路径,是因为这三种标识符能触及的范围不同。用 Go 编写的控制逻辑会链接这些包、匹配哨兵,并能从它持有的任何错误中读取任一代码。围绕命令编写的控制逻辑只有退出状态和打印的文本——而打印的文本会指明条件,因为短代码位于方括号开头中。因此这类控制逻辑应以该短代码为依据,而不是以消息措辞为依据;以消息为索引的视图仍是从已有措辞反查的途径。在 Go 中匹配哨兵;围绕命令时以短代码为依据;在客户端支持该协议时,从结构化诊断中读取描述性代码。
在不同包中声明、短名称相同的哨兵是不同的条件,而不是同一条件的两种写法:errors.Is 按身份区分它们,因此与其中一个匹配并不会与另一个匹配。表格中特别指出的重新导出是例外,之所以特别指出,正是因为这是两个名称确实匹配的情况。请针对表格所列包中的名称进行匹配,并将单独的短名称视为有歧义。
面向用户的诊断目录(构建中止时开发者在终端中看到的消息),请参见 fatal-halts.md。建议性警告目录(不会中止的 warning:、lint: 和 notice: 输出),请参见 warnings.md。类别前缀分类([DEVELOPER_ERROR] / [OPS_ERROR] / [CATALOG_ERROR] / [TRANSLATION_ERROR] / [FETCH_ERROR] / [POLICY_ERROR] / [TRUST_ERROR]),请参见 error-translation.md。