Skip to content
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.

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

fix: fix broken refs and change warns to errors #1139

Merged
merged 1 commit into from
Sep 3, 2020
Merged

Conversation

hugomrdias
Copy link
Contributor

closes #980
closes #1103

@hugomrdias hugomrdias requested a review from olizilla September 2, 2020 15:44
olizilla
olizilla previously approved these changes Sep 2, 2020
Copy link
Collaborator

@olizilla olizilla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@@ -234,7 +234,7 @@ TODO: link to filproofs/feistel

> The Replication phase turns an *unsealed sector* into a *sealed sector* by first *generating a key*, then using the key to *encode the orignal data*.

Before running the `Replicate` algorithm, the prover must ensure that the sector is correctly formatted with a valid "Storage Format" described in [Filecoin Client Data Processing](/missing_link) (currently `paddedfr32v1` is the required default).
Before running the `Replicate` algorithm, the prover must ensure that the sector is correctly formatted with a valid "Storage Format" described in Filecoin Client Data Processing (currently `paddedfr32v1` is the required default).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we have nothing to link to here, we should re-word it to not imply that there is

Suggested change
Before running the `Replicate` algorithm, the prover must ensure that the sector is correctly formatted with a valid "Storage Format" described in Filecoin Client Data Processing (currently `paddedfr32v1` is the required default).
Before running the `Replicate` algorithm, the prover must ensure that the sector is correctly formatted with a valid "Storage Format" (currently `paddedfr32v1` is the required default).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i will update this !

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

after hugo: downloading modules ... ends 😱

hugomrdias added a commit that referenced this pull request Sep 7, 2020
* master: (27 commits)
  fix(content): filecoin VM interface update (#1056)
  fix(content): chainsync section update (#1123)
  fix(content): libraries section update (#1115)
  fix: show hugo errors on build
  docs: tidy up the readme, add toc. (#1141)
  fix: reword stacked drg missing link text"
  fix: fix broken refs and change warns to errors (#1139)
  fix: import meter css (#1140)
  feat: build toc and dashboard in hugo (#1122)
  feat: show wip and reliable in progress bar (#1137)
  content: fix typo plus remove definition of weight (#1138)
  fix: css for label style and dashboard link (#1136)
  feat: add symbol embeds and listing (#1126)
  v1.0.1
  feat(tooling): release scripts
  v1.0.0
  chore: update readme and package.json
  fix: update dns link
  fix: fix broken links
  fix(content): FIL VM System Actors Update (#1061)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fix hugo warnings Broken links in stacked_drg.md to client-data.md
2 participants