示例
Configure zap.Config OutputPaths with custom URI schemes via zap.RegisterSink and verify unregistered scheme rejection and URL parsing
sha256:46df4736d445e122bed613d66d9074610072b234cffa56ec4013cd41d2affee5
PUBLISHED
L3_CONTRACT_PASS
MIT-0
执行证据
分开显示声明环境和签名验证运行,明确样本的证明范围。
证据依据签名契约通过
验证回执1
验证级别L3_CONTRACT_PASS
声明的环境
- 执行上下文
- go
- 操作系统
- linux
- 架构
- x64
- 运行时
- go
- 语言
- go
- 包管理器
- go
验证运行环境
- 执行上下文
- go 1.26
- 操作系统
- linux alpine · musl
- 架构
- x64
- 运行时
- go 1.26
- 语言
- go
- 包管理器
- go
- 执行方式
- container · docker
CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17
案例
- 目标
- Configure zap.Config OutputPaths with custom URI schemes via zap.RegisterSink and verify unregistered scheme rejection and URL parsing HOW
- 包
-
go.uber.org/zap 1.27.0
- 环境
- go
- 创建时间
- 2026-08-17T11:48:38Z
常见的想当然
zap.Config.Build automatically resolves unregistered URI schemes to file paths or creates default sink wrappers for custom protocol schemes
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- zap.Config.Build fails with a 'no sink found for scheme' error when OutputPaths contains a URI scheme that has not been registered via zap.RegisterSink.
- zap.RegisterSink registers a custom URL scheme factory and rejects empty schemes, duplicate scheme registrations, and the reserved 'file' scheme.
- zap.Config.Build parses custom OutputPaths URIs into url.URL structures with query parameters, passes them to the registered sink factory, and routes structured log entries to the sink.
文件
- NOTES.md
- csx.json
- go.mod
- go.sum
- zap_config_sink_test.go
下载源代码构件 (tar.gz)
原始种子者
csx-seed
验证回执
- go 1.26 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9