-
Notifications
You must be signed in to change notification settings - Fork 13
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
Fix metadata bug in OxenFS write #67
Conversation
WalkthroughThe changes update the OxenFS class documentation by adding an example that demonstrates how to use Changes
Sequence Diagram(s)sequenceDiagram
participant T as Test Function
participant F as fsspec Backend
participant O as OxenFS (_open_write)
participant R as RemoteRepo
T ->> F: Initialize filesystem parameters
T ->> O: Request write file operation with file object and commit message
O ->> O: Check if target directory exists (metadata check)
O ->> R: Write file and record commit
R -->> T: Confirm commit and file write
T ->> T: Assert commit count and validate file content
Poem
✨ Finishing Touches
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
oxen/tests/test_fsspec_backend.py (1)
79-100
: LGTM! Good test coverage for writing to new directories.The test effectively validates the core functionality of writing files to new directories, maintaining consistency with existing test patterns.
Consider adding additional test cases to cover:
- Error scenarios (e.g., writing to a path where parent is a file)
- Directory metadata verification after creation
- Nested directory creation (e.g., "new_dir/sub_dir/file.txt")
Example test case for error scenario:
def test_fsspec_write_file_to_invalid_dir(chat_bot_remote_repo_fully_pushed): local_repo, remote_repo = chat_bot_remote_repo_fully_pushed fs = fsspec.filesystem( "oxen", namespace=remote_repo._repo.namespace(), repo=remote_repo._repo.name(), host=remote_repo._repo.host, scheme=remote_repo._repo.scheme ) # First create a file with fs.open("file.txt", mode="wb") as f: f.write("This is a file") # Then try to write to a path where parent is this file with pytest.raises(ValueError, match="target_dir cannot be an existing file"): with fs.open("file.txt/invalid.txt", mode="wb") as f: f.write("This should fail")
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
oxen/python/oxen/oxen_fs.py
(2 hunks)oxen/tests/test_fsspec_backend.py
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
- GitHub Check: test
- GitHub Check: test
🔇 Additional comments (2)
oxen/python/oxen/oxen_fs.py (2)
65-79
: LGTM! Clear and helpful documentation example.The example effectively demonstrates how to use
shutil.copyfileobj
with OxenFS, following good documentation practices.
219-219
:❓ Verification inconclusive
LGTM! Improved error handling for directory metadata.
The addition of the null check
metadata and not metadata.is_dir
fixes a potential NoneType error when checking directory metadata.Let's verify that this is the only place where we need this null check:
🏁 Script executed:
#!/bin/bash # Search for other metadata.is_dir checks that might need the same null check ast-grep --pattern 'metadata.is_dir'Length of output: 237
Action Required: Confirm safeguarded usage of metadata.is_dir in earlier code blocks
The null-check added at line 219 effectively prevents a potential NoneType error for that specific condition. However, our search indicates there are two other occurrences (lines 159 and 197) where
metadata.is_dir
is used without a null check. Please verify that in those contexts themetadata
variable is guaranteed to be non-null. If there's any possibility thatmetadata
could beNone
in those cases, consider adding a similar null check to prevent runtime errors.
Also document how to save an existing file object using
OxenFS
andshutil.copyfileobj
.Summary by CodeRabbit
Documentation
Bug Fixes
Tests