Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Stencil cache proto schema even after schema is deleted

未关闭
#180 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
go

调研方向

Start by reproducing the DELETE, POST, and GET requests against multiple Stencil pods behind the service, then inspect the schema-serving and cache entry points. Done means a deleted schema does not reappear after recreation, including when requests reach different pods, without requiring a rolling restart.

由索引模型根据 Issue 内容生成。

描述

Describe the bug

When I delete a proto-schema

curl -X DELETE http://stencil:8080/v1beta1/namespaces/my-proto/schemas/internal

and recreate the schema

buf build -v --path "internal/src" --as-file-descriptor-set -o "internal/generated/out.desc"
curl --fail-with-body -X POST http://stencil:8080/v1beta1/namespaces/pixxel-proto/schemas/internal --data-binary "@internal/generated/out.desc"

The old schema is still present when getting this schema.

curl http://stencil:8080/v1beta1/namespaces/pixxel-proto/schemas/internal -o any.desc
protoc --decode_raw < any.desc. (the output here still shows the old deleted schema)

Here the stencil URL http://stencil:8080/ is a Service which loads balances across multiple stencil pods.

This problem is solved after doing a rolling restart of Stencil pods.

Expected behavior

Stencil appears to be caching the schema even after the pods are deleted. The cache is local to the pod and not shared across all pods, hence old cache is appearing.

主要语言
Go
星标
236
派生
42
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

raystack/stencil 的其他 Issue

查看 raystack/stencil 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。