Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
perf(noema): parallelize bounded changed-file evidence fetches #1011
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
perf(noema): parallelize bounded changed-file evidence fetches #1011
Changes from all commits
d0372f00d1e699b333b6f7212d9b47770c2a0128179349275File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
도달할 수 없는 분기입니다. 제거하세요.
343-344행에서
paths가 비어 있으면 함수는 이미 반환합니다.MAX_CONTEXT_FILES는 12이므로paths[:MAX_CONTEXT_FILES]는 항상 원소를 1개 이상 가집니다. 따라서if not target_paths분기는 실행되지 않습니다.이 분기는 테스트로 도달할 수 없습니다. 코딩 가이드라인은
scripts/ci/코드에 100% 테스트 커버리지를 요구합니다. 분기를 제거하면 커버리지 요구를 만족할 수 있습니다.♻️ 제안 수정
As per coding guidelines: "Maintain 100% test coverage and 100% interrogate docstring coverage for code under
scripts/ci/".📝 Committable suggestion
🤖 Prompt for AI Agents
Source: Coding guidelines
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: ContextualWisdomLab/.github
Length of output: 536
🏁 Script executed:
Repository: ContextualWisdomLab/.github
Length of output: 4896
🏁 Script executed:
Repository: ContextualWisdomLab/.github
Length of output: 2737
🌐 Web query:
interrogate Python documentation ignore-nested-functions default nested functions docstring coverage💡 Result:
In Python documentation generation and static analysis, there is no standardized, universal "ignore-nested-functions" setting across all tools. Support for documenting or ignoring nested (inner) functions varies significantly by implementation. Standard Library pydoc The standard library pydoc module does not natively document nested functions [1][2]. It is designed to document modules, classes, and functions at the module level [3][4]. Because nested functions are local to the scope in which they are defined, they are typically not accessible to pydoc's introspection mechanism [2]. Sphinx Autodoc Sphinx's autodoc extension generally ignores nested functions by design, as it focuses on generating reference manuals for public APIs [5]. There is no official configuration flag to force autodoc to include them, and the tool often ignores them during its parsing phase [5]. Users requiring custom behavior often use the autodoc-skip-member event in conf.py to programmatically include or exclude members, though this is primarily intended for skipping, not necessarily for exposing non-exported nested objects [6]. Third-Party Tools and Coverage Some third-party docstring coverage and generation tools provide explicit configuration to ignore or handle nested functions: - gpt4docstrings: This tool includes an explicit command-line option, --ignore-nested-functions (-n), to ignore nested functions and methods during its docstring processing [7][8]. - docsig: This tool (a docstring checker) provides a configuration option to check nested functions and classes, which is disabled by default [9]. When enabled, it verifies the existence and quality of docstrings for nested objects [9]. In summary, standard tools like pydoc and Sphinx implicitly ignore nested functions because they are not part of the top-level public interface [2][5]. Specialized linters and coverage tools often allow you to toggle this behavior explicitly [9][7].
Citations:
🏁 Script executed:
Repository: ContextualWisdomLab/.github
Length of output: 632
🌐 Web query:
site:interrogate.readthedocs.io ignore-nested-functions interrogate💡 Result:
In the context of the interrogate tool, which is used for checking Python docstring coverage, --ignore-nested-functions (or the shorthand -n) is a command-line option that instructs the tool to exclude nested functions and methods from the coverage analysis [1][2]. By default, this option is set to False, meaning interrogate will normally include nested functions and methods in its docstring coverage assessment [1][3]. This option can also be configured in a project's pyproject.toml file by setting ignore-nested-functions = true under the [tool.interrogate] section [1][4].
Citations:
🌐 Web query:
site:github.com/econchill/interrogate "ignore-nested-functions"💡 Result:
Search results found no direct match in
econchill/interrogate. The option appears in other projects’ Interrogate configuration, e.g.ignore-nested-functions = true. (github.com)Citations:
중첩 함수
_fetch_file_content에 docstring을 추가하세요.pyproject.toml에서ignore-nested-functions를 활성화하지 않았습니다. 기본값은false이므로 이 함수는 100% 문서화 커버리지 대상입니다.🤖 Prompt for AI Agents
Source: Coding guidelines
Uh oh!
There was an error while loading. Please reload this page.