cathayddt/bdk

Streamlined blockchain deployment kit for Hyperledger Fabric.

bdk's Issues

bdk create channel error

ISSUE

說明 (Description)

請簡單說明此 issue。

Please include a summary of the issue.

種類 (Issue Type)

[ ] Feature Request
[ ] Report Bug
[x] Other

通報問題 (Report Bug)

重現步驟 (Steps to Reproduce)

1. bdk network create --test-network
2. bdk orderer up -i
3. bdk peer up -i
4. bdk channel create -i

測試環境 (Environment):

• OS: Mac
• NodeJS Version:
• NPM Version:
• Docker Version:

應呈現結果 (Expected Behavior)

成功创建Channel

實際呈現結果 (Resulted Behavior)

---

其他說明 (Additional Context)

新增更新區塊鏈憑證功能

說明 (Description)

現行功能只能發放憑證，新功能希望能管理運行中的區塊連憑證，使憑證能更新與撤銷。

Please include a summary of the issue.

種類 (Issue Type)

[x] Feature Request
[ ] Report Bug
[ ] Other

---

新功能 (Feature Request)

希望新增此功能的原因 (Reason for this Feature)

• 更新即期憑證
• 更新過去憑證
• Revoke 憑證

可能的使用方式

bdk ca update --msp-id=foo
bdk orderer ca update --msp-id=foo
bdk peer ca update --msp-id=foo

Help text not displaying properly for certain commands

ISSUE

說明 (Description)

Help text not displaying for commands that have file io operations.

種類 (Issue Type)

• Feature Request
• Report Bug
• Other

可能的解法 (Proposed Solution)

Create exceptions or error handling for subcommands that require file io operations.

通報問題 (Report Bug)

重現步驟 (Steps to Reproduce)

1. Run help on any command that requires file io (e.g. bdk channel --help)

測試環境 (Environment):

• OS:
• NodeJS Version:
• NPM Version:
• Docker Version:

應呈現結果 (Expected Behavior)
Descriptive help text without errors.

實際呈現結果 (Resulted Behavior)
Error: Error: ENOENT: no such file or directory, scandir...

Overriding environmental variables

ISSUE

說明 (Description)

Individual commands should include optional parameters and interactive prompts that override environmental variables.

Please include a summary of the issue.

種類 (Issue Type)

[x] Feature Request
[ ] Report Bug
[ ] Other

---

新功能 (Feature Request)

希望新增此功能的原因 (Reason for this Feature)
This should greatly improve UX since it's more straightforward and that the user will not need to change environmental variables manually.

可能的解法 (Proposed Solution)
Add optional overriding parameter for commands that utilize environmental variables, and include a prompt with similar use in interactive mode.

---

其他說明 (Additional Context)

Optimize readme.md, example

ISSUE

說明 (Description)

Optimize readme.md, example

種類 (Issue Type)

[ ] Feature Request
[ ] Report Bug
[x] Other

---

其他說明 (Additional Context)

1. readme 的 test-network 說明更完整
2. example 可讀性需要增強（條列式說明）

Multi-hosts部屬的網絡連接問題

ISSUE

說明 (Description)

multi-hosts部屬的網絡連接問題，我是先建立docker-swarm連結三個獨立的hosts，然後於Manager去建立一個Overlay network以及產生network需要的相關資料，再去各個host，分別啟動不同的peers、orderers，問題就在於bdk up是以docker-compose去up，他會於當前執行的host依據docker-compose中的network定義產生一個bridge網絡(scope非整個swarm網絡)，使得hosts之間的peer與orderer之間是無法連線溝通，目前只好採一些土炮的方式來進行改善。

種類 (Issue Type)

[x] Feature Request
[ ] Report Bug
[] Other

---

新功能 (Feature Request)

希望新增此功能的原因 (Reason for this Feature)
因為很少單機部屬情況，大多數情形都是cluster部屬，這方面的說明比較少，若這方面能˙有比較多的支援、選擇或者說明，應該會變得相當吸引人，目前我就算採用土炮的方式來製作，也比官方原始的方式來得有效率，非常感謝這個開源工具。

...

可能的解法 (Proposed Solution)
我目前就是先用docker-swarm去建立一個最小服務，而這服務就在所有節點去建立一個共同的Overlay Network，網絡名稱取得跟bdk產生的docker-compose中採用的external network名稱一樣，接著再用bdk去up於不同的host上，就能成功達成multi-hosts的部屬，這目前運作上沒有問題，但總覺得運作起來有點多餘。
...

---

Workflows: unit-test optimize

ISSUE

Description

Happen in #72 , github action free-tier ubuntu runner's performance not fit our requirement.
Now npm run test:coverage spent too much time when local test and workflow, we should optimize it!!!

And I also consider about mock some dockerode test in test case, if this repo contain more PR. Action free usage limit will exceed.
Self-hosted runner is also a choice too, but we only release a version in a season. It's not that worth!

Please include a summary of the issue.

Issue Type

• Feature Request
• Report Bug
• Other: CI / CD

---

Feature Request

Reason for this Feature

npm run test:coverage and npm run test:sonar spent too much time!
We don't want paid money!

Proposed Solution

re-write unit-test or remove some duplicate function in unit-test

---

Report Bug

Steps to Reproduce

1. send a PR and merge

Environment:

• github action: ubuntu-latest

Expected Behavior

time under 5 mins

Resulted Behavior

20 mins!

approve/update 前供使用者確認 approve/update 的內容

ISSUE

說明 (Description)

新指令： bdk org decode-envelop

種類 (Issue Type)

[x] Feature Request
[ ] Report Bug
[ ] Other

---

新功能 (Feature Request)

在 approve 前無法檢查內容

...

可能的解法 (Proposed Solution)
decode channel-artifacts/{channelName}/{channelName}_update_envelope.pb

Org Definition Json應該對每個Org分別產生

ISSUE

說明 (Description)

bdk/src/service/peer.ts

Line 61 in 26724bc

const configtxYaml = new ConfigtxYaml()

應該移到 64 行的 for 迴圈內

種類 (Issue Type)

[ ] Feature Request
[x] Report Bug
[ ] Other

---

通報問題 (Report Bug)

重現步驟 (Steps to Reproduce)

1. ...
2. ...

測試環境 (Environment):

• OS:
• NodeJS Version:
• NPM Version:
• Docker Version:

應呈現結果 (Expected Behavior)

請詳細說明應呈現的畫面/結果。

Please describe the bahavior expected.

實際呈現結果 (Resulted Behavior)

請詳細說明實際執行呈現的畫面/結果。

Please describe the behavior that actually occurred.

---

其他說明 (Additional Context)

新增CA getcainfo獲取憑證功能

ISSUE

說明 (Description)

使用getcainfo傳遞憑證，提供import/export以外的方式

Please include a summary of the issue.

種類 (Issue Type)

[x] Feature Request
[ ] Report Bug
[ ] Other

---

新功能 (Feature Request)

希望新增此功能的原因 (Reason for this Feature)

...

可能的解法 (Proposed Solution)

...

---

其他說明 (Additional Context)

orderer/peer up & down need hostname.toLowerCase()

ISSUE

說明 (Description)

hostname need lower case when orderer/peer created

種類 (Issue Type)

[ ] Feature Request
[x] Report Bug
[ ] Other

補齊 unit test

ISSUE

說明 (Description)

We need unit test

種類 (Issue Type)

[ ] Feature Request
[ ] Report Bug
[x] Other

bdk export/import

ISSUE

說明 (Description)

將需要傳檔的步驟都做成export/import指令

種類 (Issue Type)

[x] Feature Request
[ ] Report Bug
[ ] Other

---

新功能 (Feature Request)

希望新增此功能的原因 (Reason for this Feature)
使用者不需要進到 ~/.bdk 資料夾內找檔案

可能的解法 (Proposed Solution)

1. 先列出所有需要傳檔的步驟
2. 將檔案壓縮成單一檔案方便互傳

peer與orderer的approve與update整合

ISSUE

說明 (Description)

bdk org peer approve 與 bdk org orderer approve 做的事一樣
bdk org peer update 與 bdk org orderer update 做的事一樣

種類 (Issue Type)

[x] Feature Request
[ ] Report Bug
[ ] Other

---

新功能 (Feature Request)

希望新增此功能的原因 (Reason for this Feature)
整合重複指令

可能的解法 (Proposed Solution)
新指令：
bdk channel approve
bdk channel update

---

其他說明 (Additional Context)

新增 --extra-host 參數

ISSUE

說明 (Description)

新增指令參數 --extra-host

種類 (Issue Type)

[x] Feature Request
[ ] Report Bug
[ ] Other

---

新功能 (Feature Request)

希望新增此功能的原因 (Reason for this Feature)
因為 peer/orderer 都在 docker 裡面跑，吃不到 host 的 /etc/hosts
若機器在內網，且沒有內網 DNS 時，無法透過 domain 解析到其他 peer/orderer

可能的解法 (Proposed Solution)
在跑 docker run 的指令把 extra hosts 加到 --add-host 的參數
在產 docker-compose.yaml 的指令，將把 extra hosts 加到 extra_hosts 欄位

其他說明 (Additional Context)

關於Explorer沒及時更新以及指令bdk explorer update的用途

What is the question?

我遇到Explorer的內容沒及時更新，bdk explorer up剛啟動時一般沒什麼問題，但大概一陣子後，譬如你chaincode添加，或者是開始匯入資料到鏈上，會發現在瀏覽器中閱覽explorer時候他的block內容沒有更新，瀏覽器重新整理也不會變，我處理的方法是採用:

• 通常我發現，docker container restart explorerContainerID，這樣就重啟後，explorer內容就會成功為最新的狀態

• 另外一個，我發現好像執行指令bdk explorer update似乎也能有類似上面效果，因為我擔心他實際上有很多不知道的操作，他速度上會需要等一陣子，可是若我只是單純用上面restart感受上比較快，還是說其實二者能成功的原因是因為是作了類似的事情
  (我看說明說這個是: 更新 Blockchain explorer 連接的 Peer，有點抽象，不太清楚他的資料是怎麼變動)

• 最後，我為了讓他定期都可以更新，我用linux Crontab設置，每日八時去 bdk explorer update (畢竟每日重啟容器不太合理)，不知道是否有沒有比較建議的方式，還是我這樣做其實就是此工具的正確作法

New feature: bdk quorum network upgrade

ISSUE

Description

Related to #78. Need upgrade function for exist node through bdk when quorum version is upgraded. We have no exist function to directly upgrade our exist validator or member node.

種類 (Issue Type)

• Feature Request
• Report Bug
• Other

---

新功能 (Feature Request)

Upgrade version for exist node.

可能的解法 (Proposed Solution)

Using bdk quorum network upgrade to select the exist node and upgrade to the version from the supported quorum list for user.

---

Set Logging Options Maxsize

What is the problem that you are trying to solve?

docker container taking all disk space when running a times.

新功能 Feature Request

container log need config log-opt https://docs.docker.com/config/containers/logging/configure/#configure-the-default-logging-driver

可能的解法 Proposed Solution

in all docker-compoese set the options max-size

version: '3'
services:
    app:
        ...
        logging:
            driver: "json-file"
            options:
                max-size: "100m"
                max-file: "10"

bdk hello error

ISSUE

說明 (Description)

按照網頁上執行所有從原始碼安裝的指令,並執行bdk completion後,執行bdk hello出現以下訊息：
[bdk] 2022-02-17T05:33:52.585Z - warn: [production] Hello warn! { _: [Array], '$0': '/opt/homebrew/bin/bdk' }
[bdk] 2022-02-17T05:33:52.585Z - error: [production] Hello error! { _: [Array], '$0': '/opt/homebrew/bin/bdk' }

種類 (Issue Type)

[ ] Feature Request
[ ] Report Bug
[＊ ] Other

[Refactor] logger && stand output

ISSUE

說明 (Description)

訊息輸出格式改為 command line 標準輸出

種類 (Issue Type)

[ ] Feature Request
[ ] Report Bug
[x] Other

---

可能的解法 (Proposed Solution)

修改 logger 格式

---

應呈現結果 (Expected Behavior)

> bdk config init
Config init success

---

其他說明 (Additional Context)

考慮可以讓使用者選著輸出模式

• 標準: 只輸出必要結果訊息（執行結果）
• Debug: 輸出所有 logger
• package 模式: 讓使用者使用自己的 logger

移除指令 `bdk chaincode deploy`

ISSUE

說明 (Description)

此指令完全可被 chaincode install, chaincode approve, chaincode commit 取代
無需再維護此多功能的指令

種類 (Issue Type)

[ ] Feature Request
[ ] Report Bug
[x] Other

network create 時的舊組織無法透過 org peer add 加入 channel

ISSUE

說明 (Description)

command bdk network create 未呼叫 peer.createPeerOrgConfigtxJSON，沒有將 org 寫入 org-json 資料夾

種類 (Issue Type)

[ ] Feature Request
[x] Report Bug
[ ] Other

---

通報問題 (Report Bug)

重現步驟 (Steps to Reproduce)

1. 建立網路，有P1, P2, P3 共3個Peer Org
2. 使用 bdk org peer create 建立 P4 Org
3. P4 建立 channel，成員包括 P1, P2, P4
4. 使用 bdk org peer add 將 P3 加入 channel

測試環境 (Environment):

• OS:
• NodeJS Version:
• NPM Version:
• Docker Version:

應呈現結果 (Expected Behavior)
讀取 P3 的 org-json 並產生信封

實際呈現結果 (Resulted Behavior)
P3 沒有 org-json

---

其他說明 (Additional Context)

chaincode deploy/approve/update/invoke/query 改用discover

ISSUE

說明 (Description)

組織設anchor-peer後，discover機制可以取得channel的其他peer，與endorsement policy

種類 (Issue Type)

[x] Feature Request
[ ] Report Bug
[ ] Other

---

新功能 (Feature Request)

希望新增此功能的原因 (Reason for this Feature)
用discover的機制就不需要再帶 --peer跟--orderer參數，tlsca資料夾可能也可以拿掉

可能的解法 (Proposed Solution)
用fabric-tool做discover
Discover peers:

docker run --rm -u "$(id -u):$(id -g)" --network shell-network-cryptogen -v $HOME/.bdk/shell-network-cryptogen:/tmp hyperledger/fabric-tools:2.2.1 \
discover peers \
--peerTLSCA /tmp/tlsca/peer0.org0.bdk.example.com/ca.crt \
--userKey /tmp/peerOrganizations/org0.bdk.example.com/users/[email protected]/msp/keystore/priv_sk \
--userCert /tmp/peerOrganizations/org0.bdk.example.com/users/[email protected]/msp/signcerts/[email protected] \
--MSP Org0 \
--server peer0.org0.bdk.example.com:7051 --channel bdk-channel

Discover chaincode endorsers:

docker run --rm -u "$(id -u):$(id -g)" --network shell-network-cryptogen -v $HOME/.bdk/shell-network-cryptogen:/tmp hyperledger/fabric-tools:2.2.1 \
discover endorsers \
--peerTLSCA /tmp/tlsca/peer0.org0.bdk.example.com/ca.crt \
--userKey /tmp/peerOrganizations/org0.bdk.example.com/users/[email protected]/msp/keystore/priv_sk \
--userCert /tmp/peerOrganizations/org0.bdk.example.com/users/[email protected]/msp/signcerts/[email protected] \
--MSP Org0 \
--server peer0.org0.bdk.example.com:7051 --channel bdk-channel --chaincode fabcar

Discover channel config

docker run --rm -u "$(id -u):$(id -g)" --network shell-network-cryptogen -v $HOME/.bdk/shell-network-cryptogen:/tmp hyperledger/fabric-tools:2.2.1 \
discover config \
--peerTLSCA /tmp/tlsca/peer0.org0.bdk.example.com/ca.crt \
--userKey /tmp/peerOrganizations/org0.bdk.example.com/users/[email protected]/msp/keystore/priv_sk \
--userCert /tmp/peerOrganizations/org0.bdk.example.com/users/[email protected]/msp/signcerts/[email protected] \
--MSP Org0 \
--server peer0.org0.bdk.example.com:7051 --channel bdk-channel

其他說明 (Additional Context)

`bdk network delete` 未刪除 explorer

ISSUE

說明 (Description)

explorer的docker-compose放的位置跟peer/orderer不同

種類 (Issue Type)

[ ] Feature Request
[x] Report Bug
[ ] Other

---

通報問題 (Report Bug)

重現步驟 (Steps to Reproduce)

1. bdk network delete -f
2. docker ps -a

測試環境 (Environment):

• OS:
• NodeJS Version:
• NPM Version:
• Docker Version:

應呈現結果 (Expected Behavior)

請詳細說明應呈現的畫面/結果。

應刪除 explorer 與 explorer-db

實際呈現結果 (Resulted Behavior)

---

其他說明 (Additional Context)

建議把 explorer 的 docker-compose down 也加進指令

ICA無法設定到期時間

ISSUE

說明 (Description)

#41 的修復不完全

種類 (Issue Type)

[ ] Feature Request
[x] Report Bug
[ ] Other

---

通報問題 (Report Bug)

重現步驟 (Steps to Reproduce)

1. RCA 發 2 天的憑證

bdk ca up -n rca.bdk.example.com -p 7054 --csr-cn rca.bdk.example.com --csr-hosts rca.bdk.example.com --csr-expiry 48h --csr-pathlength 2

2. 確定 RCA 確實只發 2 天憑證

openssl x509 -text -noout -in $HOME/.bdk/test/ca/rca.bdk.example.com/crypto/ca-cert.pem

3. 註冊 ICA

bdk ca enroll -t client -u rca.bdk.example.com -p 7054 --client-id admin --client-secret adminpw --role rca --org-hostname rca.bdk.example.com
bdk ca register -t ica -a admin -u rca.bdk.example.com -p 7054 --client-id ica.org0.bdk.example.com --client-secret org0icapw

4. 啟動 ICA 透過 CSR 設定只發 1 天憑證

bdk ca up -n ica.org0.bdk.example.com -p 7154 --ica-parentserver-cn rca.bdk.example.com --ica-parentserver-url "https://ica.org0.bdk.example.com:[email protected]:7054" --ica-enrollment-host ica.org0.bdk.example.com --ica-enrollment-profile ca --csr-expiry 24h --csr-pathlength 1

5. 檢查 ICA 憑證

openssl x509 -text -noout -in $HOME/.bdk/test/ca/rca.bdk.example.com/crypto/ca-cert.pem

測試環境 (Environment):

• OS:
• NodeJS Version:
• NPM Version:
• Docker Version:

應呈現結果 (Expected Behavior)
ICA 憑證有效期限為 24 小時

實際呈現結果 (Resulted Behavior)
ICA 憑證有效期限為 48 小時

RCA:

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            14:92:5d:be:40:c8:97:9d:ef:63:b6:88:b0:ab:97:bb:7f:0f:c4:fa
    Signature Algorithm: ecdsa-with-SHA256
        Issuer: C=US, ST=North Carolina, O=Hyperledger, OU=Fabric, CN=rca.bdk.example.com
        Validity
            Not Before: Jan 22 02:18:00 2022 GMT
            Not After : Jan 24 02:18:00 2022 GMT
        Subject: C=US, ST=North Carolina, O=Hyperledger, OU=Fabric, CN=rca.bdk.example.com
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (256 bit)
                pub: 
                    04:56:ce:7d:3d:35:71:4f:bb:aa:0f:9b:c3:27:35:
                    b7:6a:e6:3d:25:77:0e:c6:ce:db:0b:a1:26:05:e8:
                    1a:c8:2b:41:4b:f3:1c:aa:62:0a:55:a6:8b:e6:3d:
                    b7:16:18:2b:0f:67:ef:7d:98:96:b4:3a:16:51:09:
                    89:b6:cb:00:dd
                ASN1 OID: prime256v1
                NIST CURVE: P-256
        X509v3 extensions:
            X509v3 Key Usage: critical
                Certificate Sign, CRL Sign
            X509v3 Basic Constraints: critical
                CA:TRUE, pathlen:2
            X509v3 Subject Key Identifier: 
                3E:D6:F7:90:B2:3B:99:4D:B5:62:F4:76:C7:1D:F1:04:F2:3F:4F:67
    Signature Algorithm: ecdsa-with-SHA256
         30:44:02:20:72:ab:fe:33:af:d4:5c:0b:8e:8a:12:cc:e8:26:
         53:e9:12:50:c6:91:3f:4b:35:fc:3f:47:f4:b8:0a:a8:f0:17:
         02:20:2f:8a:b1:4e:bd:d7:c4:ae:08:d8:19:17:b1:60:97:53:
         99:f4:99:ca:2c:c0:ec:d6:46:97:ed:35:85:95:44:6e

ICA:

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            14:92:5d:be:40:c8:97:9d:ef:63:b6:88:b0:ab:97:bb:7f:0f:c4:fa
    Signature Algorithm: ecdsa-with-SHA256
        Issuer: C=US, ST=North Carolina, O=Hyperledger, OU=Fabric, CN=rca.bdk.example.com
        Validity
            Not Before: Jan 22 02:18:00 2022 GMT
            Not After : Jan 24 02:18:00 2022 GMT
        Subject: C=US, ST=North Carolina, O=Hyperledger, OU=Fabric, CN=rca.bdk.example.com
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (256 bit)
                pub: 
                    04:56:ce:7d:3d:35:71:4f:bb:aa:0f:9b:c3:27:35:
                    b7:6a:e6:3d:25:77:0e:c6:ce:db:0b:a1:26:05:e8:
                    1a:c8:2b:41:4b:f3:1c:aa:62:0a:55:a6:8b:e6:3d:
                    b7:16:18:2b:0f:67:ef:7d:98:96:b4:3a:16:51:09:
                    89:b6:cb:00:dd
                ASN1 OID: prime256v1
                NIST CURVE: P-256
        X509v3 extensions:
            X509v3 Key Usage: critical
                Certificate Sign, CRL Sign
            X509v3 Basic Constraints: critical
                CA:TRUE, pathlen:2
            X509v3 Subject Key Identifier: 
                3E:D6:F7:90:B2:3B:99:4D:B5:62:F4:76:C7:1D:F1:04:F2:3F:4F:67
    Signature Algorithm: ecdsa-with-SHA256
         30:44:02:20:72:ab:fe:33:af:d4:5c:0b:8e:8a:12:cc:e8:26:
         53:e9:12:50:c6:91:3f:4b:35:fc:3f:47:f4:b8:0a:a8:f0:17:
         02:20:2f:8a:b1:4e:bd:d7:c4:ae:08:d8:19:17:b1:60:97:53:
         99:f4:99:ca:2c:c0:ec:d6:46:97:ed:35:85:95:44:6e

ICA 在 CA up 時未使用到期時間等參數

ISSUE

說明 (Description)

使用 bdk ca up 啟動 ICA 時，不會使用設定到期時間

種類 (Issue Type)

[ ] Feature Request
[ ] Report Bug
[ ] Other

---

通報問題 (Report Bug)

重現步驟 (Steps to Reproduce)

1. bdk ca up

測試環境 (Environment):

• OS:
• NodeJS Version:
• NPM Version:
• Docker Version:

應呈現結果 (Expected Behavior)

實際呈現結果 (Resulted Behavior)

---

其他說明 (Additional Context)

bdk/src/model/yaml/docker-compose/caComposeYaml.ts

Lines 52 to 62 in e1e7a53

	!upstreamEnabled && csr
	? [
	// CSR (RCA) options
	`FABRIC_CA_SERVER_CSR_CN=${csr.cn}`,
	`FABRIC_CA_SERVER_CSR_HOSTS=${csr.hosts}`,
	`FABRIC_CA_SERVER_CSR_CA_EXPIRY=${csr.expiry}`,
	`FABRIC_CA_SERVER_CSR_CA_PATHLENGTH=${csr.pathlength}`,
	]
	: [
	`FABRIC_CA_SERVER_CSR_HOSTS=${intermediate?.enrollmentHost}`,
	],

起ICA時， upstreamEnabled 為True，docker-compose不會加上這些參數

討論CA參數

ISSUE

說明 (Description)

現行 CA 系列指令的參數會太複雜嗎？有簡化的必要嗎？在這篇討論吧！

種類 (Issue Type)

[ ] Feature Request
[ ] Report Bug
[x] Other

其他說明 (Additional Context)

1. 大部分情況下，ca-name = host = cn，目前也想不到這三者不同的情況，是否該整合成一個參數
2. ica-parentserver-url 現在要求使用者輸入 https://:@hostname 是否拆成3個參數較友善
3. 是否有其他需要優化的參數？

Missing Trie Node

ISSUE

說明 (Description)

Blockscout (-32000) missing trie node logs

種類 (Issue Type)

• Feature Request
• Report Bug
• Other

---

通報問題 (Report Bug)

重現步驟 (Steps to Reproduce)

1. Block already garbage collection (gc)
2. Blockscout restart as new

測試環境 (Environment):

• OS: macOS
• NodeJS Version: 16.13
• NPM Version:
• Docker Version: 20.10.17

應呈現結果 (Expected Behavior)

No error

Please describe the bahavior expected.

實際呈現結果 (Resulted Behavior)

0x21e2aba9ac09c64c0e6f5e02b6f7ae11e4db8b8f@m: (-32000) missing trie node c3888f465bb0d17b8977bca602a1a99897d7c8643e8b2d6b4323b07ca031249f (path )
0x6a275bd5d12d1eea671b7b98e7ffda16b67b51ca@p: (-32000) missing trie node d72aa08d8f55320061f35962e7b7e39f02fb6d07ee1e35be171c6769ed7469bd (path )
0x507143aeac6f0d1bd70909b01c676e1e6c61bee4@l: (-32000) missing trie node b9bdd258d62841cb2ab5d396e6d9317c1e4cc99aefe3f1925a440fbfb5888b33 (path )
0x420f4de35b90c160e7d3161e39371b7763125505@k: (-32000) missing trie node c05aea93665af82a933f8699307eeaab14d1d7b44f6f6ea5a2c603e856de88a6 (path )
0x0c3b00533f967379354ad93486771f81a42f4bc8@p: (-32000) missing trie node d72aa08d8f55320061f35962e7b7e39f02fb6d07ee1e35be171c6769ed7469bd (path )
0x02f74263d1b3ef715f751b6726e18c6ec383d43a@n: (-32000) missing trie node 5d9e12b050bc204a2a84b1480748fa70cd1b21b3b1391a75f3aa0bf95385c711 (path )
0x26c03677cb820ad86b85e47b95d05b5cdab1d066@n: (-32000) missing trie node 5d9e12b050bc204a2a84b1480748fa70cd1b21b3b1391a75f3aa0bf95385c711 (path )
0xa2e182cf01e0d2cb8226a41197d57aebdb58c1bd@o: (-32000) missing trie node 38927c2718411631d444d136f9fdc2780dd4e956dcaa36877aec28ac402760e3 (path )
0x9aa5ccb5d0d52404d2b8efd4c74dcb4eee01f749@o: (-32000) missing trie node 38927c2718411631d444d136f9fdc2780dd4e956dcaa36877aec28ac402760e3 (path )
0x6d743f45324a40033a2297d494da45395adb2ecf@l: (-32000) missing trie node b9bdd258d62841cb2ab5d396e6d9317c1e4cc99aefe3f1925a440fbfb5888b33 (path )
0x50bc55b6800df95718f733be6ef2648a42f68d63@n: (-32000) missing trie node 5d9e12b050bc204a2a84b1480748fa70cd1b21b3b1391a75f3aa0bf95385c711 (path )
0x8f92801950858911046be2d01c49b4e822cb3029@l: (-32000) missing trie node b9bdd258d62841cb2ab5d396e6d9317c1e4cc99aefe3f1925a440fbfb5888b33 (path )
0x9a276bc878ff08cdabb2d37b7710c68ae6ba205d@k: (-32000) missing trie node c05aea93665af82a933f8699307eeaab14d1d7b44f6f6ea5a2c603e856de88a6 (path )
0x7991c05c0a675d05e3e0c30ba4edf72e131e1baa@k: (-32000) missing trie node c05aea93665af82a933f8699307eeaab14d1d7b44f6f6ea5a2c603e856de88a6 (path )
0xe9cd36d5e0d84fd6e9d3de177e5ecd5d58dd96a5@p: (-32000) missing trie node d72aa08d8f55320061f35962e7b7e39f02fb6d07ee1e35be171c6769ed7469bd (path )
0x5e8a5e850b23469574be3ce4899a5e5cfd5c7080@m: (-32000) missing trie node c3888f465bb0d17b8977bca602a1a99897d7c8643e8b2d6b4323b07ca031249f (path )
0xf56f9a5b8a2f8e370c8ab58ae046d871151882c3@m: (-32000) missing trie node c3888f465bb0d17b8977bca602a1a99897d7c8643e8b2d6b4323b07ca031249f (path )
0x9e0e79272e11550102475f1e5c2db517db916035@o: (-32000) missing trie node 38927c2718411631d444d136f9fdc2780dd4e956dcaa36877aec28ac402760e3 (path )
0x74068fe63abce328900f58bffa71fb58a335042a@p: (-32000) missing trie node d72aa08d8f55320061f35962e7b7e39f02fb6d07ee1e35be171c6769ed7469bd (path )
0xed3f194f094447cf400119e0356bfdd835faf16a@p: (-32000) missing trie node d72aa08d8f55320061f35962e7b7e39f02fb6d07ee1e35be171c6769ed7469bd (path )
0x6f831597ff804e1e38fc884e8ca64120887d69aa@k: (-32000) missing trie node c05aea93665af82a933f8699307eeaab14d1d7b44f6f6ea5a2c603e856de88a6 (path )
0x464003bd696c14d2fc434fa10ed1cdd8df944090@l: (-32000) missing trie node b9bdd258d62841cb2ab5d396e6d9317c1e4cc99aefe3f1925a440fbfb5888b33 (path )
0xd273936075ea0187d8bd959a4fb53f624e6b37f5@k: (-32000) missing trie node c05aea93665af82a933f8699307eeaab14d1d7b44f6f6ea5a2c603e856de88a6 (path )

Please describe the behavior that actually occurred.

---

其他說明 (Additional Context)

可能修復解法：加入--gcmode archive 在 validator-docker-compose.yaml

bdk channel ls

ISSUE

說明 (Description)

List channel in peer, orderer or network

種類 (Issue Type)

[x] Feature Request
[ ] Report Bug
[ ] Other

---

新功能 (Feature Request)

增加可閱讀資料

執行 `npm install` 時出現 `gyp ERR! build error`

ISSUE

說明 (Description)

當我執行 npm install 出現以下錯誤訊息

gyp ERR! build error
gyp ERR! stack Error: not found: make

種類 (Issue Type)

[ ] Feature Request
[*] Report Bug
[ ] Other

---

通報問題 (Report Bug)

重現步驟 (Steps to Reproduce)

1. curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
2. git clone https://github.com/cathayddt/bdk.git
3. cd bdk
4. nvm install $(cat .nvmrc )
5. npm i

測試環境 (Environment):

• OS: Ubuntu 20.04.3 LTS (GNU/Linux 5.11.0-1020-gcp x86_64)
• NodeJS Version: v12.22.7
• NPM Version: 6.14.15
• Docker Version: 20.10.9

應呈現結果 (Expected Behavior)

安裝過程中不應該有錯誤訊息

實際呈現結果 (Resulted Behavior)

gyp ERR! build error
gyp ERR! stack Error: not found: make
gyp ERR! stack     at getNotFoundError (/home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/which/which.js:13:12)
gyp ERR! stack     at F (/home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/which/which.js:68:19)
gyp ERR! stack     at E (/home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/which/which.js:80:29)
gyp ERR! stack     at /home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/which/which.js:89:16
gyp ERR! stack     at /home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/isexe/index.js:42:5
gyp ERR! stack     at /home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/isexe/mode.js:8:5
gyp ERR! stack     at FSReqCallback.oncomplete (fs.js:168:21)
gyp ERR! System Linux 5.11.0-1020-gcp
gyp ERR! command "/home/eugene/.nvm/versions/node/v12.22.7/bin/node" "/home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/eugene/bdk/node_modules/cpu-features
gyp ERR! node -v v12.22.7
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok

> [email protected] install /home/eugene/bdk/node_modules/ssh2
> node install.js

gyp ERR! build error
gyp ERR! stack Error: not found: make
gyp ERR! stack     at getNotFoundError (/home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/which/which.js:13:12)
gyp ERR! stack     at F (/home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/which/which.js:68:19)
gyp ERR! stack     at E (/home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/which/which.js:80:29)
gyp ERR! stack     at /home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/which/which.js:89:16
gyp ERR! stack     at /home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/isexe/index.js:42:5
gyp ERR! stack     at /home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/isexe/mode.js:8:5
gyp ERR! stack     at FSReqCallback.oncomplete (fs.js:168:21)
gyp ERR! System Linux 5.11.0-1020-gcp
gyp ERR! command "/home/eugene/.nvm/versions/node/v12.22.7/bin/node" "/home/eugene/.nvm/versions/node/v12.22.7/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "--target=v12.22.7" "rebuild"
gyp ERR! cwd /home/eugene/bdk/node_modules/ssh2/lib/protocol/crypto
gyp ERR! node -v v12.22.7
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
Failed to build optional crypto binding

---

其他說明 (Additional Context)

是缺少某些dependencies？請補充於 README.md

請教一些非技術的問題, 如何因應關於機敏資料定義的改變

關於機敏資料

說明 (Description)

今天參加TBW2022聽到Eric, Evan精彩的talk, 想請教一下目前已經實際開始應用的場景是否有考慮如果一些已經上鏈的資料, 在未來法律修改突然被定義成機敏資料必須要讓使用者可以完整刪除這樣的情況? 畢竟台灣個資法和國外個資法也還是有不同, 也不排除外來對個資的處理也有可能會越來越嚴苛或甚至必須要完全遵守GDPR..

master branch npm install 出現 dependency conflict on MAC M1 (macOS Monterey)

ISSUE

說明 (Description)

執行以下 command

npm install

出現以下錯誤：

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"^4.5.4" from the root project
npm ERR!   peer typescript@">=2.7" from [email protected]
npm ERR!   node_modules/ts-node
npm ERR!     dev ts-node@"^10.4.0" from the root project
npm ERR!   1 more (tsutils)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@"4.0.x || 4.1.x || 4.2.x || 4.3.x || 4.4.x" from [email protected]
npm ERR! node_modules/typedoc
npm ERR!   dev typedoc@"^0.21.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/typescript
npm ERR!   peer typescript@"4.0.x || 4.1.x || 4.2.x || 4.3.x || 4.4.x" from [email protected]
npm ERR!   node_modules/typedoc
npm ERR!     dev typedoc@"^0.21.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /Users/santai/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/santai/.npm/_logs/2022-12-16T02_57_14_742Z-debug-0.log

Please include a summary of the issue.

種類 (Issue Type)

[ ] Feature Request
[ ] Report Bug
[ ] Other

---

新功能 (Feature Request)

希望新增此功能的原因 (Reason for this Feature)

...

可能的解法 (Proposed Solution)

package typedoc 只支援到 typescript 4.4.0 以下的版本，但是 package.json 裡面設定 typescript@"^4.5.4"

---

通報問題 (Report Bug)

重現步驟 (Steps to Reproduce)

1. npm install

測試環境 (Environment):

• OS: macOS monterey
• NodeJS Version: v18.12.0
• NPM Version: 8.19.2
• Docker Version: docker version 20.10.11, build dea9396

應呈現結果 (Expected Behavior)

請詳細說明應呈現的畫面/結果。

Please describe the bahavior expected.

實際呈現結果 (Resulted Behavior)

請詳細說明實際執行呈現的畫面/結果。

Please describe the behavior that actually occurred.

---

其他說明 (Additional Context)