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

Astral ruff commands #65

Closed
wants to merge 5 commits into from
Closed

Astral ruff commands #65

wants to merge 5 commits into from

Conversation

JacobCoffee
Copy link
Owner

Pull Request Checklist

  • New code has 100% test coverage
  • (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
  • (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR
  • Pre-Commit Checks were ran and passed
  • Tests were ran and passed

Description

Close Issue(s)

Copy link

railway-app bot commented Feb 27, 2024

This PR is being deployed to Railway 🚅

Copy link

railway-app bot commented Feb 27, 2024

This PR is being deployed to Railway 🚅

byte: ◻️ REMOVED

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

PR Type: Enhancement

PR Summary: This pull request introduces new functionality related to Astral Inc. software, specifically Ruff, by adding commands to query Ruff linting rules and format code using Ruff. It includes changes to utility functions, settings, and the addition of a new plugin module for Astral-related commands. The PR modifies logging setup, updates constants, and adjusts settings configurations to accommodate the new features.

Decision: Comment

📝 Type: 'Enhancement' - not supported yet.
  • Sourcery currently only approves 'Typo fix' PRs.
✅ Issue addressed: this change correctly addresses the issue or implements the desired feature.
No details provided.
📝 Complexity: the changes are too large or complex for Sourcery to approve.
  • Unsupported files: the diff contains files that Sourcery does not currently support during reviews.

General suggestions:

  • Ensure that all new commands and utilities are thoroughly tested, especially those that interact with external processes or APIs.
  • Consider refining exception handling to catch more specific exceptions rather than generic ones, as this can improve debugging and error reporting.
  • Review the changes to settings configurations, particularly the addition of 'extra="ignore"' in various settings, to ensure that this aligns with the project's configuration management practices.
  • Verify that the new plugin module integrates smoothly with the existing bot framework and that command interactions are intuitive for end-users.

Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨

Share Sourcery

Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.

Comment on lines +231 to +232
except Exception as e: # noqa: BLE001
stderr = e.stderr.decode() if hasattr(e, "stderr") else "" # type: ignore[reportAttributeAccessIssue]
Copy link
Contributor

Choose a reason for hiding this comment

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

suggestion (llm): Catching a generic Exception is generally not recommended as it can make debugging harder by obscuring the actual exceptions being raised. Consider catching more specific exceptions related to the subprocess execution or the environment that could fail. This approach will make the error handling more precise and informative.

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.

1 participant