Fix requirements.txt conflicts and regenerate poetry.lock to sync with pyproject.toml#121
Fix requirements.txt conflicts and regenerate poetry.lock to sync with pyproject.toml#121mithun50 wants to merge 8 commits intoAOSSIE-Org:mainfrom mithun50:main
Conversation
Added `poetry lock` command to sync the both `pyproject.toml` and `poetry.lock`
Deleting this due to it has conflict
This file is not synced with pyproject.toml
WalkthroughThe changes update dependency version constraints in Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Poetry
participant System
User->>Poetry: poetry env use python3.10
User->>Poetry: poetry lock --no-update
Poetry->>System: Update poetry.lock without updating dependencies
User->>Poetry: poetry install --with dev
Poetry->>System: Install dependencies per lock file
Estimated code review effort🎯 2 (Simple) | ⏱️ ~7 minutes Assessment against linked issues
Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/INSTALL_GUIDE.md (1)
32-37: Usepoetry lock --no-updateto avoid inadvertent upgradesRunning plain
poetry lock(Line 35) regenerates the lock file and may pull newer versions than the ones committed, defeating reproducibility.
Recommend the safer variant:-poetry lock +poetry lock --no-update # regenerate hashes without bumping versionsAdd a short rationale so newcomers understand the difference.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
poetry.lockis excluded by!**/*.lock
📒 Files selected for processing (2)
backend/requirements.txt(1 hunks)docs/INSTALL_GUIDE.md(1 hunks)
🔇 Additional comments (1)
backend/requirements.txt (1)
123-124: Ignore outdated protobuf constraint for onnxruntime==1.22.0PyPI metadata for onnxruntime 1.22.0 shows its only
Requires-Distentry is"protobuf"(no version cap), so pinningprotobuf>=6.30.0,<6.32.0does not conflict.No changes required:
- backend/requirements.txt lines 123–124 (
onnxruntime==1.22.0)- backend/requirements.txt line 153 (
protobuf>=6.30.0,<6.32.0)Likely an incorrect or invalid review comment.
Fixed some conflicts
Fixed version incompatible
|
Review required @smokeyScraper |
|
Hey @mithun50, Refer -> #106 (comment) |
|
Hey @smokeyScraper I'll go ahead and restructure the commits to keep the history clean — combining the edit-related ones and keeping a single commit for the CodeRabbit fix as suggested. Will use the editor's Git tools to make it neat. Appreciate the heads-up! |
2 participants
Closes #120
📝 Description
This PR addresses the following issues:
Regenerated poetry.lock using poetry lock to reflect the updated dependencies in pyproject.toml.
🔧 Changes Made
Fixed dependency conflicts in requirements.txt:
Regenerated poetry.lock file:
Verified consistency between:
Ensured no unintended version upgrades/downgrades by reviewing diffs in poetry.lock.
✅ Checklist
Summary by CodeRabbit
Documentation
Chores