Rather than both.
Introduced in 386a6b62a8a1db9dd0f354cb95b7585f555c7e5d, #12653
I think it's reasonable to split the expression to log which directory needs more space.
utACK 11e85ca
1630 | @@ -1631,7 +1631,7 @@ bool AppInitMain(InitInterfaces& interfaces) 1631 | 1632 | // ********************************************************* Step 11: import blocks 1633 | 1634 | - if (!CheckDiskSpace() && !CheckDiskSpace(0, true)) 1635 | + if (!CheckDiskSpace() || !CheckDiskSpace(0, true))
Could use named arguments for literals?
utACK 11e85ca
1630 | @@ -1631,7 +1631,7 @@ bool AppInitMain(InitInterfaces& interfaces) 1631 | 1632 | // ********************************************************* Step 11: import blocks 1633 | 1634 | - if (!CheckDiskSpace() && !CheckDiskSpace(0, true)) 1635 | + if (!CheckDiskSpace() || !CheckDiskSpace(/* additional_bytes */ 0, /* blocks_dir */ true))
When you are changing this anyway: please provide explicit arguments to the first call too, instead of relying on default arguments
Rather than both.
Introduced in 386a6b62a8a1db9dd0f354cb95b7585f555c7e5d
Updated to address feedback.
utACK ba8c8b22, thanks!
utACK ba8c8b22272ad40fe2de465d7e745532bab48d3b
Could add a test, if possible somehow?
I don't know of any way to set up the scenario as-is - could refactor for more testability with stubbing/mocking.