dependabot[bot] commented 1 month ago

User description

Bumps pytest from 8.2.1 to 8.2.2.

Release notes

8.2.2

pytest 8.2.2 (2024-06-04)

Bug Fixes

#12355: Fix possible catastrophic performance slowdown on a certain parametrization pattern involving many higher-scoped parameters.

#12367: Fix a regression in pytest 8.2.0 where unittest class instances (a fresh one is created for each test) were not released promptly on test teardown but only on session teardown.

#12381: Fix possible "Directory not empty" crashes arising from concurent cache dir (.pytest_cache) creation. Regressed in pytest 8.2.0.

Improved Documentation

#12290: Updated Sphinx theme to use Furo instead of Flask, enabling Dark mode theme.

#12356: Added a subsection to the documentation for debugging flaky tests to mention lack of thread safety in pytest as a possible source of flakyness.

#12363: The documentation webpages now links to a canonical version to reduce outdated documentation in search engine results.

Commits

329d371 Prepare release version 8.2.2
214d098 Merge pull request #12414 from bluetech/backport-12409
153a436 [8.2.x] fixtures: fix catastrophic performance problem in reorder_items
b41d5a5 Merge pull request #12412 from pytest-dev/backport-12408-to-8.2.x
9bb73d7 [8.2.x] cacheprovider: fix "Directory not empty" crash from cache directory c...
4569a01 [8.2.x] doc: Update trainings/events (#12402)
1d103e5 [8.2.x] Clarify pytest_ignore_collect docs (#12386)
240a252 [8.2.x] Add html_baseurl to sphinx conf.py (#12372)
a5ee3c4 Merge pull request #12370 from pytest-dev/backport-12368-to-8.2.x
f7358ae [8.2.x] unittest: fix class instances no longer released on test teardown sin...
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Description

Update pytest dependency from version 8.2.1 to 8.2.2 in requirements-dev.txt and requirements.txt.

Changes walkthrough 📝

Relevant files

Dependency

requirements-dev.txt `Update pytest dependency version in requirements-dev.txt` requirements-dev.txt ['Updated `pytest` dependency from 8.2.1 to 8.2.2']	+1/-1
requirements.txt `Update pytest dependency version in requirements.txt` requirements.txt ['Updated `pytest` dependency from 8.2.1 to 8.2.2']	+1/-1

Description

Update pytest dependency version from 8.2.1 to 8.2.2 in requirements files.
Bug fixes and improved documentation in pytest 8.2.2.

Changes walkthrough 📝

Relevant files

Dependencies

requirements-dev.txt Update `pytest` dependency version in requirements-dev.txt requirements-dev.txt ['Update `pytest` dependency version from 8.2.1 to 8.2.2']	+1/-1
requirements.txt Update `pytest` dependency version in requirements.txt requirements.txt ['Update `pytest` dependency version from 8.2.1 to 8.2.2']	+1/-1

coderabbitai[bot] commented 1 month ago

[!IMPORTANT]

Review skipped

Bot user detected.

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

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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 generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@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 as 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. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

deepsource-io[bot] commented 1 month ago

Here's the code health analysis summary for commits 0349c15..ab417d4. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Test coverage	✅ Success		View Check ↗

Code Coverage Report

Metric	Aggregate	Python
Branch Coverage	87.9%	87.9%
Condition Coverage	87.9%	87.9%
Composite Coverage	96.2%	96.2%
Line Coverage	97.5%	97.5%

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

socket-security[bot] commented 1 month ago

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
pypi/pytest@8.2.2	environment, eval, filesystem, network, shell, unsafe	`+4`	8.32 MB	The_Compiler, anatoly, flub, ...4 more

🚮 Removed packages: pypi/pytest@8.2.1, pypi/pytest@8.2.1

View full report↗︎

github-actions[bot] commented 1 month ago

Tag v (branch: main, SHA: 7970784) Added.

codacy-production[bot] commented 1 month ago

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
:white_check_mark: +0.00% (target: -1.00%)	:white_check_mark: ∅

Coverage variation details

| | Coverable lines | Covered lines | Coverage | | ------------- | ------------- | ------------- | ------------- | | Common ancestor commit (8a4c2657ad82519543f41ed9de3b0f5900a3389a) | 407 | 397 | 97.54% | | | Head commit (465e933ed1c3693b404cb40bb6f778ad6fac8a55) | 407 (+0) | 397 (+0) | 97.54% (**+0.00%**) | **Coverage variation** is the difference between the coverage for the head and common ancestor commits of the pull request branch: ` - `

Diff coverage details

| | Coverable lines | Covered lines | Diff coverage | | ------------- | ------------- | ------------- | ------------- | | Pull request (#92) | 0 | 0 | **∅ (not applicable)** | **Diff coverage** is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: `/ * 100%`

See your quality gate settings Change summary preferences

_{:rocket: Don’t miss a bit, follow what’s new on Codacy.}

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

codecov[bot] commented 1 month ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.81%. Comparing base (8a4c265) to head (465e933). Report is 3 commits behind head on main.

:exclamation: Current head 465e933 differs from pull request most recent head ab417d4

Please upload reports for the commit ab417d4 to get more accurate results.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #92 +/- ## ======================================= Coverage 97.81% 97.81% ======================================= Files 10 10 Lines 411 411 Branches 76 76 ======================================= Hits 402 402 Misses 9 9 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

manoelhc commented 1 month ago

@dependabot rebase

github-actions[bot] commented 1 month ago

Qodana Community for Python

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either: - Register at [Qodana Cloud](https://qodana.cloud/) and [configure the action](https://github.com/jetbrains/qodana-action#qodana-cloud) - Use [GitHub Code Scanning with Qodana](https://github.com/jetbrains/qodana-action#github-code-scanning) - Host [Qodana report at GitHub Pages](https://github.com/JetBrains/qodana-action/blob/3a8e25f5caad8d8b01c1435f1ef7b19fe8b039a0/README.md#github-pages) - Inspect and use `qodana.sarif.json` (see [the Qodana SARIF format](https://www.jetbrains.com/help/qodana/qodana-sarif-output.html#Report+structure) for details) To get `*.log` files or any other Qodana artifacts, run the action with `upload-result` option set to `true`, so that the action will upload the files as the job artifacts: ```yaml - name: 'Qodana Scan' uses: JetBrains/qodana-action@v2024.1.5 with: upload-result: true ```

Contact Qodana team

Contact us at [qodana-support@jetbrains.com](mailto:qodana-support@jetbrains.com) - Or via our issue tracker: https://jb.gg/qodana-issue - Or share your feedback: https://jb.gg/qodana-discussions

dependabot[bot] commented 1 month ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

penify-dev[bot] commented 1 month ago

PR Review 🔍

(Review updated until commit https://github.com/manoelhc/test-actions/commit/465e933ed1c3693b404cb40bb6f778ad6fac8a55)

⏱️ Estimated effort to review [1-5]	1, because the changes are straightforward and limited to updating the pytest dependency version in the requirements files.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

penify-dev[bot] commented 1 month ago

PR Code Suggestions ✨

Category	Suggestion	Score
Consistency	Update the `pytest` dependency version consistently to 8.2.2 in both requirements files ___ Consider updating the `pytest` dependency version consistently to 8.2.2 in both requirements files. [requirements-dev.txt [6]](https://github.com/manoelhc/test-actions/pull/92/files#diff-2b4945591edfeaa4cf4d3f155e66d4b43d1bda7a55d881d5cf3107f1b05abbbcR6-R6) ```diff +pytest==8.2.2 - ``` Suggestion importance[1-10]: 8 Why: Maintaining consistent dependency versions across both requirements files is important for stability and compatibility.	8
Consistency	Maintain consistency by updating the `pytest` dependency version to 8.2.2 in both requirements files ___ Ensure consistency by updating the `pytest` dependency version to 8.2.2 in both requirements files. [requirements.txt [7]](https://github.com/manoelhc/test-actions/pull/92/files#diff-4d7c51b1efe9043e44439a949dfd92e5827321b34082903477fd04876edb7552R7-R7) ```diff +pytest==8.2.2 - ``` Suggestion importance[1-10]: 8 Why: Keeping the `pytest` dependency version consistent between the requirements files helps avoid potential conflicts and ensures uniformity.	8

penify-dev[bot] commented 1 month ago

Persistent review updated to latest commit https://github.com/manoelhc/test-actions/commit/465e933ed1c3693b404cb40bb6f778ad6fac8a55

penify-dev[bot] commented 1 month ago

PR Code Suggestions ✨

Category	Suggestion	Score
Consistency	Update the `pytest` dependency version consistently to 8.2.2 in both requirements files ___ Consider updating the `pytest` dependency version consistently to 8.2.2 in both requirements files. [requirements-dev.txt [6]](https://github.com/manoelhc/test-actions/pull/92/files#diff-2b4945591edfeaa4cf4d3f155e66d4b43d1bda7a55d881d5cf3107f1b05abbbcR6-R6) ```diff +pytest==8.2.2 - ``` Suggestion importance[1-10]: 8 Why: The suggestion correctly identifies the inconsistency in the `pytest` version and provides a solution to update it consistently in both files.	8
Consistency	Update the `pytest` dependency version to 8.2.2 for consistency across requirements files ___ Ensure consistency by updating the `pytest` dependency version to 8.2.2 in both requirements files. [requirements.txt [7]](https://github.com/manoelhc/test-actions/pull/92/files#diff-4d7c51b1efe9043e44439a949dfd92e5827321b34082903477fd04876edb7552R7-R7) ```diff +pytest==8.2.2 - ``` Suggestion importance[1-10]: 8 Why: The suggestion is accurate in identifying the need for consistency in the `pytest` version across files and provides the correct solution.	8

codacy-production[bot] commented 1 month ago

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
:white_check_mark: +0.00% (target: -1.00%)	:white_check_mark: ∅

Coverage variation details

| | Coverable lines | Covered lines | Coverage | | ------------- | ------------- | ------------- | ------------- | | Common ancestor commit (0349c1581b2e1d624cd52ffba846bf0482490540) | 407 | 397 | 97.54% | | | Head commit (ab417d4c4a27499c40f089e47053717a9949ee28) | 407 (+0) | 397 (+0) | 97.54% (**+0.00%**) | **Coverage variation** is the difference between the coverage for the head and common ancestor commits of the pull request branch: ` - `

Diff coverage details

| | Coverable lines | Covered lines | Diff coverage | | ------------- | ------------- | ------------- | ------------- | | Pull request (#92) | 0 | 0 | **∅ (not applicable)** | **Diff coverage** is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: `/ * 100%`