-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
backport: finish merging 25001 #6531
base: develop
Are you sure you want to change the base?
Conversation
Base32/base64 are mechanisms for encoding binary data. That they'd decode to a string is just bizarre. The fact that they'd do that based on the type of input arguments even more so.
WalkthroughThe provided pull request introduces a comprehensive set of changes across multiple source files in the Bitcoin codebase, focusing on improving string handling, error management, and performance. The modifications primarily revolve around three key aspects:
These modifications aim to enhance code clarity, improve performance, and strengthen error handling throughout the Bitcoin implementation, demonstrating a systematic approach to code modernization. Finishing Touches
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Nitpick comments (6)
src/util/string.h (1)
79-87
: Consider adding noexcept specifierThe Join template functions could benefit from noexcept specification where applicable.
-template <typename T, typename T2> -T Join(const std::vector<T>& list, const T2& separator) +template <typename T, typename T2> +T Join(const std::vector<T>& list, const T2& separator) noexcept(noexcept(T{}))src/util/strencodings.h (1)
67-67
: Improved error handling with std::optional return typeThe change from output parameters to
std::optional
return type forDecodeBase64
andDecodeBase32
functions improves error handling and makes the API more modern and safer.Consider adding documentation to clarify what conditions would cause the functions to return an empty optional.
Also applies to: 70-71
src/util/strencodings.cpp (1)
205-210
: Comprehensive Base32 padding handlingThe Base32 padding logic handles all valid cases (1, 3, 4, or 6 padding characters) explicitly and safely.
Consider adding a comment explaining why these specific padding lengths are valid for Base32.
src/rpc/evo.cpp (2)
818-820
: Improve error handling for base64 signature decodingThe code now properly handles base64 decoding errors using std::optional, providing better error handling and safety.
Consider extracting the error message to a constant to maintain consistency across the codebase:
static const char* BASE64_DECODE_ERROR = "failed to decode base64 ready signature for protx"; if (!opt_vchSig.has_value()) throw JSONRPCError(RPC_INTERNAL_ERROR, BASE64_DECODE_ERROR);
880-884
: Improve error handling for base64 signature parsingThe code now properly handles base64 decoding errors using std::optional and provides a more specific error message.
Consider making the error message more descriptive to help users understand what went wrong:
if (!opt_vchSig.has_value()) { throw JSONRPCError(RPC_INVALID_PARAMETER, "The provided signature is not a valid base64 string"); }src/test/util_tests.cpp (1)
2697-2703
: Add test cases for RemovePrefixView functionNew test cases added to verify the RemovePrefixView functionality with various input combinations.
Consider adding more edge cases to improve test coverage:
BOOST_CHECK_EQUAL(RemovePrefixView("foo/bar", "foo/"), "bar"); BOOST_CHECK_EQUAL(RemovePrefixView("foo/bar/", "foo/bar/"), ""); BOOST_CHECK_EQUAL(RemovePrefixView("foo/bar/baz", "foo/bar/baz/"), "foo/bar/baz");
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (26)
src/base58.cpp
(2 hunks)src/bitcoin-tx.cpp
(1 hunks)src/httprpc.cpp
(1 hunks)src/httpserver.cpp
(1 hunks)src/i2p.cpp
(1 hunks)src/netaddress.cpp
(3 hunks)src/netbase.cpp
(5 hunks)src/psbt.cpp
(1 hunks)src/psbt.h
(1 hunks)src/qt/walletframe.cpp
(2 hunks)src/rpc/evo.cpp
(2 hunks)src/rpc/governance.cpp
(3 hunks)src/stacktraces.cpp
(1 hunks)src/test/base32_tests.cpp
(1 hunks)src/test/base64_tests.cpp
(2 hunks)src/test/fuzz/base_encode_decode.cpp
(2 hunks)src/test/fuzz/http_request.cpp
(1 hunks)src/test/fuzz/psbt.cpp
(2 hunks)src/test/fuzz/string.cpp
(2 hunks)src/test/util_tests.cpp
(2 hunks)src/util/message.cpp
(1 hunks)src/util/moneystr.cpp
(1 hunks)src/util/strencodings.cpp
(9 hunks)src/util/strencodings.h
(10 hunks)src/util/string.h
(3 hunks)src/util/system.cpp
(1 hunks)
🧰 Additional context used
🪛 GitHub Actions: Clang Diff Format Check
src/rpc/evo.cpp
[warning] 816-816: Code formatting issue: Conditional statement needs to be split into multiple lines
[warning] 877-877: Code formatting issue: Missing space after variable declaration
🔇 Additional comments (47)
src/test/base32_tests.cpp (2)
25-27
: LGTM! Improved error handling approachThe transition from bool* to std::optional for DecodeBase32 results in cleaner and more idiomatic C++ code. The use of BOOST_REQUIRE ensures immediate test failure on decode errors.
31-34
: LGTM! Comprehensive null character handling testsGood coverage of edge cases for null character handling, including:
- Middle of string
- Valid input
- After valid base32 string
- Invalid size scenarios
src/test/base64_tests.cpp (2)
22-24
: LGTM! Consistent error handling improvementThe changes align with the base32 updates, using std::optional for cleaner error handling.
38-41
: LGTM! Comprehensive null character validationGood set of test cases covering various null character scenarios in base64 strings.
src/test/fuzz/base_encode_decode.cpp (3)
25-25
: Performance improvement using TrimStringViewGood optimization by using TrimStringView instead of TrimString to avoid unnecessary string copies.
35-39
: LGTM! Consistent Base32 decoding patternThe changes align with the new error handling approach using std::optional.
42-44
: LGTM! Consistent Base64 decoding patternThe changes maintain consistency with the Base32 implementation.
src/util/moneystr.cpp (1)
43-43
: LGTM! Consistent string validationThe change from ValidAsCString to ContainsNoNUL provides more precise validation and maintains consistency with similar changes across the codebase.
src/util/message.cpp (2)
38-39
: LGTM! Improved error handling with std::optionalThe change from boolean flag to std::optional for DecodeBase64 result improves code clarity and error handling.
44-44
: Verify proper error handling for RecoverCompactWhile the dereferencing of signature_bytes is safe due to the prior check, consider adding error handling for RecoverCompact failure.
src/test/fuzz/psbt.cpp (1)
26-27
: LGTM! Improved type safety in fuzzing testsThe changes enhance type safety by:
- Using an intermediate variable for the random string
- Explicitly converting to byte span using MakeByteSpan
Also applies to: 74-75
src/test/fuzz/http_request.cpp (1)
57-57
: LGTM! More explicit string constructionThe change improves code clarity by using explicit std::string construction instead of relying on implicit conversion.
src/util/string.h (4)
32-39
: LGTM! Optimized string trimming with string_viewThe new TrimStringView implementation properly handles empty results and avoids unnecessary string allocations.
42-45
: LGTM! Clean separation of view and string operationsGood practice to provide both string_view and string versions of the trim operation.
47-58
: LGTM! Consistent pattern for prefix removalFollowing the same pattern as trim operations with separate view and string versions.
102-107
: LGTM! Improved null character detectionThe new ContainsNoNUL function is more explicit about its purpose and uses modern C++ features.
src/base58.cpp (2)
129-132
: LGTM! The validation change improves clarity.The change from
ValidAsCString
toContainsNoNUL
makes the validation more focused and explicit about what it's checking.
163-166
: LGTM! Consistent validation approach.The validation change is consistent with the
DecodeBase58
function above.src/qt/walletframe.cpp (4)
252-252
: LGTM! Better type for binary data.Changed from
std::string
tostd::vector<unsigned char>
, which is more appropriate for handling binary PSBT data.
256-261
: LGTM! Improved error handling with std::optional.The change to use
std::optional
for base64 decoding provides clearer error handling and better type safety.
272-272
: LGTM! Direct binary reading.Using
std::istream_iterator<unsigned char>
provides direct binary reading without string conversion.
277-277
: LGTM! Consistent byte span usage.Using
MakeByteSpan
adapts the data correctly for the updatedDecodeRawPSBT
interface.src/test/fuzz/string.cpp (1)
43-43
: LGTM! Consistent validation approach.The change from
ValidAsCString
toContainsNoNUL
aligns with similar changes in other files, making the validation intent more explicit.src/psbt.cpp (2)
346-351
: LGTM! Improved error handling with std::optional.The change to use
std::optional
for base64 decoding provides better type safety and clearer error handling.
354-356
: LGTM! Better type safety with Span.Changed function signature to use
Span<const std::byte>
, providing better type safety for binary data handling.src/util/strencodings.h (3)
238-244
: Good addition of IntIdentity helperThe
IntIdentity
helper class provides a clean default implementation for theinfn
parameter inConvertBits
. This improves code clarity and maintainability.
248-249
: Verify ConvertBits template usage with new IntIdentityThe
ConvertBits
template function now uses the newIntIdentity
helper. We should verify all existing uses remain compatible.✅ Verification successful
ConvertBits template modification is backward compatible
All existing uses of ConvertBits are compatible with the new IntIdentity parameter as they rely on the default value, requiring no changes to the calling code.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Search for all uses of ConvertBits to verify compatibility rg "ConvertBits<" --type cppLength of output: 648
97-102
: Verify the behavior change in LocaleIndependentAtoiThe function now uses
TrimStringView
andstd::from_chars
instead of the C locale-dependent functions. While this is a good modernization, we should verify the behavior is identical.✅ Verification successful
✓ Behavior change in LocaleIndependentAtoi is correct
The function's behavior is identical to the C locale-dependent functions, as verified by:
- Comprehensive test suite covering all edge cases
- Explicit fuzz test verification against legacy behavior
- Consistent usage patterns across the codebase
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Search for all calls to LocaleIndependentAtoi to verify usage patterns rg -A 2 "LocaleIndependentAtoi"Length of output: 10089
src/httprpc.cpp (1)
174-178
: Improved error handling in RPCAuthorizedThe changes improve both efficiency and safety:
- Using
std::string_view
reduces unnecessary copying- Using
std::optional
for Base64 decoding makes error handling more explicit- Early return on decoding failure simplifies the control flow
src/i2p.cpp (1)
72-76
: Streamlined Base64 decoding with std::optionalThe changes improve the code by:
- Using
std::optional
for clearer error handling- Using
std::move
to avoid unnecessary copying of the decoded data- Providing a more descriptive error message on failure
src/util/strencodings.cpp (4)
150-153
: Robust padding handling in Base64 decodingThe padding removal logic is now more explicit and safer, properly handling one or two padding characters.
156-162
: Efficient Base64 decoding implementationThe implementation is improved with:
- Proper memory pre-allocation
- Use of ConvertBits for the actual conversion
- Clear error handling through the return value
213-222
: Efficient Base32 decoding implementationSimilar improvements to Base64 decoding:
- Proper memory pre-allocation
- Use of ConvertBits for conversion
- Clear error handling
494-494
: Verify ParseByteUnits with new string_view parameterThe function now takes std::string_view, which is more efficient but we should verify all callers handle the lifetime correctly.
✅ Verification successful
String view lifetime usage is safe
All current usages of
ParseByteUnits
maintain proper string_view lifetime:
- Test cases use string literals
- Production code in
init.cpp
safely uses temporary strings🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Search for all calls to ParseByteUnits rg "ParseByteUnits\(" --type cppLength of output: 2251
src/httpserver.cpp (1)
275-279
: LGTM! Improved error handling for Base64 decoding.The changes enhance robustness and readability by:
- Using
std::optional
for clearer error handling- Employing string iterator for more idiomatic delimiter search
- Properly handling all error cases with early returns
src/stacktraces.cpp (1)
430-435
: LGTM! Enhanced error handling for crash info deserialization.The changes improve robustness by:
- Using
std::optional
for explicit error handling- Adding proper validation of the decoded buffer
- Using clear variable naming with
opt_buf
src/netbase.cpp (1)
147-147
: LGTM! Consistent input validation across network functions.The changes standardize string validation by using
ContainsNoNUL
consistently across:
LookupIntern
LookupHost
Lookup
LookupNumeric
LookupSubNet
This provides a more focused check for null characters in input strings.
Also applies to: 176-176, 194-194, 219-219, 671-671
src/bitcoin-tx.cpp (1)
226-226
: LGTM! Performance optimization in string handling.The change from
TrimString
toTrimStringView
potentially improves performance by avoiding unnecessary string copies during parsing.src/netaddress.cpp (4)
214-214
: LGTM! Improved string validation.The change from
ValidAsCString
toContainsNoNUL
is a good improvement as it makes the validation intent clearer.
244-247
: LGTM! Improved readability with descriptive variable names.The use of descriptive variable names (
input_pubkey
,input_checksum
,input_version
) improves code readability.
283-290
: LGTM! Consistent error handling pattern.The changes in
SetI2P
follow the same pattern asSetTor
, maintaining consistency in error handling.
238-244
: Verify error handling in base32 decoding.The change to use
std::optional
for base32 decoding improves error handling, but we should verify that all error cases are properly handled.✅ Verification successful
Base32 decoding error handling is properly implemented
The implementation in
DecodeBase32
returnsstd::optional
for all error cases (invalid length, invalid characters, conversion failures) and all callers properly check for nullopt before using the result. The test suite includes comprehensive validation of error cases.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Search for other base32 decoding error handling patterns rg -A 3 "DecodeBase32\(" | grep -v "if.*has_value"Length of output: 2565
Script:
#!/bin/bash # Check the implementation of DecodeBase32 for error cases ast-grep --pattern 'DecodeBase32(std::string_view str) { $$$ }'Length of output: 67
Script:
#!/bin/bash # Get the implementation of DecodeBase32 rg -A 30 "^std::optional<std::vector<unsigned char>> DecodeBase32\(std::string_view str\)" src/util/strencodings.cppLength of output: 2053
Script:
#!/bin/bash # Get the complete implementation including the return statement rg -A 40 "^std::optional<std::vector<unsigned char>> DecodeBase32\(std::string_view str\)" src/util/strencodings.cppLength of output: 2191
src/psbt.h (1)
917-917
: LGTM! Improved type safety with Span.The change from
std::string
toSpan<const std::byte>
for raw PSBT data improves type safety and makes the API more explicit about its binary data handling.src/rpc/governance.cpp (2)
425-428
: LGTM! Improved error handling with optional.The change to use
std::optional
for base64 decoding improves error handling and makes the success/failure state more explicit.
Line range hint
962-977
: LGTM! Consistent error handling pattern.The changes in
voteraw
follow the same pattern asSignVote
, maintaining consistency in error handling across the codebase.src/util/system.cpp (1)
907-908
: LGTM! Performance optimization with string_view.The change to use
std::string_view
avoids unnecessary string copies during config parsing, which is a good performance optimization.src/test/util_tests.cpp (1)
281-291
: Update string trimming tests to use TrimStringViewTest cases have been updated to use TrimStringView, which is more efficient than TrimString as it avoids unnecessary string copies.
@@ -422,10 +422,10 @@ static bool SignVote(const CWallet& wallet, const CKeyID& keyID, CGovernanceVote | |||
return false; | |||
} | |||
bool failed = true; |
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.
bool failed = true; |
@@ -427,12 +427,12 @@ std::string GetCrashInfoStrFromSerializedStr(const std::string& ciStr) | |||
static uint64_t basePtr = GetBaseAddress(); | |||
|
|||
bool dataInvalid = false; |
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.
bool dataInvalid = false; |
Issue being fixed or feature implemented
This was partially done earlier; do the remaining commits
What was done?
see commits
How Has This Been Tested?
built locally
Breaking Changes
none
Checklist:
Go over all the following points, and put an
x
in all the boxes that apply.