Skip to content

fix: Spelling error fixed#7370

Merged
Dreamsorcerer merged 2 commits into
aio-libs:masterfrom
abdulaev-sh-m:master
Jul 18, 2023
Merged

fix: Spelling error fixed#7370
Dreamsorcerer merged 2 commits into
aio-libs:masterfrom
abdulaev-sh-m:master

Conversation

@abdulaev-sh-m

@abdulaev-sh-m abdulaev-sh-m commented Jul 18, 2023

Copy link
Copy Markdown
Contributor

What do these changes do?

Fixes #7351

Are there changes in behavior for the user?

Related issue number

Checklist

  • I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • If you provide code modification, please add yourself to CONTRIBUTORS.txt
    • The format is <Name> <Surname>.
    • Please keep alphabetical order, the file is sorted by names.
  • Add a new news fragment into the CHANGES folder
    • name it <issue_id>.<type> for example (588.bugfix)
    • if you don't have an issue_id change it to the pr id after creating the pr
    • ensure type is one of the following:
      • .feature: Signifying a new feature.
      • .bugfix: Signifying a bug fix.
      • .doc: Signifying a documentation improvement.
      • .removal: Signifying a deprecation or removal of public API.
      • .misc: A ticket has been closed, but it is not of interest to users.
    • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."

@Dreamsorcerer Dreamsorcerer added bot:chronographer:skip This PR does not need to include a change note backport-3.8 labels Jul 18, 2023
@Dreamsorcerer Dreamsorcerer enabled auto-merge (squash) July 18, 2023 09:59
@Dreamsorcerer

Copy link
Copy Markdown
Member

Thanks

@codecov

codecov Bot commented Jul 18, 2023

Copy link
Copy Markdown

Codecov Report

Merging #7370 (20db75e) into master (44f322d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7370   +/-   ##
=======================================
  Coverage   97.27%   97.27%           
=======================================
  Files         106      106           
  Lines       31410    31410           
  Branches     3926     3926           
=======================================
  Hits        30555    30555           
  Misses        650      650           
  Partials      205      205           
Flag Coverage Δ
CI-GHA 97.22% <ø> (ø)
OS-Linux 96.89% <ø> (-0.01%) ⬇️
OS-Windows 95.35% <ø> (ø)
OS-macOS 96.58% <ø> (ø)
Py-3.10.11 95.28% <ø> (ø)
Py-3.10.12 96.78% <ø> (ø)
Py-3.11.0 96.53% <ø> (ø)
Py-3.8.10 95.25% <ø> (ø)
Py-3.8.17 96.72% <ø> (ø)
Py-3.9.13 95.24% <ø> (ø)
Py-3.9.17 96.74% <ø> (ø)
Py-pypy7.3.11 94.22% <ø> (-0.01%) ⬇️
VM-macos 96.58% <ø> (ø)
VM-ubuntu 96.89% <ø> (-0.01%) ⬇️
VM-windows 95.35% <ø> (ø)

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

Impacted Files Coverage Δ
aiohttp/payload.py 95.47% <ø> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@Dreamsorcerer Dreamsorcerer merged commit 22c264c into aio-libs:master Jul 18, 2023
@patchback

patchback Bot commented Jul 18, 2023

Copy link
Copy Markdown
Contributor

Backport to 3.8: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.8/22c264ce70c9ff45eb2d21a090a874a4ffcdb469/pr-7370

Backported as #7371

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

patchback Bot pushed a commit that referenced this pull request Jul 18, 2023
(cherry picked from commit 22c264c)
@patchback

patchback Bot commented Jul 18, 2023

Copy link
Copy Markdown
Contributor

Backport to 3.9: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.9/22c264ce70c9ff45eb2d21a090a874a4ffcdb469/pr-7370

Backported as #7372

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

patchback Bot pushed a commit that referenced this pull request Jul 18, 2023
(cherry picked from commit 22c264c)
Dreamsorcerer pushed a commit that referenced this pull request Jul 18, 2023
**This is a backport of PR #7370 as merged into master
(22c264c).**

<!-- Thank you for your contribution! -->

## What do these changes do?

Fixes #7351 

## Are there changes in behavior for the user?

<!-- Outline any notable behaviour for the end users. -->

## Related issue number

<!-- Are there any issues opened that will be resolved by merging this
change? -->

## Checklist

- [x] I think the code is well written
- [x] Unit tests for the changes exist
- [x] Documentation reflects the changes
- [x] If you provide code modification, please add yourself to
`CONTRIBUTORS.txt`
  * The format is &lt;Name&gt; &lt;Surname&gt;.
  * Please keep alphabetical order, the file is sorted by names.
- [x] Add a new news fragment into the `CHANGES` folder
  * name it `<issue_id>.<type>` for example (588.bugfix)
* if you don't have an `issue_id` change it to the pr id after creating
the pr
  * ensure type is one of the following:
    * `.feature`: Signifying a new feature.
    * `.bugfix`: Signifying a bug fix.
    * `.doc`: Signifying a documentation improvement.
    * `.removal`: Signifying a deprecation or removal of public API.
* `.misc`: A ticket has been closed, but it is not of interest to users.
* Make sure to use full sentences with correct case and punctuation, for
example: "Fix issue with non-ascii contents in doctest text files."

Co-authored-by: Shamil Abdulaev <[email protected]>
Dreamsorcerer pushed a commit that referenced this pull request Jul 18, 2023
**This is a backport of PR #7370 as merged into master
(22c264c).**

<!-- Thank you for your contribution! -->

## What do these changes do?

Fixes #7351 

## Are there changes in behavior for the user?

<!-- Outline any notable behaviour for the end users. -->

## Related issue number

<!-- Are there any issues opened that will be resolved by merging this
change? -->

## Checklist

- [x] I think the code is well written
- [x] Unit tests for the changes exist
- [x] Documentation reflects the changes
- [x] If you provide code modification, please add yourself to
`CONTRIBUTORS.txt`
  * The format is &lt;Name&gt; &lt;Surname&gt;.
  * Please keep alphabetical order, the file is sorted by names.
- [x] Add a new news fragment into the `CHANGES` folder
  * name it `<issue_id>.<type>` for example (588.bugfix)
* if you don't have an `issue_id` change it to the pr id after creating
the pr
  * ensure type is one of the following:
    * `.feature`: Signifying a new feature.
    * `.bugfix`: Signifying a bug fix.
    * `.doc`: Signifying a documentation improvement.
    * `.removal`: Signifying a deprecation or removal of public API.
* `.misc`: A ticket has been closed, but it is not of interest to users.
* Make sure to use full sentences with correct case and punctuation, for
example: "Fix issue with non-ascii contents in doctest text files."

Co-authored-by: Shamil Abdulaev <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bot:chronographer:skip This PR does not need to include a change note

Projects

None yet

Development

Successfully merging this pull request may close these issues.

typo in payload.py class AsyncIterablePayload error message

2 participants