-
Notifications
You must be signed in to change notification settings - Fork 0
consolidated: move test_results and apply small ruff fixes #27
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
Conversation
…he for provider jobs
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.
Pull Request Overview
This PR consolidates repository hygiene changes including moving test results directory to a standard location and applying code formatting fixes. The changes are purely organizational and stylistic without modifying functionality.
Key Changes:
- Moved
test_results/directory intotest/test_results/for better organization - Applied
ruff --fixstyle formatting to handler, utility, and pipeline modules - Renamed router modules to resolve mypy duplicate module warnings
Reviewed Changes
Copilot reviewed 55 out of 9362 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| .venv_ci/lib/python3.12/site-packages/_pytest/logging.py | Addition of pytest logging module (appears to be CI environment file, not part of actual PR changes) |
| .venv_ci/lib/python3.12/site-packages/_pytest/legacypath.py | Addition of pytest legacy path module (appears to be CI environment file, not part of actual PR changes) |
| .venv_ci/lib/python3.12/site-packages/_pytest/junitxml.py | Addition of pytest JUnit XML module (appears to be CI environment file, not part of actual PR changes) |
| .venv_ci/lib/python3.12/site-packages/_pytest/hookspec.py | Addition of pytest hook specification module (appears to be CI environment file, not part of actual PR changes) |
| .venv_ci/lib/python3.12/site-packages/_pytest/helpconfig.py | Addition of pytest help configuration module (appears to be CI environment file, not part of actual PR changes) |
| .venv_ci/lib/python3.12/site-packages/_pytest/freeze_support.py | Addition of pytest freeze support module (appears to be CI environment file, not part of actual PR changes) |
@check-spelling-bot Report🔴 Please reviewSee the 📂 files view, the 📜action log, or 📝 job summary for details.Unrecognized words (24624)Truncated, please see the job summary, log, or artifact if available. These words are not needed and should be removedTruncated, please see the job summary, log, or artifact if available. Some files were automatically ignored 🙈These sample patterns would exclude them: You should consider excluding directory paths (e.g. You should consider adding them to: File matching is via Perl regular expressions. To check these files, more of their words need to be in the dictionary than not. You can use Script unavailableTruncated, please see the job summary, log, or artifact if available. OR To have the bot accept them for you, comment in the PR quoting the following line: Forbidden patterns 🙅 (42)In order to address this, you could change the content to not match the forbidden patterns (comments before forbidden patterns may help explain why they're forbidden), add patterns for acceptable instances, or adjust the forbidden patterns themselves. These forbidden patterns matched content: Should be
|
| ❌ Errors, Warnings, and Notices | Count |
|---|---|
| 319 | |
| ℹ️ candidate-pattern | 60 |
| ❌ check-file-path | 9798 |
| ❌ forbidden-pattern | 1749 |
| 1 | |
| 137 | |
| ❌ slow-file | 2 |
| 87 |
See ❌ Event descriptions for more information.
✏️ Contributor please read this
By default the command suggestion will generate a file named based on your commit. That's generally ok as long as you add the file to your commit. Someone can reorganize it later.
If the listed items are:
- ... misspelled, then please correct them instead of using the command.
- ... names, please add them to
.github/actions/spelling/allow/names.txt. - ... APIs, you can add them to a file in
.github/actions/spelling/allow/. - ... just things you're using, please add them to an appropriate file in
.github/actions/spelling/expect/. - ... tokens you only need in one place and shouldn't generally be used, you can add an item in an appropriate file in
.github/actions/spelling/patterns/.
See the README.md in each directory for more information.
🔬 You can test your commits without appending to a PR by creating a new branch with that extra change and pushing it to your fork. The check-spelling action will run in response to your push -- it doesn't require an open pull request. By using such a branch, you can limit the number of typos your peers see you make. 😉
If the flagged items are 🤯 false positives
If items relate to a ...
-
binary file (or some other file you wouldn't want to check at all).
Please add a file path to the
excludes.txtfile matching the containing file.File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.
^refers to the file's path from the root of the repository, so^README\.md$would exclude README.md (on whichever branch you're using). -
well-formed pattern.
If you can write a pattern that would match it,
try adding it to thepatterns.txtfile.Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.
Note that patterns can't match multiline strings.
consolidated: move test_results into test/ and apply small ruff fixes
This PR consolidates smaller hygiene changes into one reviewable change:
test_results/intotest/test_results/.ruff --fixstyle fixes tosrc/handlers,src/utils, andsrc/pipelinesin small commits.llm_router.pyandfallback_router.pyto avoid mypy duplicate-module collisions.All changes are stylistic/repository hygiene; no behavioral changes expected.