Skip to content

Fix Typos #1336

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix Typos #1336

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -290,7 +290,7 @@ This release includes a migration which must be applied before deploying against
* [1.21](https://github.com/filecoin-project/lily/blob/master/schemas/v1/21_actor_add_state.go)

### Feat
* feat: Add retry opt for asynq https://github.com/filecoin-project/lily/pull/1167
* feat: Add retry opt for async https://github.com/filecoin-project/lily/pull/1167
* Create FEVM actor stats task https://github.com/filecoin-project/lily/pull/1173
* implement fevm_actor_stats task and schema
* task name `fevm_actor_stats`
Expand All @@ -313,7 +313,7 @@ This release includes a migration which must be applied before deploying against
* fix: do not error on null or empty params for parsing message https://github.com/filecoin-project/lily/pull/1171

### Chore
* feat:update the lotus version https://github.com/filecoin-project/lily/pull/1153
* feat: update the lotus version https://github.com/filecoin-project/lily/pull/1153
* feat: update the lotus version to v1.23.0 https://github.com/filecoin-project/lily/pull/1175


Expand Down Expand Up @@ -641,7 +641,7 @@ The following datasets are affected:
```bash
$ lily index height 1741960 --tasks=actorstatesraw,actorstatespower,actorstatesreward,actorstatesminer,actorstatesinit,actorstatesmarket,actorstatesmultisig,actorstatesverifreg,block,messages,chaineconomics,msapprovals,implicitmessage,consensus
```
will produce the follow entries in the processing_reports table
will produce the following entries in the processing_reports table

| height | task | status |
| --- | --- | --- |
Expand Down Expand Up @@ -683,10 +683,10 @@ The following datasets are affected:
| 1741960 | actor | OK |

- Watcher Workers (#871)
- The `lily watch` command now has the option to specify the number of tipsets that may be indexed in parallel. This can be specified with the `--workers` flag (see `lily watch --help` for details). Note that using large values (greater than 2) will require significant resource to coupe with indexing demands.
- The `lily watch` command now has the option to specify the number of tipsets that may be indexed in parallel. This can be specified with the `--workers` flag (see `lily watch --help` for details). Note that using large values (greater than 2) will require significant resource to cope with indexing demands.

- Blockstore and Statestore Caching (#766)
- The `lily daemon` command now as the option to use a `blockstore` and/or `statestore` cache. The `blockstore` cache caches values from the lotus blockstore, the `statestore` cache caches values from the lotus statestore. Setting these flags will increase the performance of the lily daemon, but will cause lily to use more memory. Assuming lily is operating on a system with 256 GiB of RAM we recommend the following values: `--blockstore-cache-size=5000000` and `--statestore-cache-size=3000000`. Some tuning will be required to find the values that work best for your deployment.
- The `lily daemon` command now has the option to use a `blockstore` and/or `statestore` cache. The `blockstore` cache caches values from the lotus blockstore, the `statestore` cache caches values from the lotus statestore. Setting these flags will increase the performance of the lily daemon, but will cause lily to use more memory. Assuming lily is operating on a system with 256 GiB of RAM we recommend the following values: `--blockstore-cache-size=5000000` and `--statestore-cache-size=3000000`. Some tuning will be required to find the values that work best for your deployment.

### Fix

Expand Down Expand Up @@ -875,7 +875,7 @@ If there are any questions or problems, please [open a support issue](https://gi
Note: This is a major release. The project name has changed from `sentinel-visor` to `lily`, the binary
produced when building the project has changed from `visor` to `lily`, and all lenses have been removed.
This means lily will cease to work with the lotusAPI lens, CAR-file lens, and Repo lens. Henceforth, Lily
will run as a deamonized process capable of both syncing and processing the Filecoin blockchain.
will run as a daemonized process capable of both syncing and processing the Filecoin blockchain.

### Docs
- strengthen constraints on schema migrations (#683)
Expand Down Expand Up @@ -1329,7 +1329,7 @@ Required schema version: `27`

The CLI interface has shifted again to deprecate the `run` subcommand in favor of dedicated subcommands for `indexer` and `processor` behaviors.

Previously the indexer and procerror would be started via:
Previously the indexer and processor would be started via:

```sh
sentinel-visor run --indexhead
Expand Down Expand Up @@ -1378,7 +1378,7 @@ The `run` subcommand will be removed in v0.5.0.

### Test
- add multisig actor extractor tests
- power actor claim extration test
- power actor claim extraction test
- **init:** test coverage for init actor extractor

### Chore
Expand Down Expand Up @@ -1474,7 +1474,7 @@ The `run` subcommand will be removed in v0.5.0.

this changes the cli interface to remove the run subcommand.

Previously the indexer and procerror would be started via:
Previously the indexer and processor would be started via:

```sh
sentinel-visor run indexer
Expand Down Expand Up @@ -1503,7 +1503,7 @@ After this change:
- support v2 actor codes ([#84](https://github.com/filecoin-project/sentinel-visor/issues/84))
- add test for create schema ([#3](https://github.com/filecoin-project/sentinel-visor/issues/3))
- **api:** wrap lotus api and store with wrapper
- **debug:** Process actor by head without persistance ([#86](https://github.com/filecoin-project/sentinel-visor/issues/86))
- **debug:** Process actor by head without persistence ([#86](https://github.com/filecoin-project/sentinel-visor/issues/86))
- **genesis:** add task for processing genesis state
- **scheduler:** Refactor task scheduler impl ([#41](https://github.com/filecoin-project/sentinel-visor/issues/41))
- **task:** add actor, actor-state, and init actor processing ([#14](https://github.com/filecoin-project/sentinel-visor/issues/14))
Expand Down
4 changes: 2 additions & 2 deletions docs/release_management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
Between releases we keep track of notable changes in CHANGELOG.md.

When we want to make a release we should update CHANGELOG.md to contain the release notes for the planned release in a section for
the proposed release number. This update is the commit that will be tagged with as the actual release which ensures that each release
the proposed release number. This update is the commit that will be tagged as the actual release which ensures that each release
contains a copy of it's own release notes.

We should also copy the release notes to the Github releases page, but CHANGELOG.md is the primary place to keep the release notes.
Expand Down Expand Up @@ -35,7 +35,7 @@ NOTE: `lily` pull requests prefer to be squash-merged into `master`, however con

## Updating CHANGELOG.md

The format is a variant of [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) combined with categories from [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/). This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). The [github.com/git-chglog](https://github.com/git-chglog/git-chglog) utility assists us with maintaing CHANGELOG.md.
The format is a variant of [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) combined with categories from [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/). This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). The [github.com/git-chglog](https://github.com/git-chglog/git-chglog) utility assists us with maintaining CHANGELOG.md.

The sections within each release have a preferred order which prioritizes by largest-user-impact-first: `Feat > Refactor > Fix > {Area-specific or Custom Sections} > Chore`

Expand Down