Skip to content
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

Delegated outputs may be None #4715

Merged
merged 1 commit into from
Aug 22, 2024
Merged

Delegated outputs may be None #4715

merged 1 commit into from
Aug 22, 2024

Conversation

brimoor
Copy link
Contributor

@brimoor brimoor commented Aug 22, 2024

Fixes a spurious warning that currently appears for delegated operations that don't return outputs.

Summary by CodeRabbit

  • Bug Fixes

    • Improved error handling by adding a check to prevent runtime errors when the outputs variable is None.
  • Chores

    • Enhanced stability of the method by ensuring safe handling of outputs.

@brimoor brimoor added the bug Bug fixes label Aug 22, 2024
@brimoor brimoor requested a review from imanjra August 22, 2024 18:32
Copy link
Contributor

coderabbitai bot commented Aug 22, 2024

Walkthrough

The changes involve adding a conditional check to the _execute_operator method to ascertain that the outputs variable is not None before invoking the to_json() method. This adjustment aims to prevent potential AttributeError exceptions, enhancing the method's robustness when handling asynchronous operations.

Changes

File Path Change Summary
fiftyone/operators/delegated.py Added a conditional check for outputs before calling to_json(), improving error handling.

Poem

In the code where rabbits hop,
A check was made, no need to stop.
When outputs hides away,
We safely play, come what may!
No more errors in our way,
Hooray for changes here today! 🐰✨


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?

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>.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @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.

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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

@imanjra imanjra left a comment

Choose a reason for hiding this comment

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

LGTM

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: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8cb6c6d and b87b70e.

Files selected for processing (1)
  • fiftyone/operators/delegated.py (1 hunks)
Additional comments not posted (1)
fiftyone/operators/delegated.py (1)

408-409: LGTM! Robustness improved with None check.

The conditional check ensures that outputs is not None before calling to_json(), preventing potential AttributeError exceptions. This enhances the robustness of the _execute_operator method.

@brimoor brimoor merged commit fb1fc50 into develop Aug 22, 2024
13 checks passed
@brimoor brimoor deleted the bug/delegated-output branch August 22, 2024 19:21
@brimoor brimoor mentioned this pull request Sep 4, 2024
brimoor added a commit that referenced this pull request Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants