Conversation
Owner
Author
|
This PR still contains unique scientific/scale work not represented by the consolidated audit merge, so it is not being discarded. However, its branch is now stale/non-mergeable against the audited current main. Marking it as draft: the correct path is to port/rebase the unique features onto current main and re-run the full current CI/coverage/security gates before considering merge. |
Furox-Art
marked this pull request as draft
September 6, 2026 00:11
Resolve conflicts by keeping main elementary-effect sensitivity while porting variance-based screening and identifiability under distinct APIs. Restore CI optional_audit/version_discipline gates on pinned actions. Co-authored-by: Cursor <cursoragent@cursor.com>
Furox-Art
marked this pull request as ready for review
September 11, 2026 13:26
…audit Parse pyproject version with regex for mypy/runtime on Python 3.10, and audit only third-party packages so unpublished local builds do not fail CI. Co-authored-by: Cursor <cursoragent@cursor.com>
CodeQL (security-and-quality) flagged the three `...` bodies in SliceableArray as py/statement-no-effect, leaving three unresolved review threads on this PR. Use `raise NotImplementedError` like src/cds/modeling/_base.py does. This keeps the 100% blended coverage gate green: `raise NotImplementedError` is listed in `[tool.coverage.report] exclude_lines`, whereas `pass` is not and would have introduced three uncovered statements.
|
Kilo Code Review could not run — your account is out of credits. Add credits or switch to a free model to enable reviews on this change. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Scope
Closes the actionable findings from the repository audit and makes the same regression classes CI-visible.
Release / supply chain
--no-isolation[scientific,io]dependencies in a dedicated blocking CI jobScientific / scale
Regression guards
Governance limitation
The code-side safeguards are included here. Repository-level
mainbranch protection/ruleset itself is an administrative GitHub setting and is not writable by the connected GitHub App; it still needs to be enabled in repository settings with the aggregateCIcheck required.