-
Notifications
You must be signed in to change notification settings - Fork 38.7k
net: fix maxuploadtarget setting #8707
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
|
utACK 86ce4ec |
src/net.h
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.
I think the comment is wrong?
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.
Whoops, c/p and forgot to actually fill it in. Will fix.
|
Could get affected/obsolete by #8712 |
|
Right, needs a rebase after #8712 probably. |
|
Roger, will rebase after merge. |
src/net.cpp
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.
Needs rebase to solve silent merge conflict.
This was broken by 63cafa6. Note that while this fixes the settings, it doesn't fix the actual usage of -maxuploadtarget completely, as there is currently a bug in the nOptimisticBytesWritten accounting that causes a delayed response if the target is reached. That bug will be addressed separately.
86ce4ec to
f3552da
Compare
|
Rebased after #8712 and fixed the comment. |
|
Concept ACK. Can confirm that this together with #8708 fixes the test failure. |
laanwj
left a comment
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.
utACK f3552da
f3552da net: fix maxuploadtarget setting (Cory Fields)
f3552da net: fix maxuploadtarget setting (Cory Fields)
f3552da net: fix maxuploadtarget setting (Cory Fields)
This was broken by 63cafa6.
Note that while this fixes the settings, it doesn't fix the actual usage of
-maxuploadtarget completely, as there is currently a bug in the
nOptimisticBytesWritten accounting that causes a delayed response if the target
is reached. That bug will be addressed separately.
Thanks to @morcos for reporting.