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

Indexing gap: sql/wisdom_cs

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

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
sql
领域
devtools

调研方向

Reproduce with the reduced snippet: save the QUALIFY ROW_NUMBER() OVER (...) = 1 query as a .sql file, index it, and check index_status with diagnostics: full for parse_partial ranges. The payload does not name the SQL grammar or extraction files, so locate them first. Done when the snippet and sql/wisdom_cs/dim_domain_crm.sql lines 51-54 index without a partial flag, or the remaining gap is explained.

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

描述

codebase-memory-mcp reports a best-effort indexing gap for project Users-gautamparab-Downloads-wisdomai_cs_large. index_status (diagnostics: full) lists sql/wisdom_cs/dim_domain_crm.sql under parse_partial with error ranges 51-52,54-54 (1-based). The rest of sql/wisdom_cs is not flagged. Status was ready (15,688 nodes / 49,797 edges).

The flagged lines are a BigQuery QUALIFY filter on a window function. Lines 51–52 are QUALIFY ROW_NUMBER() OVER ( and the PARTITION BY line. Line 54 is the closing ) = 1. The ORDER BY ... DESC NULLS LAST line between them (line 53) is not in the error ranges, so the parser recovers the inner order-by and fails again on the comparison after the window.

QUALIFY is valid BigQuery (and Snowflake) SQL. It is not in the core SQL grammar, so the tree-sitter parse records error nodes there. The file is still indexed; symbols inside those ranges may be missing from the graph.

Reduced stand-in for the flagged construct (generic names, not the warehouse view):

SELECT id
FROM items
QUALIFY ROW_NUMBER() OVER (
  PARTITION BY id
  ORDER BY updated_at DESC NULLS LAST, id DESC
) = 1;

Environment: codebase-memory-mcp dev on macOS Apple Silicon (Darwin 25.6.0).

主要语言
C
星标
45.8k
派生
3.8k
平均合并
3 天 4 小时
30 天内合并 PR
208

环境准备

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

从这里开始

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

DeusData/codebase-memory-mcp 的其他 Issue

查看 DeusData/codebase-memory-mcp 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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