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

Merging main to develop #5250

Merged
merged 3 commits into from
Dec 10, 2024
Merged

Merging main to develop #5250

merged 3 commits into from
Dec 10, 2024

Conversation

brimoor
Copy link
Contributor

@brimoor brimoor commented Dec 10, 2024

Summary by CodeRabbit

  • New Features

    • Introduced FIFTYONE_CVAT_EMAIL environment variable for CVAT server configuration.
    • Added Data Lens feature for exploring and importing samples from external sources.
    • Launched Data Quality Panel for automatic dataset quality scanning.
    • Introduced Query Performance Panel for optimizing queries on large datasets.
    • Enabled embeddings visualizations directly from the Embeddings panel.
    • Added SMTP server configuration for sending user invitations in Internal Mode.
  • Documentation

    • Enhanced documentation for plugin development and usage, including updates on handling the new FIFTYONE_CVAT_EMAIL secret.
    • Improved clarity on the annotation API and environment variable configurations.

@brimoor brimoor requested a review from findtopher December 10, 2024 14:28
Copy link
Contributor

coderabbitai bot commented Dec 10, 2024

Walkthrough

The changes in this pull request focus on updating the documentation for FiftyOne, specifically regarding the integration with CVAT. A new environment variable, FIFTYONE_CVAT_EMAIL, has been introduced to allow users to provide an email address for authentication. Documentation updates include enhanced instructions for configuring this variable, clarifications on handling sensitive information, and improvements to various sections related to plugin development and usage. Overall, the updates aim to provide clearer guidance on authentication and configuration processes without altering existing functionalities.

Changes

File Path Change Summary
docs/source/integrations/cvat.rst Added FIFTYONE_CVAT_EMAIL environment variable; updated configuration examples for CVAT.
docs/source/plugins/developing_plugins.rst Added FIFTYONE_CVAT_EMAIL secret to fiftyone.yml example for the @voxel51/annotation plugin.
docs/source/plugins/using_plugins.rst Updated "Getting plugin info" to include FIFTYONE_CVAT_EMAIL; clarified GitHub token usage.
docs/source/release-notes.rst Introduced new features: Data Lens, Data Quality Panel, Query Performance Panel, SMTP configuration, embeddings visualizations, and model evaluation.
docs/source/teams/secrets.rst Added FIFTYONE_CVAT_EMAIL secret key to the @voxel51/annotation plugin documentation.
docs/source/user_guide/annotation.rst Expanded environment variable section to include FIFTYONE_CVAT_EMAIL; clarified annotate() method parameters.

Possibly related PRs

Suggested labels

documentation

🐇 In the garden of code, we hop and play,
With FIFTYONE_CVAT_EMAIL, brightening the way.
Secrets and plugins, all in a row,
Clearer instructions for all who will grow.
So let’s celebrate with a joyful cheer,
For better documentation, we hold dear! 🌼


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>, please review it.
    • 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 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 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 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. (Experiment)
  • @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.

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

🧹 Outside diff range and nitpick comments (1)
docs/source/integrations/cvat.rst (1)

Line range hint 221-237: LGTM! Consider adding more context about email requirement

The addition of the FIFTYONE_CVAT_EMAIL environment variable is well-documented and follows the existing pattern. However, it would be helpful to add a brief note explaining when/why this email field is required for authentication.

Add a brief explanation like:

    export FIFTYONE_CVAT_EMAIL=...  # if applicable
+   # Note: The email field is required when using CVAT's SSO authentication
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ea8b36f and a035528.

📒 Files selected for processing (6)
  • docs/source/integrations/cvat.rst (2 hunks)
  • docs/source/plugins/developing_plugins.rst (5 hunks)
  • docs/source/plugins/using_plugins.rst (4 hunks)
  • docs/source/release-notes.rst (2 hunks)
  • docs/source/teams/secrets.rst (2 hunks)
  • docs/source/user_guide/annotation.rst (1 hunks)
🔇 Additional comments (9)
docs/source/teams/secrets.rst (1)

70-70: LGTM! The new secret key is properly documented.

The addition of FIFTYONE_CVAT_EMAIL is consistent across both the YAML configuration and Python usage examples, maintaining proper documentation standards.

Let's verify the consistency of this secret across the codebase:

Also applies to: 87-87

✅ Verification successful

Secret key FIFTYONE_CVAT_EMAIL is consistently documented and properly used across the codebase

The verification shows that the secret is consistently documented and used across multiple documentation files:

  • Properly listed in configuration examples in teams/secrets.rst
  • Correctly demonstrated in usage examples with ctx.secrets["FIFTYONE_CVAT_EMAIL"]
  • Consistently documented in integration guides and tutorials
  • Maintains the same format and naming convention throughout the codebase
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the FIFTYONE_CVAT_EMAIL secret is consistently documented
# and implemented across the codebase

# Check for the secret in configuration files and documentation
rg -A 2 "FIFTYONE_CVAT_EMAIL" 

# Check for any potential usages in Python code
ast-grep --pattern 'ctx.secrets["FIFTYONE_CVAT_EMAIL"]'

Length of output: 3115

docs/source/plugins/using_plugins.rst (1)

299-299: LGTM! The new secret key is comprehensively documented.

The FIFTYONE_CVAT_EMAIL secret is consistently documented across all relevant sections:

  • Plugin info output
  • YAML configuration
  • Environment variables setup
  • Python usage example

The documentation maintains proper formatting and provides clear guidance for users.

Also applies to: 473-473, 496-496, 509-509

docs/source/user_guide/annotation.rst (1)

360-361: LGTM! The email configuration is properly documented.

The addition of the FIFTYONE_CVAT_EMAIL environment variable is well-documented with:

  • Clear indication that it's optional ("if applicable")
  • Proper integration into the environment variables section
  • Consistent formatting with other configuration options

Also applies to: 368-368

docs/source/integrations/cvat.rst (2)

Line range hint 1532-1549: LGTM! Secret declaration is properly documented

The addition of FIFTYONE_CVAT_EMAIL to the plugin's secrets list is consistent with the environment variable changes and follows the established pattern.


Line range hint 1562-1563: LGTM! Code example properly demonstrates secret usage

The example correctly shows how to access the new FIFTYONE_CVAT_EMAIL secret in operators, maintaining consistency with the documentation above.

docs/source/plugins/developing_plugins.rst (2)

255-255: LGTM! Secret is properly included in plugin example

The addition of FIFTYONE_CVAT_EMAIL to the example fiftyone.yml file is consistent with the CVAT integration changes.


2508-2508: LGTM! Code example properly demonstrates secret usage in panels

The example correctly shows how to access the new FIFTYONE_CVAT_EMAIL secret in panels, maintaining consistency with the plugin documentation.

docs/source/release-notes.rst (2)

54-55: LGTM: Added referrerPolicy for reverse proxy support

The addition of referrerPolicy improves the App's functionality when running behind reverse proxies.


66-67: LGTM: Optimized object detection evaluation

The optimization of object detection evaluation using r-trees improves performance.

Copy link
Member

@findtopher findtopher left a comment

Choose a reason for hiding this comment

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

🔩

@brimoor brimoor merged commit 42c6b18 into develop Dec 10, 2024
12 checks passed
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