-
Notifications
You must be signed in to change notification settings - Fork 2
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
base: master
Are you sure you want to change the base?
Patch fetch cc test reporter tool as gist submodule #82
Conversation
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Here's the code health analysis summary for commits Analysis Summary
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #82 +/- ##
===========================================
Coverage 100.000% 100.000%
===========================================
Files 1 1
Lines 33 33
===========================================
Hits 33 33
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Sentry.
|
Note Need to fix CI |
There was a problem hiding this 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
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is inaccurate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Topic :: System :: Networking |
[files] | ||
packages = pythonrepo |
There was a problem hiding this comment.
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
setuptools>=75.0.0 | ||
wheel>=0.44.0 | ||
build>=1.2.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Revert this to
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'
😦 Looks like a re-design is in order. At-least for MacOS runners. |
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
Check the Code
make test-style
(flake8, etc.)?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
README.md
for security fixes.Close Issues
Release (optional)