rename more things

frrist · frrist · commit 060241b5f06a · 2021-08-30T10:13:26.000-07:00
diff --git a/chain/find.go b/chain/find.go
@@ -73,7 +73,7 @@ func (g *GapIndexer) Run(ctx context.Context) error {
 	findLog.Infow("found gaps in epochs", "count", len(heightGaps))
 	findLog.Infow("found null rounds", "count", len(nulls))
 
-	// looks for entriest in the visor processing report table that have been skipped.
+	// looks for entriest in the lily processing report table that have been skipped.
 	skipGaps, err := g.findEpochSkips(ctx)
 	if err != nil {
 		return xerrors.Errorf("detecting skipped gaps: %w", err)
diff --git a/commands/daemon.go b/commands/daemon.go
@@ -36,15 +36,15 @@ var clientAPIFlags struct {
 
 var clientAPIFlag = &cli.StringFlag{
 	Name:        "api",
-	Usage:       "Address of visor api in multiaddr format.",
+	Usage:       "Address of lily api in multiaddr format.",
 	EnvVars:     []string{"LILY_API"},
 	Value:       "/ip4/127.0.0.1/tcp/1234",
 	Destination: &clientAPIFlags.apiAddr,
 }
 
 var clientTokenFlag = &cli.StringFlag{
 	Name:        "api-token",
-	Usage:       "Authentication token for visor api.",
+	Usage:       "Authentication token for lily api.",
 	EnvVars:     []string{"LILY_API_TOKEN"},
 	Value:       "",
 	Destination: &clientAPIFlags.apiToken,
@@ -58,7 +58,7 @@ var clientAPIFlagSet = []cli.Flag{
 
 type daemonOpts struct {
 	repo      string
-	bootstrap bool // TODO: is this necessary - do we want to run visor in this mode?
+	bootstrap bool // TODO: is this necessary - do we want to run lily in this mode?
 	config    string
 	genesis   string
 }
@@ -67,9 +67,9 @@ var daemonFlags daemonOpts
 
 var DaemonCmd = &cli.Command{
 	Name:  "daemon",
-	Usage: "Start a visor daemon process.",
-	Description: `Starts visor in daemon mode with its own blockstore.
-In daemon mode visor synchronizes with the filecoin network and runs jobs such
+	Usage: "Start a lily daemon process.",
+	Description: `Starts lily in daemon mode with its own blockstore.
+In daemon mode lily synchronizes with the filecoin network and runs jobs such
 as walk and watch against its local blockstore. This gives better performance
 than operating against an external blockstore but requires more disk space and
 memory.
@@ -79,10 +79,10 @@ and synchronized. Visor can use a copy of an already synchronized Lotus node
 repository or can initialize its own empty one and import a snapshot to catch
 up to the chain.
 
-To initialize an empty visor blockstore repository and import an initial
+To initialize an empty lily blockstore repository and import an initial
 snapshot of the chain:
 
-  visor init --repo=<path> --import-snapshot=<url>
+  lily init --repo=<path> --import-snapshot=<url>
 
 This will initialize a blockstore repository at <path> and import chain state
 from the snapshot at <url>. The type of snapshot needed depends on the type
@@ -100,7 +100,7 @@ Lotus documentation for full details.
 
 Once the repository is initialized, start the daemon:
 
-  visor daemon --repo=<path> --config=<path>/config.toml
+  lily daemon --repo=<path> --config=<path>/config.toml
 
 Visor will connect to the filecoin network and begin synchronizing with the
 chain. To check the synchronization status use 'visor sync status' or
@@ -121,7 +121,7 @@ Note that jobs are not persisted between restarts of the daemon. See
 		clientAPIFlag,
 		&cli.StringFlag{
 			Name:        "repo",
-			Usage:       "Specify path where visor should store chain state.",
+			Usage:       "Specify path where lily should store chain state.",
 			EnvVars:     []string{"LILY_REPO"},
 			Value:       "~/.lotus",
 			Destination: &daemonFlags.repo,
diff --git a/commands/gap.go b/commands/gap.go
@@ -39,14 +39,14 @@ var GapFillCmd = &cli.Command{
 	Flags: []cli.Flag{
 		&cli.StringFlag{
 			Name:        "api",
-			Usage:       "Address of visor api in multiaddr format.",
+			Usage:       "Address of lily api in multiaddr format.",
 			EnvVars:     []string{"LILY_API"},
 			Value:       "/ip4/127.0.0.1/tcp/1234",
 			Destination: &gapFlags.apiAddr,
 		},
 		&cli.StringFlag{
 			Name:        "api-token",
-			Usage:       "Authentication token for visor api.",
+			Usage:       "Authentication token for lily api.",
 			EnvVars:     []string{"LILY_API_TOKEN"},
 			Value:       "",
 			Destination: &gapFlags.apiToken,
@@ -129,14 +129,14 @@ var GapFindCmd = &cli.Command{
 	Flags: []cli.Flag{
 		&cli.StringFlag{
 			Name:        "api",
-			Usage:       "Address of visor api in multiaddr format.",
+			Usage:       "Address of lily api in multiaddr format.",
 			EnvVars:     []string{"LILY_API"},
 			Value:       "/ip4/127.0.0.1/tcp/1234",
 			Destination: &gapFlags.apiAddr,
 		},
 		&cli.StringFlag{
 			Name:        "api-token",
-			Usage:       "Authentication token for visor api.",
+			Usage:       "Authentication token for lily api.",
 			EnvVars:     []string{"LILY_API_TOKEN"},
 			Value:       "",
 			Destination: &gapFlags.apiToken,
diff --git a/commands/help.go b/commands/help.go
@@ -112,7 +112,7 @@ A walk takes a range of heights and will walk from the heaviest tipset at the
 upper height to the lower height using the parent state root present in each
 tipset.
 
-The type of data extracted by visor is controlled by 'tasks' that focus on
+The type of data extracted by lily is controlled by 'tasks' that focus on
 particular parts of the chain. For more information about available tasks
 see 'visor help tasks'.
 
@@ -125,7 +125,7 @@ chain. For watching incoming tipsets the blockstore must be connected and in
 sync with the filecoin network. Historic walks can be performed against an
 offline store.
 
-While running, visor will maintain its own local blockstore and attempt
+While running, lily will maintain its own local blockstore and attempt
 to synchronise it with the filecoin network. For more information on running
 visor as a daemon, including how to initialise the blockstore, see
 'visor help daemon'.
@@ -215,13 +215,13 @@ Other tasks:
 
 	{
 		Name:        "monitoring",
-		Description: "Monitoring visor operation",
+		Description: "Monitoring lily operation",
 		Text: `Visor may be monitored during operation using logfiles, metrics and tracing.
-The visor command recognizes environment variables and provides options to
+The lily command recognizes environment variables and provides options to
 control the behaviour of each type of monitoring output. Options should be
 supplied before any sub command:
 
-  visor [global options] <command>
+  lily [global options] <command>
 
 Visor uses the IPFS logging library (https://github.com/ipfs/go-ipfs) to write
 application logs. By default logs are written to STDERR in JSON format. Log
@@ -254,7 +254,7 @@ destination of the logs.
                          log levels formatted as name:level, for example
                          'logger1:debug,logger2:info'.
 
-In addition, visor supports some global options for controlling logging:
+In addition, lily supports some global options for controlling logging:
 
   --log-level LEVEL        Set the default log level for all loggers to LEVEL.
                            This option overrides any value set using the
@@ -264,9 +264,9 @@ In addition, visor supports some global options for controlling logging:
                            overrides any value set using the
                            LILY_LOG_LEVEL_NAMED environment variable.
 
-To control logging output while the visor daemon is running see 'visor help log'.
+To control logging output while the lily daemon is running see 'visor help log'.
 
-During operation visor exposes metrics and debugging information on port 9991
+During operation lily exposes metrics and debugging information on port 9991
 by default. The address used by this http server can be changed using the
 '--prometheus-port' option which expects an IP address and port number. The
 address may be omitted to run the server on all interfaces, for example: ':9991'.
@@ -286,9 +286,9 @@ Environment variables for controlling function level tracing:
   LILY_TRACING         Enable tracing. Set to 'true' to enable tracing.
 
   JAEGER_AGENT_HOST,    Hostname and port of a Jaeger compatible agent that
-  JAEGER_AGENT_PORT     visor should send traces to.
+  JAEGER_AGENT_PORT     lily should send traces to.
 
-  JAEGER_SERVICE_NAME   The name visor should use when reporting traces.
+  JAEGER_SERVICE_NAME   The name lily should use when reporting traces.
 
   JAEGER_SAMPLER_TYPE,  Control the type of sampling used to capture traces.
   JAEGER_SAMPLER_PARAM  The type may be either 'const' or 'probabilistic'.
diff --git a/commands/init.go b/commands/init.go
@@ -24,11 +24,11 @@ var initFlags struct {
 
 var InitCmd = &cli.Command{
 	Name:  "init",
-	Usage: "Initialise a visor repository.",
+	Usage: "Initialise a lily repository.",
 	Flags: []cli.Flag{
 		&cli.StringFlag{
 			Name:        "repo",
-			Usage:       "Specify path where visor should store chain state.",
+			Usage:       "Specify path where lily should store chain state.",
 			EnvVars:     []string{"LILY_REPO"},
 			Value:       "~/.lotus",
 			Destination: &initFlags.repo,
diff --git a/commands/setup.go b/commands/setup.go
@@ -147,7 +147,7 @@ func setupMetrics(flags VisorMetricOpts) error {
 	view.SetReportingPeriod(2 * time.Second)
 
 	views := []*view.View{}
-	views = append(views, metrics.DefaultViews...)        // visor metrics
+	views = append(views, metrics.DefaultViews...)        // lily metrics
 	views = append(views, lotusmetrics.ChainNodeViews...) // lotus chain metrics
 
 	// register the metrics views of interest
diff --git a/commands/stop.go b/commands/stop.go
@@ -7,7 +7,7 @@ import (
 
 var StopCmd = &cli.Command{
 	Name:  "stop",
-	Usage: "Stop a running visor daemon",
+	Usage: "Stop a running lily daemon",
 	Flags: flagSet(
 		clientAPIFlagSet,
 	),
diff --git a/commands/sync.go b/commands/sync.go
@@ -26,7 +26,7 @@ var SyncCmd = &cli.Command{
 
 var SyncStatusCmd = &cli.Command{
 	Name:  "status",
-	Usage: "Report sync status of a running visor daemon",
+	Usage: "Report sync status of a running lily daemon",
 	Flags: flagSet(
 		clientAPIFlagSet,
 	),
diff --git a/commands/wait.go b/commands/wait.go
@@ -12,7 +12,7 @@ import (
 
 var WaitApiCmd = &cli.Command{
 	Name:  "wait-api",
-	Usage: "Wait for visor api to come online",
+	Usage: "Wait for lily api to come online",
 	Flags: flagSet(
 		clientAPIFlagSet,
 		[]cli.Flag{
diff --git a/commands/walk.go b/commands/walk.go
@@ -63,14 +63,14 @@ var WalkCmd = &cli.Command{
 		},
 		&cli.StringFlag{
 			Name:        "api",
-			Usage:       "Address of visor api in multiaddr format.",
+			Usage:       "Address of lily api in multiaddr format.",
 			EnvVars:     []string{"LILY_API"},
 			Value:       "/ip4/127.0.0.1/tcp/1234",
 			Destination: &walkFlags.apiAddr,
 		},
 		&cli.StringFlag{
 			Name:        "api-token",
-			Usage:       "Authentication token for visor api.",
+			Usage:       "Authentication token for lily api.",
 			EnvVars:     []string{"LILY_API_TOKEN"},
 			Value:       "",
 			Destination: &walkFlags.apiToken,
diff --git a/commands/watch.go b/commands/watch.go
@@ -56,14 +56,14 @@ var WatchCmd = &cli.Command{
 		},
 		&cli.StringFlag{
 			Name:        "api",
-			Usage:       "Address of visor api in multiaddr format.",
+			Usage:       "Address of lily api in multiaddr format.",
 			EnvVars:     []string{"LILY_API"},
 			Value:       "/ip4/127.0.0.1/tcp/1234",
 			Destination: &watchFlags.apiAddr,
 		},
 		&cli.StringFlag{
 			Name:        "api-token",
-			Usage:       "Authentication token for visor api.",
+			Usage:       "Authentication token for lily api.",
 			EnvVars:     []string{"LILY_API_TOKEN"},
 			Value:       "",
 			Destination: &watchFlags.apiToken,
diff --git a/config/config.go b/config/config.go
@@ -74,7 +74,7 @@ func DefaultConf() *Conf {
 	}
 }
 
-// SampleConf is the example configuration that is written when visor is first started. All entries will be commented out.
+// SampleConf is the example configuration that is written when lily is first started. All entries will be commented out.
 func SampleConf() *Conf {
 	def := DefaultConf()
 	cfg := *def
diff --git a/lens/lily/struct.go b/lens/lily/struct.go
@@ -22,7 +22,7 @@ var _ LilyAPI = (*LilyAPIStruct)(nil)
 
 type LilyAPIStruct struct {
 	// authentication
-	// TODO: avoid importing CommonStruct, split out into separate visor structs
+	// TODO: avoid importing CommonStruct, split out into separate lily structs
 	v0api.CommonStruct
 
 	Internal struct {
diff --git a/lens/util/network.go b/lens/util/network.go
@@ -9,7 +9,7 @@ import (
 	"github.com/filecoin-project/lotus/chain/stmgr"
 )
 
-// DefaultNetwork is the filecoing network this version of visor has been built against
+// DefaultNetwork is the filecoing network this version of lily has been built against
 var DefaultNetwork = NewNetwork(stmgr.DefaultUpgradeSchedule(), build.NewestNetworkVersion)
 
 // Network holds properties of the filecoin network
diff --git a/main.go b/main.go
@@ -111,7 +111,7 @@ func main() {
 			&cli.StringFlag{
 				Name:        "jaeger-service-name",
 				EnvVars:     []string{"JAEGER_SERVICE_NAME"},
-				Value:       "visor",
+				Value:       "lily",
 				Destination: &commands.VisorTracingFlags.JaegerName,
 			},
 			&cli.StringFlag{
diff --git a/metrics/metrics.go b/metrics/metrics.go
@@ -33,7 +33,7 @@ var (
 	ProcessingFailure       = stats.Int64("processing_failure", "Number of processing failures", stats.UnitDimensionless)
 	PersistFailure          = stats.Int64("persist_failure", "Number of persistence failures", stats.UnitDimensionless)
 	WatchHeight             = stats.Int64("watch_height", "The height of the tipset last seen by the watch command", stats.UnitDimensionless)
-	TipSetSkip              = stats.Int64("tipset_skip", "Number of tipsets that were not processed. This is is an indication that visor cannot keep up with chain.", stats.UnitDimensionless)
+	TipSetSkip              = stats.Int64("tipset_skip", "Number of tipsets that were not processed. This is is an indication that lily cannot keep up with chain.", stats.UnitDimensionless)
 	JobStart                = stats.Int64("job_start", "Number of jobs started", stats.UnitDimensionless)
 	JobComplete             = stats.Int64("job_complete", "Number of jobs completed without error", stats.UnitDimensionless)
 	JobError                = stats.Int64("job_error", "Number of jobs stopped due to a fatal error", stats.UnitDimensionless)
diff --git a/model/interface.go b/model/interface.go
@@ -5,7 +5,7 @@ import (
 	"errors"
 )
 
-// OldestSupportedSchemaVersion is the oldest version of the schema that visor can convert its models to
+// OldestSupportedSchemaVersion is the oldest version of the schema that lily can convert its models to
 // Models can be persisted using any version between this and the latest version. Version 28 is the version
 // in which support for multiple schemas was introduced.
 var OldestSupportedSchemaVersion = Version{Major: 0, Patch: 28}
diff --git a/storage/sql.go b/storage/sql.go
@@ -33,7 +33,7 @@ import (
 )
 
 // Note this list is manually updated. Its only significant use is to verify schema compatibility
-// between the version of visor being used and the database being written to.
+// between the version of lily being used and the database being written to.
 var models = []interface{}{
 	(*blocks.BlockHeader)(nil),
 	(*blocks.BlockParent)(nil),
@@ -429,7 +429,7 @@ func (s *TxStorage) PersistModel(ctx context.Context, m interface{}) error {
 	return nil
 }
 
-// GenerateUpsertString accepts a visor model and returns two string containing SQL that may be used
+// GenerateUpsertString accepts a lily model and returns two string containing SQL that may be used
 // to upsert the model. The first string is the conflict statement and the second is the insert.
 //
 // Example given the below model:
