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

[3.1] Make LineTooLong exception more detailed about actual data size (GH-2863) #2917

Merged
merged 1 commit into from
Apr 5, 2018

Conversation

asvetlov
Copy link
Member

@asvetlov asvetlov commented Apr 5, 2018

(cherry picked from commit 6a60358)

Co-authored-by: Alexey Popravka popravich@users.noreply.github.com

…GH-2863)

(cherry picked from commit 6a60358)

Co-authored-by: Alexey Popravka <popravich@users.noreply.github.com>
@codecov-io
Copy link

codecov-io commented Apr 5, 2018

Codecov Report

Merging #2917 into 3.1 will increase coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##              3.1    #2917      +/-   ##
==========================================
+ Coverage   97.98%   97.98%   +<.01%     
==========================================
  Files          39       39              
  Lines        7501     7504       +3     
  Branches     1317     1318       +1     
==========================================
+ Hits         7350     7353       +3     
  Misses         48       48              
  Partials      103      103
Impacted Files Coverage Δ
aiohttp/http_parser.py 98.05% <100%> (+0.01%) ⬆️
aiohttp/http_exceptions.py 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

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

@asvetlov asvetlov merged commit 33daec0 into 3.1 Apr 5, 2018
@asvetlov asvetlov deleted the backport-6a60358-3.1 branch April 5, 2018 19:50
@lock
Copy link

lock bot commented Oct 28, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs.
If you feel like there's important points made in this discussion, please include those exceprts into that [new issue].
[new issue]: https://github.com/aio-libs/aiohttp/issues/new

@lock lock bot added the outdated label Oct 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants