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

Patch fetch cc test reporter tool as gist submodule #82

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

reactive-firewall
Copy link
Owner

@reactive-firewall reactive-firewall commented Nov 27, 2024

Reviewing:

This is the checklist that I try to go through for every single pull request that I get. If you're wondering why it takes so long for me to accept pull requests, this is why.

General

  • Is this change useful to me, or something that I think will benefit others greatly?
  • Check for overlap with other PRs.
  • Think carefully about the long-term implications of the change. How will it affect existing projects that are dependent on this? How will it affect my projects? If this is complicated, do I really want to maintain it forever? Is there any way it could be implemented as a separate package, for better modularity and flexibility?

Check the Code

  • If it does too much, ask for it to be broken up into smaller PRs.
  • Does it pass make test-style (flake8, etc.)?
  • Is it consistent?
  • Review the changes carefully, line by line. Make sure you understand every single part of every line. Learn whatever you do not know yet.
  • Take the time to get things right. PRs almost always require additional improvements to meet the bar for quality. Be very strict about quality. This usually takes several commits on top of the original PR.

Check the Tests

  • Does it have tests? If not:

  • Comment on the PR "Can you please add tests for this code to tests/test_blah.py", or...

  • Write the tests yourself.

  • Do the tests pass for all of the CI tests? If not, write a note in the PR to fix CI, or fix them yourself.

Check the Docs

  • Does it have docs? If not:

  • Comment on the PR "Can you please add docs for this feature to the wiki", or...

  • Write the docs yourself.

  • If any new functions/classes are added, do they contain docstrings?

Credit the Authors

  • Add name and URL to README.md for security fixes.
  • Thank them for their hard work.

Close Issues

  • Merge the PR branch. This will close the PR's issue.
  • Close any duplicate or related issues that can now be closed. Write thoughtful comments explaining how the issues were resolved.

Release (optional)

  • Decide whether the changes in master make sense as a major, minor, or patch release.
  • Look at the clock. If you're tired, release later when you have time to deal with release problems.
  • Then follow all the steps in [Release Checklist]

Copy link

coderabbitai bot commented Nov 27, 2024

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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 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.

@reactive-firewall reactive-firewall added this to the Version 1.1.5 milestone Nov 27, 2024
@github-actions github-actions bot added Python Lang Changes to Python source code Linter Any linter tool or setting file enhancements Configs Improvements or additions to configuration Testing Something can be verified CI Continuous Integration Tooling Python Repo Anything Project Related labels Nov 27, 2024
Copy link

deepsource-io bot commented Nov 27, 2024

Here's the code health analysis summary for commits 2322eab..acf255f. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource Python LogoPython✅ SuccessView Check ↗

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

Copy link

codecov bot commented Nov 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.000%. Comparing base (2322eab) to head (f40d336).

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##             master        #82   +/-   ##
===========================================
  Coverage   100.000%   100.000%           
===========================================
  Files             1          1           
  Lines            33         33           
===========================================
  Hits             33         33           
Flag Coverage Δ
3.10 100.000% <ø> (ø)
3.11 100.000% <ø> (ø)
3.12 100.000% <ø> (ø)
3.7 100.000% <ø> (+3.571%) ⬆️
3.8 100.000% <ø> (ø)
3.9 100.000% <ø> (ø)
macos-13 100.000% <ø> (ø)
macos-latest 100.000% <ø> (ø)
ubuntu-latest 100.000% <ø> (ø)
windows-latest 100.000% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
pythonrepo/pythonrepo.py 100.000% <ø> (ø)

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2322eab...f40d336. Read the comment docs.

@reactive-firewall
Copy link
Owner Author

Note

Need to fix CI

Copy link
Owner Author

@reactive-firewall reactive-firewall left a comment

Choose a reason for hiding this comment

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

🙅🏻

Unstable Commit

Caution

Unstable - This commit is failed to pass minimal acceptance testing.

pyproject.tomal Outdated
Copy link
Owner Author

Choose a reason for hiding this comment

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

filename seems wrong

Topic :: Software Development :: Libraries :: Python Modules
Topic :: Security
Topic :: System :: Networking
Copy link
Owner Author

Choose a reason for hiding this comment

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

This is inaccurate.

Copy link
Owner Author

Choose a reason for hiding this comment

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

Suggested change
Topic :: System :: Networking

Comment on lines -47 to -48
[files]
packages = pythonrepo
Copy link
Owner Author

Choose a reason for hiding this comment

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

OOps, this should be reverted back to

[files]
packages = pythonrepo

Comment on lines +47 to +49
setuptools>=75.0.0
wheel>=0.44.0
build>=1.2.1
Copy link
Owner Author

Choose a reason for hiding this comment

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

Revert this to

Suggested change
setuptools>=75.0.0
wheel>=0.44.0
build>=1.2.1
setuptools >=38.0.0
wheel>=0.35.0

an in requirements.txt need to use:

setuptools==38.0.0; python_version >= '2.7' and python_version < '3.5'
setuptools==45.0.0; python_version >= '3.5' and python_version <= '3.9.19'
setuptools>=75.0.0; python_version >= '3.9.20'
wheel>=0.35.0; python_version >= '2.7' and python_version <= '3.7'
wheel>=0.44.0; python_version >= '3.8'
build>=1.2.1; python_version >= '3.9.20'

@reactive-firewall
Copy link
Owner Author

😦 Looks like a re-design is in order. At-least for MacOS runners.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration Tooling Configs Improvements or additions to configuration Linter Any linter tool or setting file enhancements Python Lang Changes to Python source code Python Repo Anything Project Related Testing Something can be verified
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improve and Generalize fetch_cc-test-reporter tool as gist submodule
1 participant