missing revalidation?

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
go
领域
backend

调研方向

Start in cache/cache.go at the linked code around line 126 and trace how fetch() releases and reacquires the lock. Check which cache operations can run during the fetch and whether any can make the pending insert invalid. Done means establishing whether revalidation is needed and, if so, defining the behavior before making a change.

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

描述

Hello, it appears a lock is dropped before a potentially long-running operation, and then reacquired before continuing. This is fine. However, it appears that there is no confirmation that the update is still legal after reacquiring the lock.

Are there any operations that could be performed while fetch() is executing that would invalidate the cache in such a way that the insert should be failed instead of continuing?

https://github.com/juju/utils/blob/bf9cc5bdd62dabc40b7f634b39a5e2dc44d44c45/cache/cache.go#L126

Thanks

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

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

juju/utils 的其他 Issue

查看 juju/utils 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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