rippled v1.1.0 Changes [Waiting for official release] #448
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- consolidated initial install dependencies - BOOST_ROOT dir will be incorrectly set if your username is not ubuntu - (Revoved by @mDuo13: automatically setting number of processors to use to compile Boost libraries to half of what users would have) - git log to now show v1.0.1 - numbering changes
Boost 1.68.0 is not compatible with rippled 1.1.0 due to some changes to Boost.Beast. Versions of Boost older than 1.67.0 are not compatible with rippled 1.1.0 because they do not include Boost.Beast. Only Boost 1.67.0 is compatible, so I updated the build instructions to be clearer about this.
Addresses changes implemented in XRPLF/rippled#2642 - Missing fields result in `invalidParams` - Accounts not found in the ledger result in `{src/dst}ActNotFound`
This was referenced Aug 21, 2018
|
@jbheron If you could, please peer review just |
ryangyoung
reviewed
Aug 24, 2018
|
|
||
| `rippled` servers with full transaction history (or a very large amount of transaction history) and a database that was initially created with a `rippled` version earlier than 0.40.0 (released January 2017) may encounter a problem with their SQLite database page size that stops the server from operating properly. Servers that store only recent transaction history (the default configuration) and servers whose database files were created with `rippled` version 0.40.0 and later are not likely to encounter this problem. | ||
|
|
||
| This document describes steps to detect and correct this problem if it arises. |
|
|
||
| ## Background | ||
|
|
||
| `rippled` servers store a copy of their transaction history in a SQLite database. Before version 0.40.0, `rippled` configured this database to have a capacity of roughly 2TB. For most uses, this is plenty. However, full transaction history back to ledger 32570 (the oldest ledger version available in the production XRP Ledger history) is likely to exceed this exceed the SQLite database capacity. `rippled` servers version 0.40.0 and later create their SQLite database files with a larger capacity, so they are unlikely to encounter this problem. |
There was a problem hiding this comment.
ledger 32570 (the oldest ledger version available in the production XRP Ledger history
Might be a good place to link to the explanation of this to your footnote in the consensus intro.
There was a problem hiding this comment.
I'm going to hold off on that for now, because:
- That content isn't in this branch yet because it's from a PR started after this one. I'd have to rebase onto master.
- I don't think the link adds much info beyond what's already mentioned in the parenthesis, and it might distract from the task at hand.
This was referenced Aug 24, 2018
Per XRPLF/rippled#2657, the signing commands should not be used as public methods and this usage is disabled in rippled v1.1.0 and later.
Update signing command documentation
|
Per XRPLF/rippled#2657, the signing commands should not be used as public methods and this usage is disabled in rippled v1.1.0 and later. The latest commit addresses this:
I left the signing methods in the "public" category for the following reasons:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Combines the following PRs with changes relating to
rippled1.1.0:--unittest-ipv6commandline option)Also adds a couple minor changes:
masterinstead ofdevelopfor rippled source code links. Update a few line numbers accordingly. (The line numbers for DepositPreauth objects are speculatively set to match what's expected to be merged to master based on the release candidate.)deposit_authorizedmethod's error codes to match deposit_authorized gives error if source not in ledger (#2640) rippled#2642This PR needs minimal modifications after the
rippled1.1.0 release: