Closed potter-sun closed 1 year ago
Pull request analysis by VIZIPI
Below you will find who is the most qualified team member to review your code. This analysis includes his/her work on the code included in this Pull request, in addition to their experience in code affected by these changes ( partly found within the list of potential missing files below ) Feedback always welcome
Match % | Person | Commit Count | Common Files |
---|---|---|---|
76.92 % | AbigailDeng | 47 | 10 |
30.77 % | lhoopox | 2 | 4 |
File | Percentile | rate |
jest.browser.config.js | 50.00 % | 1 out of 2 times |
types/util/proto.d.ts | 50.00 % | 1 out of 2 times |
tsconfig.json | 50.00 % | 1 out of 2 times |
types/index.d.ts | 50.00 % | 1 out of 2 times |
types/wallet/index.d.ts | 50.00 % | 1 out of 2 times |
README.md | 50.00 % | 1 out of 2 times |
CHANGELOG.md | 50.00 % | 1 out of 2 times |
test/unit/util/bloom.test.js | 50.00 % | 1 out of 2 times |
types/util/keyStore.d.ts | 50.00 % | 1 out of 2 times |
test/unit/chain/index.test.js | 50.00 % | 1 out of 2 times |
95.95%
[dist/aelf.cjs.js.map] 68.02%
[src/util/bloom.js] 97.57%
[dist/aelf.umd.js] 95.95%
[dist/aelf.umd.js.map] 80.97%
[src/util/utils.js] 99.60%
[package.json] 0.00%
[test/e2e/wallet.test.js] 0.00%
[src/index.js] 99.19%
[yarn.lock] 97.57%
[dist/aelf.cjs.js]
Google Chrome 115.0.5790.102 produces incorrect SHA-256 hashes
When js-sha256 is used in chrome, there will be occasional problems in generating hash. Refer to the following method to use @aws-crypto/sha256-js
reference link: js-sha256 issue