simlecode · simlecode · Mar 26, 2021 · Mar 30, 2021 · Mar 30, 2021 · Mar 31, 2021
diff --git a/.DS_Store b/.DS_Store
diff --git a/.circleci/config.yml b/.circleci/config.yml
diff --git a/.docker/Dockerfile b/.docker/Dockerfile
@@ -8,8 +8,9 @@ RUN curl -sSf https://sh.rustup.rs | sh -s -- -y
 # https://github.com/ipfs/go-ipfs/blob/master/Dockerfile
 # Thanks Lars :)
 
-ENV SRC_DIR /go/src/github.com/filecoin-project/go-filecoin
+ENV SRC_DIR /go/src/github.com/filecoin-project/venus
 ENV GO111MODULE on
+ENV HTTPS_PROXY https://goproxy.io
 ARG FIL_PROOFS_PARAMETER_CACHE="./tmp/filecoin-proof-parameters"
 ARG FILECOIN_USE_PRECOMPILED_RUST_PROOFS=yes
 ARG FILECOIN_USE_PRECOMPILED_BLS_SIGNATURES=yes
@@ -43,9 +44,9 @@ FROM busybox:1.30.1-glibc AS filecoin
 MAINTAINER Filecoin Dev Team
 
 # Get the filecoin binary, entrypoint script, and TLS CAs from the build container.
-ENV SRC_DIR /go/src/github.com/filecoin-project/go-filecoin
+ENV SRC_DIR /go/src/github.com/filecoin-project/venus
 COPY --from=builder $SRC_DIR/tmp/filecoin-proof-parameters/* /tmp/filecoin-proof-parameters/
-COPY --from=builder $SRC_DIR/go-filecoin /usr/local/bin/go-filecoin
+COPY --from=builder $SRC_DIR/venus /usr/local/bin/venus
 COPY --from=builder $SRC_DIR/bin/container_daemon /usr/local/bin/start_filecoin
 COPY --from=builder $SRC_DIR/bin/devnet_start /usr/local/bin/devnet_start
 COPY --from=builder $SRC_DIR/bin/node_restart /usr/local/bin/node_restart

diff --git a/.docker/Dockerfile.ci.filecoin b/.docker/Dockerfile.ci.filecoin
@@ -2,9 +2,9 @@ FROM busybox:1.30.1-glibc AS filecoin
 MAINTAINER Filecoin Dev Team
 
 # Get the filecoin binary, entrypoint script, and TLS CAs from the build container.
-ENV SRC_DIR /go/src/github.com/filecoin-project/go-filecoin
+ENV SRC_DIR /go/src/github.com/filecoin-project/venus
 COPY filecoin-proof-parameters /var/tmp/filecoin-proof-parameters
-COPY filecoin/go-filecoin /usr/local/bin/go-filecoin
+COPY filecoin/venus /usr/local/bin/venus
 COPY bin/container_daemon /usr/local/bin/start_filecoin
 COPY bin/devnet_start /usr/local/bin/devnet_start
 COPY bin/node_restart /usr/local/bin/node_restart

diff --git a/.docker/Dockerfile.faucet b/.docker/Dockerfile.faucet
@@ -8,8 +8,9 @@ RUN curl -sSf https://sh.rustup.rs | sh -s -- -y
 # https://github.com/ipfs/go-ipfs/blob/master/.docker/Dockerfile
 # Thanks Lars :)
 
-ENV SRC_DIR /go/src/github.com/filecoin-project/go-filecoin
+ENV SRC_DIR /go/src/github.com/filecoin-project/venus
 ENV GO111MODULE on
+ENV HTTPS_PROXY https://goproxy.io
 ENV FILECOIN_USE_PRECOMPILED_RUST_PROOFS true
 ENV FILECOIN_USE_PRECOMPILED_BLS_SIGNATURES true
 
@@ -43,7 +44,7 @@ FROM busybox:1.30.1-glibc
 MAINTAINER Filecoin Dev Team
 
 # Get the binary, entrypoint script, and TLS CAs from the build container.
-ENV SRC_DIR /go/src/github.com/filecoin-project/go-filecoin
+ENV SRC_DIR /go/src/github.com/filecoin-project/venus
 COPY --from=0 $SRC_DIR/faucet /usr/local/bin/faucet
 COPY --from=0 /tmp/su-exec/su-exec /sbin/su-exec
 COPY --from=0 /tmp/tini /sbin/tini

diff --git a/.docker/Dockerfile.genesis b/.docker/Dockerfile.genesis
@@ -8,8 +8,9 @@ RUN curl -sSf https://sh.rustup.rs | sh -s -- -y
 # https://github.com/ipfs/go-ipfs/blob/master/.docker/Dockerfile
 # Thanks Lars :)
 
-ENV SRC_DIR /go/src/github.com/filecoin-project/go-filecoin
+ENV SRC_DIR /go/src/github.com/filecoin-project/venus
 ENV GO111MODULE on
+ENV HTTPS_PROXY https://goproxy.io
 
 COPY . $SRC_DIR
 
@@ -40,7 +41,7 @@ FROM busybox:1.30.1-glibc
 MAINTAINER Filecoin Dev Team
 
 # Get the binary, entrypoint script, and TLS CAs from the build container.
-ENV SRC_DIR /go/src/github.com/filecoin-project/go-filecoin
+ENV SRC_DIR /go/src/github.com/filecoin-project/venus
 COPY --from=0 $SRC_DIR/genesis-file-server /usr/local/bin/genesis-file-server
 COPY --from=0 /tmp/su-exec/su-exec /sbin/su-exec
 COPY --from=0 /tmp/tini /sbin/tini

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0 +1,102 @@
+name: "Bug Report"
+description: "File a bug report to help us improve"
+labels: [need/triage, kind/bug]
+body:
+- type: checkboxes
+  attributes:
+    label: Checklist
+    description: Please check off the following boxes before continuing to file a bug report!
+    options:
+      - label: This is **not** a security-related bug/issue. If it is, please follow please follow the [security policy](https://github.com/filecoin-project/venus/security/policy).
+        required: true
+      - label: This is **not** a question or a support request. If you have any lotus related questions, please ask in the [venus forum](https://github.com/filecoin-project/venus/discussions).
+        required: true
+      - label: This is **not** a new feature request. If it is, please file a [feature request](https://github.com/filecoin-project/venus/issues/new?assignees=&labels=need%2Ftriage%2Ckind%2Ffeature&template=feature_request.yml) instead.
+        required: true
+      - label: This is **not** an enhancement request. If it is, please file a [improvement suggestion](https://github.com/filecoin-project/venus/issues/new?assignees=&labels=need%2Ftriage%2Ckind%2Fenhancement&template=enhancement.yml) instead.
+        required: true
+      - label: I **have** searched on the [issue tracker](https://github.com/filecoin-project/venus/issues) and the [venus forum](https://github.com/filecoin-project/venus/discussions), and there is no existing related issue or discussion.
+        required: true
+      - label: I am running the [`latest release`](https://github.com/filecoin-project/venus/releases), or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
+        required: true
+      - label: I did not make any code changes to venus.
+        required: false
+- type: checkboxes
+  attributes:
+    label: Venus component
+    description: Please select the venus component you are filing a bug for
+    options:
+      - label: venus daemon - chain sync
+        required: false
+      - label: venus auth - authentication
+        required: false
+      - label: venus gateway - chain service gateway
+        required: false
+      - label: venus miner - mining and block production
+        required: false
+      - label: venus sealer/worker - sealing
+        required: false
+      - label: venus sealer - proving(WindowPoSt)
+        required: false
+      - label: venus market - storage deal
+        required: false
+      - label: venus market - retrieval deal
+        required: false
+      - label: venus market - data transfer
+        required: false
+      - label: venus light-weight client
+        required: false
+      - label: venus JSON-RPC API
+        required: false
+      - label: venus messager - message management (mpool)
+        required: false
+      - label:  Other
+        required: false
+- type: textarea
+  id: version
+  attributes:
+    label: Venus Version
+    render: text
+    description: Enter the output of `./venus version` and `./venus-sealer -v` if applicable.
+    placeholder: |
+      e.g. 
+      Daemon: "Commit": "v1.0.4 c816de06debd1874bc0b2c9cad10a80e8f388681" 
+      Local: venus-sealer version 1.2.6+git.eb586f1.dirty
+  validations:
+    required: true
+- type: textarea
+  id: Description
+  attributes:
+    label: Describe the Bug
+    description: |
+      This is where you get to tell us what went wrong, when doing so, please try to provide a clear and concise description of the bug with all related information:
+      * What you were doing when you experienced the bug?
+      * Any *error* messages you saw, *where* you saw them, and what you believe may have caused them (if you have any ideas).
+      * What is the expected behaviour?
+      * For sealing issues, include the output of `./venus-sealer sectors status --log <sectorId>` for the failed sector(s).
+      * For proving issues, include the output of `./venus-sealer proving` info.
+      * For deal making issues, include the output of `./market-client list-deals -v` and/or `./venus-market storage-deals|retrieval-deals|data-transfers list [-v]` commands for the deal(s) in question.
+  validations:
+    required: true
+- type: textarea
+  id: extraInfo
+  attributes:
+    label: Logging Information
+    render: text
+    description: |
+      Please provide debug logs of the problem, remember you can get set log level.
+      If you don't provide detailed logs when you raise the issue it will almost certainly be the first request I make before furthur diagnosing the problem.
+  validations:
+    required: true
+- type: textarea
+  id: RepoSteps
+  attributes:
+    label: Repo Steps
+    description: "Steps to reproduce the behavior"
+    value: |
+      1. Run '...'
+      2. Do '...'
+      3. See error '...'
+      ...
+  validations:
+    required: false
diff --git a/.github/ISSUE_TEMPLATE/enhancement.yml b/.github/ISSUE_TEMPLATE/enhancement.yml
@@ -0,0 +1,56 @@
+name: Enhancement
+description:  Suggest an improvement to an existing venus feature.
+labels: [need/triage, kind/enhancement]
+body:
+- type: checkboxes
+  attributes:
+    label: Checklist
+    description: Please check off the following boxes before continuing to create an improvement suggestion!
+    options:
+      - label: This is **not** a new feature or an enhancement to the Filecoin protocol. If it is,  please open an [FIP issue](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0001.md).
+        required: true
+      - label: This is **not** a new feature request. If it is, please file a [feature request](https://github.com/filecoin-project/venus/issues/new?assignees=&labels=need%2Ftriage%2Ckind%2Ffeature&template=feature_request.yml) instead.
+        required: true
+      - label: This is **not** brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on [the venus forum](https://github.com/filecoin-project/venus/discussions/categories/ideas) and select the category as `Ideas`.
+        required: true
+      - label: I **have** a specific, actionable, and well motivated improvement to propose.
+        required: true
+- type: checkboxes
+  attributes:
+    label: Venus component
+    description: Please select the venus component you are filing an improvement request for
+    options:
+      - label: venus daemon - [chain service] chain sync
+        required: false
+      - label: venus auth - [chain service] authentication
+        required: false
+      - label: venus messager - [chain service] message management (mpool)
+        required: false
+      - label: venus gateway - [chain service] gateway
+        required: false
+      - label: venus miner - [chain service] mining and block production
+        required: false
+      - label: venus sealer/worker - sealing
+        required: false
+      - label: venus sealer - proving (WindowPoSt)
+        required: false
+      - label: venus market - storage deal
+        required: false
+      - label: venus market - retrieval deal
+        required: false
+      - label: venus market - data transfer
+        required: false
+      - label: venus light-weight client
+        required: false
+      - label: venus JSON-RPC API
+        required: false
+      - label:  Other
+        required: false
+- type: textarea
+  id: request
+  attributes:
+    label: Improvement Suggestion
+    description: A clear and concise description of what the motivation or the current problem is and what is the suggested improvement?
+    placeholder: Ex. Currently venus... However, as a storage provider, I'd like...
+  validations:
+    required: true
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -0,0 +1,75 @@
+name: Feature request
+description:  Suggest an idea for venus
+labels: [need/triage, kind/feature]
+body:
+- type: checkboxes
+  attributes:
+    label: Checklist
+    description: Please check off the following boxes before continuing to create a new feature request!
+    options:
+      - label: This is **not** a new feature or an enhancement to the Filecoin protocol. If it is, please open an [FIP issue](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0001.md).
+        required: true
+      - label: This is **not** brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on [the venus forum](https://github.com/filecoin-project/venus/discussions/categories/ideas) and select the category as `Ideas`.
+        required: true
+      - label: I **have** a specific, actionable, and well motivated feature request to propose.
+        required: true
+- type: checkboxes
+  attributes:
+    label: Venus component
+    description: Please select the venus component you are filing a new feature request for
+    options:
+      - label: venus daemon - [chain service] chain sync
+        required: false
+      - label: venus auth - [chain service] authentication
+        required: false
+      - label: venus messager - [chain service] message management (mpool)
+        required: false
+      - label: venus gateway - [chain service] gateway
+        required: false
+      - label: venus miner - [chain service] mining and block production
+        required: false
+      - label: venus sealer/worker - sealing
+        required: false
+      - label: venus sealer - proving (WindowPoSt)
+        required: false
+      - label: venus market - storage deal
+        required: false
+      - label: venus market - retrieval deal
+        required: false
+      - label: venus market - data transfer
+        required: false
+      - label: venus light-weight client
+        required: false
+      - label: venus JSON-RPC API
+        required: false
+      - label:  Other
+        required: false
+- type: textarea
+  id: request
+  attributes:
+    label: What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.
+    description: A clear and concise description of what the motivation or the problem is. 
+    placeholder: Ex. I'm always frustrated when [...]
+  validations:
+    required: true
+- type: textarea
+  id: solution
+  attributes:
+    label: Describe the solution you'd like
+    description: A clear and concise description of what you want to happen. 
+  validations:
+    required: true
+- type: textarea
+  id: alternates
+  attributes:
+    label: Describe alternatives you've considered
+    description: A clear and concise description of any alternative solutions or features you've considered.
+  validations:
+    required: false
+- type: textarea
+  id: extra
+  attributes:
+    label: Additional context
+    description: Add any other context, design docs or screenshots about the feature request here.
+  validations:
+    required: false
diff --git a/.github/ISSUE_TEMPLATE/new_story.md b/.github/ISSUE_TEMPLATE/new_story.md
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
@@ -1,9 +1,21 @@
-### Motivation
+## Related Issues
+<!-- link all issues that this PR might resolve/fix. If an issue doesn't exist, include a brief motivation for the change being made.-->
 
+## Proposed Changes
+<!-- provide a clear list of the changes being made-->
 
-### Proposed changes
 
-Closes #
+## Additional Info
+<!-- callouts, links to documentation, and etc-->
 
-<!-- Add the label "protocol breaking" if this PR alters protocol compatibility -->
+## Checklist
 
+Before you mark the PR ready for review, please make sure that:
+- [ ] All commits have a clear commit message.
+- [ ] The PR title is in the form of of `<PR type>: <#issue number> <area>: <change being made>`
+    - example: ` fix: #1234 mempool: Introduce a cache for valid signatures`
+    - `PR type`: _fix_, _feat_, _INTERFACE BREAKING CHANGE_, _CONSENSUS BREAKING_, _build_, _chore_, _ci_, _docs_, _misc_, _perf_, _refactor_, _revert_, _style_, _test_
+    - `area`: _venus_, _venus-messager_, _venus-miner_, _venus-gateway_, _venus-auth_, _venus-market_, _venus-sealer_, _venus-wallet_, _venus-cluster_, _api_, _chain_, _state_, _vm_, _data transfer_, _mempool_, _message_, _block production_, _multisig_, _networking_, _paychan_, _proving_, _sealing_, _wallet_
+- [ ] This PR has tests for new functionality or change in behaviour
+- [ ] If new user-facing features are introduced, clear usage guidelines and / or documentation updates should be included in [venus docs](https://venus.filecoin.io) or [Discussion Tutorials.](https://github.com/filecoin-project/venus/discussions/categories/tutorials)
+- [ ] CI is green