Repository navigation
Develop v2.1.0 - #1941
Develop v2.1.0#1941
Conversation
fix down_revision(WEKO3_OPE-10145)
Reviewer's guide (collapsed on small PRs)Reviewer's GuideUpdates the Alembic migration dependency so the file read-only keys migration follows revision 8ae99b034410 instead of 8644b32a3eec, keeping the migration graph aligned for v2.1.0. Flow diagram for the v2.1.0 migration dependencyflowchart LR
R[8ae99b034410] --> F[faf4faa08601<br/>Add file read-only keys]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🔍 Claude レビュー統合指摘はありません。 次にすること: 差分は変更なしで問題ありません。 モデル sonnet / 2 回実行して和集合 / コスト $0.1551。同じ入力でも結果が揺れるため複数回まわし、一部のパスでしか挙がらなかったものには回数を添えています 他レビューを踏まえた自動レビューです。誤りが含まれることがあります。 |
There was a problem hiding this comment.
Hey - I've found 1 issue
Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments
### Comment 1
<location path="modules/invenio-files-rest/invenio_files_rest/alembic/faf4faa08601_add_column_file_readonly_keys.py" line_range="16" />
<code_context>
# revision identifiers, used by Alembic.
revision = 'faf4faa08601'
-down_revision = '8644b32a3eec'
+down_revision = '8ae99b034410'
branch_labels = ()
depends_on = None
</code_context>
<issue_to_address>
**Location upgrades and queries fail**
When a fresh database is upgraded, or an existing database is at `8644b32a3eec`, `faf4faa08601` skips `8644b32a3eec`, so Alembic cannot plan upgrades from that revision, and fresh schemas miss the S3 columns. Existing rows also miss the read-only-key columns; location access then fails with a database error.
Restore `8644b32a3eec` as `down_revision` so Alembic follows the migration chain and applies the required column migrations.
</issue_to_address>Sourcery assessment
Needs a human reviewer. 1 finding to address first, and this changes the Alembic migration graph, so an incorrect dependency could make upgrades run in the wrong order or fail, potentially leaving a partially applied schema change. Reverting fixes future migration runs, while any already-applied schema state would need a migration rerun or repair.
Blocking findings: modules/invenio-files-rest/invenio_files_rest/alembic/faf4faa08601_add_column_file_readonly_keys.py:16
| # revision identifiers, used by Alembic. | ||
| revision = 'faf4faa08601' | ||
| down_revision = '8644b32a3eec' | ||
| down_revision = '8ae99b034410' |
There was a problem hiding this comment.
🟠 High · Location upgrades and queries fail
When a fresh database is upgraded, or an existing database is at 8644b32a3eec, faf4faa08601 skips 8644b32a3eec, so Alembic cannot plan upgrades from that revision, and fresh schemas miss the S3 columns. Existing rows also miss the read-only-key columns; location access then fails with a database error.
Restore 8644b32a3eec as down_revision so Alembic follows the migration chain and applies the required column migrations.
Prompt for AI agents
In `modules/invenio-files-rest/invenio_files_rest/alembic/faf4faa08601_add_column_file_readonly_keys.py` at line 16:
**Location upgrades and queries fail**
When a fresh database is upgraded, or an existing database is at `8644b32a3eec`, `faf4faa08601` skips `8644b32a3eec`, so Alembic cannot plan upgrades from that revision, and fresh schemas miss the S3 columns. Existing rows also miss the read-only-key columns; location access then fails with a database error.
Restore `8644b32a3eec` as `down_revision` so Alembic follows the migration chain and applies the required column migrations.
API インベントリ差分(件数のみ)
ベースラインとの差分API インベントリ差分レポート
判定: ❌ FAIL (FAIL 1 / WARN 3)サマリ
[FAIL] G2 認証系デコレータが削除された — 3件
[WARN] W2 実装本体が変化(data_op / 情報露出を再確認) — 9件
[WARN] W6 依存パッケージの版が変化した — 1件
[WARN] W5 監視対象 config が変化した — 2件
台帳との突き合わせ(生成されませんでした) ソース由来の経路検知(生成されませんでした) |
Summary by Sourcery
Chores: