| Age | Commit message (Collapse) | Author |
|---|
|
|
|
cc16d99 [trivial] Fix typos in comments (practicalswift)
|
|
Also, update the clang format file to reflect the current coding
style mentioned in the developer notes.
|
|
|
|
This contains a few hacks very specific to Qt's buildsystem. These can be
reverted once we split the build between native and target builds.
Qt's build contains a circular dependency when not using a system zlib.
By far the easiest fix is to switch to a system zlib, rather than Qt's own.
However, that confuses Qt's cross build which assumes that when using a system
zlib, it should also find a system (native) zlib for native tools. The build
breaks if that zlib is not present.
To solve this:
1. Always use a system zlib rather than the one provided by qt
2. Set force_bootstrap, which instructs the build tools to be built as though
we're cross-compiling (build != target)
3. For build tools, use qt's internal zlib so that a native zlib is not
required.
Step 3 means that if any zlib headers are found by the native build, it will
confuse Qt's internal zlib build. So we also need to make sure that the target
headers/libs aren't found. To do so, specify that our
cflags/cxxflags/cppflags/ldflags only apply for non-host builds.
|
|
qt5.7 changed the location of some of its symbols, creating a circular
dependency in Qt5Core. Rather than trying to fix that up, build our own zlib
rather than having it built for us.
|
|
|
|
|
|
fab035f qa: Actually test assertions in pruning.py (MarcoFalke)
|
|
04b8773 [Qt] fix transaction details output-index to reflect vout index (Jonas Schnelli)
|
|
|
|
The result value indicates the actual fee on the transaction that was replaced. But there is an error message which uses the description 'oldfee' to refer to the original fee rate applied to the new transaction's estimated max size. It was confusing that two different uses of 'oldfee' had two different numeric values.
|
|
Have wallet's default bump value be higher than the default incrementalRelayFee to future proof against changes to incremental relay fee. Only applies when not setting the fee rate directly.
|
|
Also refactor to use wrapper for stop_node
|
|
Use the wallet's fee calculation logic to properly clamp fee against minimums and maximums when calculating the fee for a bumpfee transaction. Unless totalFee is explictly given, in which case, manually check against min, but do nothing to adjust given fee.
In all cases do a final check against maxTxFee (after adding any incremental amount).
|
|
|
|
de1ae32 Exclude RBF txs from fee estimation (Alex Morcos)
|
|
8ff8d21 Send final alert message to older peers after connecting. (Gregory Maxwell)
|
|
c36ec71 depends: qt: disable printer for all platforms, not just osx (Cory Fields)
|
|
44f2baa Do not shadow local variable named `tx`. (Pavel Janík)
|
|
with bumpfee
5a00659 [wallet] Clarify getbalance help string to explain interaction with bumpfee (Russell Yanofsky)
|
|
99464bc net: Consistently use GetTimeMicros() for inactivity checks (Suhas Daftuar)
|
|
|
|
2f10f06 qa: Increase a sync_blocks timeout in pruning.py (Suhas Daftuar)
|
|
|
|
- The last-timestamp-encountered variable wasn’t being used properly. Rewrite code to properly allow for new blockchain files to be written when split by month.
- Properly set a blockchain file’s access and modify times.
- Add a “debug output” option to quiet certain output that might not always be desirable.
- Update the README.
|
|
|
|
The use of mocktime in test logic means that comparisons between
GetTime() and GetTimeMicros()/1000000 are unreliable since the former
can use mocktime values while the latter always gets the system clock;
this changes the networking code's inactivity checks to consistently
use the system clock for inactivity comparisons.
Also remove some hacks from setmocktime() that are no longer needed,
now that we're using the system clock for nLastSend and nLastRecv.
|
|
|
|
|
|
|
|
ac9a846 [Trivial] fix logging typo in FlushStateToDisk() (John Newbery)
|
|
|
|
be31a2b [Trivial] Update license year range to 2017 (Lauda)
|
|
094e4b3 Better document usage of SyncTransaction (Alex Morcos)
4afbde6 Introduce MemPoolConflictRemovalTracker (Alex Morcos)
ff25c32 mempool: add notification for added/removed entries (Wladimir J. van der Laan)
|
|
fa4d478 qt: Use nPowTargetSpacing constant (MarcoFalke)
|
|
The same as #7363.
|
|
|
|
Analogue to ConnectTrace that tracks transactions that have been removed from the mempool due to conflicts and then passes them through SyncTransaction at the end of its scope.
|
|
Add notification signals to make it possible to subscribe to mempool
changes:
- NotifyEntryAdded(CTransactionRef)>
- NotifyEntryRemoved(CTransactionRef, MemPoolRemovalReason)>
Also add a mempool removal reason enumeration, which is passed to the
removed notification based on why the transaction was removed from
the mempool.
|
|
bd92f24 [bugfix] save feeDelta instead of priorityDelta in DumpMempool (Alex Morcos)
|
|
in reorg'd chains
7ba0a00 Testing: listsinceblock should not use orphan block height. (Karl-Johan Alm)
ee5c1ce Bug-fix: listsinceblock: use closest common ancestor when a block hash was provided for a chain that was not the main chain. (Karl-Johan Alm)
|
|
Documentation change only, no change in behavior.
|
|
5cdf106 Remove redundant semicolons in Python code (practicalswift)
|
|
116419e Don't overwrite validation state with corruption check (Alex Morcos)
|
|
9899893 Move wallet callbacks into cs_main (this effectively reverts #7946) (Matt Corallo)
|
|
5c66d41 [Trivial] Grammar and typo correction (Lauda)
|
|
Minor corrections in src\test\* .
|
|
addrman_tests.cpp
afab9f4 [test] Avoid potential NULL pointer dereference in addrman_tests.cpp (practicalswift)
|
|
|
