[Help] Do non-fatal errors get unfailed?

未关闭
#5,159 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
postgres, rust
领域
backend, databases

调研方向

从 store/postgres/src/deployment_store.rs 中被引用的部分开始，尤其是处理致命错误和非致命错误的行。追踪 subgraph 失败状态和 non_fatal_errors 向量是如何被持久化和清除的，然后确定观察到的行为是有意为之还是一个 bug，以及数据库处于何种状态（如果存在这样的状态）时可以预测不会失败。

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

描述

enhancement ops Stale
Description

I'm trying to better understand how graph node handles subgraph failures and I learned that graph node automatically unfails subgraphs on initialization and during other aspects of the subgraph lifetime.

Based on this comment and this comment it seems that only fatal errors are unfailed while non-fatal errors persist. Is that correct?

Is there a way to query the database and know if a subgraph will be unfailed at some point in the future or is that managed entirely through in memory?

Ninja edit: it seems that non-fatal errors can get wiped too eg here and here where None is passed to the non_fatal_errors vector - might this be a bug?

Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.

No response

Some information to help us out
  • Tick this box if you plan on implementing this feature yourself.
  • I have searched the issue tracker to make sure this issue is not a duplicate.
主要语言
Rust
星标
3.2k
派生
1.1k
平均合并
4 天 1 小时
30 天内合并 PR
1

贡献指南

打开贡献指南

从这里开始

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

graphprotocol/graph-node 的其他 Issue

查看 graphprotocol/graph-node 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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