13 May 2024 |
gitlab-bot | [nexa/nexa] ptschip
opened
merge request !510: Draft: [Depends on 508] For post block processing do SyncWithWallets in a different thread
For very large blocks this prevents us from having to pause tx admission longer than necessary.
For a 100MB block it saves roughly 4 seconds from post block processing.
| 10:38:16 |
14 May 2024 |
gitlab-bot | [nexa/nexa] ptschip
opened
merge request !511: Small perf fixes to minerpolicy
- use references instead of copying the hash values all the time
| 10:07:37 |
gitlab-bot | [nexa/nexa] gandrewstone
approved
merge request !503: Compile Nexa for ubuntu 23.10 | 21:47:30 |
gitlab-bot | [nexa/nexa] gandrewstone
merged
merge request !503: Compile Nexa for ubuntu 23.10 | 21:47:36 |
gitlab-bot | [nexa/nexa] gandrewstone
merged
merge request !506: Remove priority from CUnknownObj | 21:52:05 |
gitlab-bot | [nexa/nexa] gandrewstone
approved
merge request !507: Prevent having to re-aquire the mempool locks when applying deltas | 22:11:00 |
gitlab-bot | [nexa/nexa] gandrewstone
merged
merge request !507: Prevent having to re-aquire the mempool locks when applying deltas | 22:11:07 |
15 May 2024 |
gitlab-bot | [nexa/nexa] ptschip
approved
merge request !501: have getdata block invs return something (notfound or reject) on error. | 08:06:20 |
gitlab-bot | [nexa/nexa] ptschip
changed the title of
merge request !509 to Change setMerkleBranch() to setBlockChainPos() | 08:07:50 |
gitlab-bot | [nexa/nexa] gandrewstone
merged
merge request !501: have getdata block invs return something (notfound or reject) on error. | 13:30:55 |
gitlab-bot | [nexa/nexa] gandrewstone
approved
merge request !504: A few performance improvements for getblocktemplate | 13:32:07 |
gitlab-bot | [nexa/nexa] gandrewstone
merged
merge request !504: A few performance improvements for getblocktemplate | 13:32:14 |
gitlab-bot | [nexa/nexa] gandrewstone
approved
merge request !509: Change setMerkleBranch() to setBlockChainPos() | 13:32:48 |
gitlab-bot | [nexa/nexa] gandrewstone
merged
merge request !509: Change setMerkleBranch() to setBlockChainPos() | 13:32:59 |
gitlab-bot | [nexa/nexa] gandrewstone
approved
merge request !511: Small perf fixes to minerpolicy | 14:02:20 |
gitlab-bot | [nexa/nexa] gandrewstone
merged
merge request !511: Small perf fixes to minerpolicy | 14:02:30 |
gitlab-bot | [nexa/nexa] gandrewstone
approved
merge request !508: Process orphans in the commit tx thread rather than the block processing thread | 14:50:37 |
gitlab-bot | [nexa/nexa] gandrewstone
merged
merge request !508: Process orphans in the commit tx thread rather than the block processing thread | 14:50:44 |
16 May 2024 |
gitlab-bot | [nexa/nexa] ptschip
changed the title of
merge request !510 to Draft: For post block processing do SyncWithWallets in a different thread | 07:11:58 |
gitlab-bot | [nexa/nexa] ptschip
changed the title of
merge request !510 to For post block processing - do SyncWithWallets() in a different thread | 11:08:50 |
gitlab-bot | [nexa/nexa] ptschip
changed the title of
merge request !510 to Improve post block processing performance - do SyncWithWallets() in a different thread | 11:09:37 |
gitlab-bot | [nexa/nexa] gandrewstone
opened
merge request !512: Remove constraint on maximum stack width at an upgrade (hard fork) date
This MR organizes the script flags code in preparation for new features by consolidating where MANDATORY and STANDARD features are defined. It then creates a new script flag that, when active, relaxes the script stack width restriction of 520 bytes. It adds tests for large stack widths and an activation test (that can be extended for many script-related upgrade features).
This MR therefore allows the total RAM used in script stacks to increase in an unconstrained manner -- its not a viable upgrade on its own. Another MR will be created that limits the total size of the script stack.
Since this functionality is "off" until a currently-unscheduled hard fork upgrade occurs, it is fine to implement and merge these two features (relaxing the stack width limitation, and adding a total size limitation) separately.
| 21:14:02 |
17 May 2024 |
gitlab-bot | [nexa/nexa] sickpig
opened
merge request !513: Add clang-format 17.0.6 to the list of tested one
clang-format 15.0.X is not available anymore via brew on macOS, so I tested the current available version (17.0.6) and I did not find any difference between the 2 in terms of formatting layout on the nexa code base.
Furthermore a duplicated settings (AlignTrailingComments: false) has been removed from clang-format configuration file.
| 16:11:46 |
gitlab-bot | [nexa/nexa] sickpig
opened
merge request !514: Fix building on FreeBSD and update the documentation
Mostly I just had to add FreeBSD to the list of supported operating
systems in various places. In one place I had to change the path to find
the path of the executable because it's different in FreeBSD.
Unfortunately in FreeBSD the only easy way (see
https://stackoverflow.com/a/1024937/428740) to get this information
programtically requires configuring procfs which I have documented. I
searched the code and it's only used in one place if you use rostrum.
(this is a port from BCHU)
| 16:16:41 |
gitlab-bot | [nexa/nexa] sickpig
opened
merge request !515: Use boolean rather than bitwise operators
Even thou using bitwise operator will yield the correct result,
it is more readable to use boolean operators when dealing with
boolean variables.
| 16:28:03 |
22 May 2024 |
gitlab-bot | [nexa/nexa] gandrewstone
approved
merge request !515: Use boolean rather than bitwise operators | 17:51:24 |
gitlab-bot | [nexa/nexa] gandrewstone
merged
merge request !515: Use boolean rather than bitwise operators | 17:51:29 |
gitlab-bot | [nexa/nexa] gandrewstone
approved
merge request !514: Fix building on FreeBSD and update the documentation | 17:52:05 |
gitlab-bot | [nexa/nexa] gandrewstone
merged
merge request !514: Fix building on FreeBSD and update the documentation | 17:52:17 |
gitlab-bot | [nexa/nexa] gandrewstone
approved
merge request !513: Add clang-format 17.0.6 to the list of tested one | 17:52:43 |