Skip to content

Conversation

@johanneskoester
Copy link
Contributor

@johanneskoester johanneskoester commented Jun 11, 2025

Summary by CodeRabbit

  • Bug Fixes
    • Improved handling of optional storage settings and rate limits to prevent errors when values are missing.
    • Enhanced detection of read/write capabilities for storage providers, ensuring more accurate behavior in storage operations.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 11, 2025

📝 Walkthrough

Walkthrough

The changes update type annotations and logic in the StorageProviderBase class. The constructor now accepts an optional integer for wait_for_free_local_storage. The rate_limiter method's logic was adjusted for explicit None handling and validation. The is_read_write property now separately checks for read and write capabilities using individual class imports and isinstance checks.

Changes

File(s) Change Summary
snakemake_interface_storage_plugins/storage_provider.py Updated type annotation for constructor parameter, revised rate_limiter logic with explicit None checks and validation, and refactored is_read_write property to use separate class imports and dual isinstance checks.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant StorageProviderBase
    participant Settings
    participant StorageObjectRead
    participant StorageObjectWrite

    User->>StorageProviderBase: Instantiate (wait_for_free_local_storage: Optional[int])
    StorageProviderBase->>Settings: Access max_requests_per_second
    alt max_requests_per_second is set
        StorageProviderBase->>StorageProviderBase: Use custom rate limit
    else
        StorageProviderBase->>StorageProviderBase: Use default rate limit
    end
    User->>StorageProviderBase: Access is_read_write property
    StorageProviderBase->>StorageObjectRead: Check isinstance
    StorageProviderBase->>StorageObjectWrite: Check isinstance
    alt Both checks True
        StorageProviderBase-->>User: Return True
    else
        StorageProviderBase-->>User: Return False
    end
Loading

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 31a3b42 and 5d382fa.

📒 Files selected for processing (1)
  • snakemake_interface_storage_plugins/storage_provider.py (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • snakemake_interface_storage_plugins/storage_provider.py
✨ Finishing Touches
  • 📝 Generate Docstrings

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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
snakemake_interface_storage_plugins/storage_provider.py (1)

62-70: Docstring / help text missing for new Optional[int] parameter

The constructor now allows wait_for_free_local_storage=None.
A short docstring or inline comment explaining the meaning of None (disable waiting) vs. a positive integer would make the API clearer for plugin authors.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 37a2a70 and 31a3b42.

📒 Files selected for processing (1)
  • snakemake_interface_storage_plugins/storage_provider.py (3 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.py`: Do not try to improve formatting. Do not suggest type annotations for functions that are defined inside of functions or methods. Do not suggest type annotation of the `s...

**/*.py: Do not try to improve formatting.
Do not suggest type annotations for functions that are defined inside of functions or methods.
Do not suggest type annotation of the self argument of methods.
Do not suggest type annotation of the cls argument of classmethods.
Do not suggest return type annotation if a function or method does not contain a return statement.

  • snakemake_interface_storage_plugins/storage_provider.py
🧬 Code Graph Analysis (1)
snakemake_interface_storage_plugins/storage_provider.py (1)
snakemake_interface_storage_plugins/storage_object.py (2)
  • StorageObjectRead (123-258)
  • StorageObjectWrite (261-284)

Comment on lines +165 to 172
StorageObjectRead,
StorageObjectWrite,
)

return isinstance(self.storage_object_cls, StorageObjectReadWrite)
return isinstance(
self.get_storage_object_cls(), StorageObjectRead
) and isinstance(self.get_storage_object_cls(), StorageObjectWrite)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

is_read_write uses isinstance() on a class – should be issubclass()

self.get_storage_object_cls() returns a class, but isinstance() expects an instance.
As written, the expression will always evaluate to False, so is_read_write will never report True, even when the storage object supports both read and write.

-        return isinstance(
-            self.get_storage_object_cls(), StorageObjectRead
-        ) and isinstance(self.get_storage_object_cls(), StorageObjectWrite)
+        cls = self.get_storage_object_cls()
+        return issubclass(cls, StorageObjectRead) and issubclass(cls, StorageObjectWrite)

This also avoids the double call to get_storage_object_cls().
Failing to fix this will silently disable the read-write code paths that rely on this property.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
StorageObjectRead,
StorageObjectWrite,
)
return isinstance(self.storage_object_cls, StorageObjectReadWrite)
return isinstance(
self.get_storage_object_cls(), StorageObjectRead
) and isinstance(self.get_storage_object_cls(), StorageObjectWrite)
StorageObjectRead,
StorageObjectWrite,
)
cls = self.get_storage_object_cls()
return issubclass(cls, StorageObjectRead) and issubclass(cls, StorageObjectWrite)
🤖 Prompt for AI Agents
In snakemake_interface_storage_plugins/storage_provider.py around lines 165 to
172, the is_read_write property incorrectly uses isinstance() on a class
returned by get_storage_object_cls(), which always returns False. Replace
isinstance() with issubclass() to correctly check if the class is a subclass of
StorageObjectRead and StorageObjectWrite. Also, call get_storage_object_cls()
once, store the result in a variable, and use that variable for both subclass
checks to avoid redundant calls.

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants