The only place where it is used is to compute a buffer size, and it doesn't really need to be used there. ONE8MEGABYTE is good enough.
Details
Details
- Reviewers
freetrader sickpig kyuupichan awemany - Group Reviewers
Restricted Project - Commits
- rSTAGINGd2939c33b08c: Remove globals.h use from net.cpp
rABCd2939c33b08c: Remove globals.h use from net.cpp
make check ../qa/pull-tester/rpc-tests.py maxuploadtarget.py
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- netglobals
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 298 Build 298: arc lint + arc unit
Event Timeline
Comment Actions
Code changes look ok for current test, and I can accept on that basis.
I will make myself a task to verify whether maxuploadtarget.py still passes if bigger blocks (i.e. the user's max upload target is respected even if blocks are >> 1MB).
Best would be to extend maxuploadtarget.py test accordingly to do a bigger-block check.