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

Sync/master202204 #80

Merged
merged 1,644 commits into from
Apr 5, 2022
Merged

Sync/master202204 #80

merged 1,644 commits into from
Apr 5, 2022

Conversation

van-orton
Copy link
Collaborator

Description

Syncing the updated code to master branch. Builds for major OSes were made using code from this branch.
Separate branch/tag (0.1.8) would be created to mark code version used for release.

MarcoFalke and others added 30 commits November 9, 2021 19:56
…lMinFee and minRelayTxFee.

This will provide better estimates which would be closer to fee paid in actual
transactions.
The test has also been changed such that when the node is restarted with a
high mempoolMinFee, the estimatesmartfee still returns a feeRate greater
than or equal to the mempoolMinFee, minRelayTxFee.(just like the feeRate of actual transactions)
Bitcoin script opcodes are equal on all chains (main and test) anyway.

Can be reviewed with "--word-diff-regex=.".
Can be reviewed with "--word-diff-regex=.".
In preparation for introducing the pimpl pattern to addrman, move all function
bodies out of the header file.

Review hint: use git diff --color-moved=dimmed-zebra
--color-moved-ws=ignore-all-space
…IfInvolvingMe() regarding rescanning_old_block parameter
Also move `Check` and `ForceCheckAddrman` to be after the `FunctionName_` functions.

Review hint: use git diff --color-moved=dimmed-zebra
--color-moved-ws=ignore-all-space
Update so the internal function signature matches the external one, as is the
case for the other addrman functions.
Maintain comments on the external interfaces rather than on the internal
functions that implement them.
Review hint: git diff --color-moved=dimmed-zebra
--color-moved-ws=ignore-all-space
CAddrInfo objects are an implementation detail of how AddrMan manages and adds
metadata to different records. Encapsulate this logic by updating Select &
SelectTriedCollision to return the additional info that the callers need.
Since knowledge of CAddrInfo is limited to callsites that import
addrman_impl.h, only objects in addrman.cpp or the tests have access. Thus we
can remove calling them friends and make the members public.
…ion.

Introduce the pimpl pattern for CAddrMan to separate the implementation details
from the externally used object representation. This reduces compile-time
dependencies and conceptually clarifies AddrMan's interface from the
implementation specifics.

Since the unit & fuzz tests currently rely on accessing CAddrMan internals, this
commit introduces addrman_impl.h, which is exclusively imported by addrman.cpp
and test files.

Review hint: git diff --color-moved=dimmed-zebra
--color-moved-ws=ignore-all-space
Now that no bitcoind callers require knowledge of the CAddrInfo object, it can
be moved into the test-only header file.

Review hint: use git diff --color-moved=dimmed-zebra
--color-moved-ws=ignore-all-space
We can avoid many unnecessary std::vector allocations by changing
CBloomFilter to take Spans instead of std::vector's for the `insert`
and `contains` operations.

CBloomFilter currently converts types such as CDataStream and uint256
to std::vector on `insert` and `contains`. This is unnecessary because
CDataStreams and uint256 are already std::vectors internally. We just
need a way to point to the right data within those types. Span gives
us this ability.

Signed-off-by: William Casarin <[email protected]>
-BEGIN VERIFY SCRIPT-
git grep -l CAddrInfo src/ | xargs sed -i 's/CAddrInfo/AddrInfo/g'
-END VERIFY SCRIPT-
MarcoFalke and others added 26 commits November 11, 2021 10:19
Now that boost has been updated > 1.60, we can simplify how we get
wallet path relative to wallet_dir by using:
`boost::filesystem::lexically_relative`
The bug was introduced in dcd6eeb64adb2b532f5003cbb86ba65b3c08a87b.
This is temporary solution until for now.
Fix test_BGL_qt
The issue with Sqlite3 assert error was traced to SQLiteBatch::SQLiteBatch
constructor omitting SetupSQLStatements function call.
Fixed qt wallet crashing issue and resolved qt test crashing when using
Sqlite3
It fails relocation related issue, and the linker advises to use -fpie
@van-orton van-orton merged commit 29eed96 into master Apr 5, 2022
@van-orton van-orton deleted the sync/master202204 branch April 5, 2022 14:28
@van-orton
Copy link
Collaborator Author

@janus code synced. Branch janus/Sync_31Oct2021 was used. Some small fixes to make release builds + branding updated.
You can delete or resync your branch to master (if there were later commits) and delete it later (would delete this branch too)

@janus
Copy link
Collaborator

janus commented Apr 6, 2022

@janus code synced. Branch janus/Sync_31Oct2021 was used. Some small fixes to make release builds + branding updated. You can delete or resync your branch to master (if there were later commits) and delete it later (would delete this branch too)

Great Job. Well done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.