|
|
|
// Copyright 2020 The go-ethereum Authors
|
|
|
|
// This file is part of go-ethereum.
|
|
|
|
//
|
|
|
|
// go-ethereum is free software: you can redistribute it and/or modify
|
|
|
|
// it under the terms of the GNU General Public License as published by
|
|
|
|
// the Free Software Foundation, either version 3 of the License, or
|
|
|
|
// (at your option) any later version.
|
|
|
|
//
|
|
|
|
// go-ethereum is distributed in the hope that it will be useful,
|
|
|
|
// but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
// GNU General Public License for more details.
|
|
|
|
//
|
|
|
|
// You should have received a copy of the GNU General Public License
|
|
|
|
// along with go-ethereum. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
|
|
|
|
package utils
|
|
|
|
|
|
|
|
import (
|
|
|
|
"fmt"
|
|
|
|
|
|
|
|
"github.com/ethereum/go-ethereum/internal/flags"
|
|
|
|
"github.com/urfave/cli/v2"
|
|
|
|
)
|
|
|
|
|
|
|
|
var ShowDeprecated = &cli.Command{
|
|
|
|
Action: showDeprecated,
|
|
|
|
Name: "show-deprecated-flags",
|
|
|
|
Usage: "Show flags that have been deprecated",
|
|
|
|
ArgsUsage: " ",
|
|
|
|
Description: "Show flags that have been deprecated and will soon be removed",
|
|
|
|
}
|
|
|
|
|
|
|
|
var DeprecatedFlags = []cli.Flag{
|
|
|
|
NoUSBFlag,
|
|
|
|
LegacyWhitelistFlag,
|
cmd, core, eth, graphql, trie: no persisted clean trie cache file (#27525)
The clean trie cache is persisted periodically, therefore Geth can
quickly warmup the cache in next restart.
However it will reduce the robustness of system. The assumption is
held in Geth that if the parent trie node is present, then the entire
sub-trie associated with the parent are all prensent.
Imagine the scenario that Geth rewinds itself to a past block and
restart, but Geth finds the root node of "future state" in clean
cache then regard this state is present in disk, while is not in fact.
Another example is offline pruning tool. Whenever an offline pruning
is performed, the clean cache file has to be removed to aviod hitting
the root node of "deleted states" in clean cache.
All in all, compare with the minor performance gain, system robustness
is something we care more.
1 year ago
|
|
|
CacheTrieJournalFlag,
|
|
|
|
CacheTrieRejournalFlag,
|
|
|
|
LegacyDiscoveryV5Flag,
|
|
|
|
}
|
|
|
|
|
|
|
|
var (
|
|
|
|
// Deprecated May 2020, shown in aliased flags section
|
|
|
|
NoUSBFlag = &cli.BoolFlag{
|
|
|
|
Name: "nousb",
|
|
|
|
Usage: "Disables monitoring for and managing USB hardware wallets (deprecated)",
|
|
|
|
Category: flags.DeprecatedCategory,
|
|
|
|
}
|
|
|
|
// Deprecated March 2022
|
|
|
|
LegacyWhitelistFlag = &cli.StringFlag{
|
|
|
|
Name: "whitelist",
|
|
|
|
Usage: "Comma separated block number-to-hash mappings to enforce (<number>=<hash>) (deprecated in favor of --eth.requiredblocks)",
|
|
|
|
Category: flags.DeprecatedCategory,
|
|
|
|
}
|
|
|
|
// Deprecated July 2023
|
cmd, core, eth, graphql, trie: no persisted clean trie cache file (#27525)
The clean trie cache is persisted periodically, therefore Geth can
quickly warmup the cache in next restart.
However it will reduce the robustness of system. The assumption is
held in Geth that if the parent trie node is present, then the entire
sub-trie associated with the parent are all prensent.
Imagine the scenario that Geth rewinds itself to a past block and
restart, but Geth finds the root node of "future state" in clean
cache then regard this state is present in disk, while is not in fact.
Another example is offline pruning tool. Whenever an offline pruning
is performed, the clean cache file has to be removed to aviod hitting
the root node of "deleted states" in clean cache.
All in all, compare with the minor performance gain, system robustness
is something we care more.
1 year ago
|
|
|
CacheTrieJournalFlag = &cli.StringFlag{
|
|
|
|
Name: "cache.trie.journal",
|
|
|
|
Usage: "Disk journal directory for trie cache to survive node restarts",
|
|
|
|
Category: flags.DeprecatedCategory,
|
cmd, core, eth, graphql, trie: no persisted clean trie cache file (#27525)
The clean trie cache is persisted periodically, therefore Geth can
quickly warmup the cache in next restart.
However it will reduce the robustness of system. The assumption is
held in Geth that if the parent trie node is present, then the entire
sub-trie associated with the parent are all prensent.
Imagine the scenario that Geth rewinds itself to a past block and
restart, but Geth finds the root node of "future state" in clean
cache then regard this state is present in disk, while is not in fact.
Another example is offline pruning tool. Whenever an offline pruning
is performed, the clean cache file has to be removed to aviod hitting
the root node of "deleted states" in clean cache.
All in all, compare with the minor performance gain, system robustness
is something we care more.
1 year ago
|
|
|
}
|
|
|
|
CacheTrieRejournalFlag = &cli.DurationFlag{
|
|
|
|
Name: "cache.trie.rejournal",
|
|
|
|
Usage: "Time interval to regenerate the trie cache journal",
|
|
|
|
Category: flags.DeprecatedCategory,
|
|
|
|
}
|
|
|
|
LegacyDiscoveryV5Flag = &cli.BoolFlag{
|
|
|
|
Name: "v5disc",
|
|
|
|
Usage: "Enables the experimental RLPx V5 (Topic Discovery) mechanism (deprecated, use --discv5 instead)",
|
|
|
|
Category: flags.DeprecatedCategory,
|
cmd, core, eth, graphql, trie: no persisted clean trie cache file (#27525)
The clean trie cache is persisted periodically, therefore Geth can
quickly warmup the cache in next restart.
However it will reduce the robustness of system. The assumption is
held in Geth that if the parent trie node is present, then the entire
sub-trie associated with the parent are all prensent.
Imagine the scenario that Geth rewinds itself to a past block and
restart, but Geth finds the root node of "future state" in clean
cache then regard this state is present in disk, while is not in fact.
Another example is offline pruning tool. Whenever an offline pruning
is performed, the clean cache file has to be removed to aviod hitting
the root node of "deleted states" in clean cache.
All in all, compare with the minor performance gain, system robustness
is something we care more.
1 year ago
|
|
|
}
|
|
|
|
)
|
|
|
|
|
|
|
|
// showDeprecated displays deprecated flags that will be soon removed from the codebase.
|
|
|
|
func showDeprecated(*cli.Context) error {
|
|
|
|
fmt.Println("--------------------------------------------------------------------")
|
|
|
|
fmt.Println("The following flags are deprecated and will be removed in the future!")
|
|
|
|
fmt.Println("--------------------------------------------------------------------")
|
|
|
|
fmt.Println()
|
|
|
|
for _, flag := range DeprecatedFlags {
|
|
|
|
fmt.Println(flag.String())
|
|
|
|
}
|
|
|
|
fmt.Println()
|
|
|
|
return nil
|
|
|
|
}
|