-
Notifications
You must be signed in to change notification settings - Fork 0
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
Merge latest Lisk Server #63
Conversation
Integrate Semgrep to CI
…hot-in-indexer Add support for MySQL snapshot in indexer
Migrate from npm to yarn
Co-authored-by: Vardan Nadkarni <[email protected]>
…-metadata-endpoints
…-blockchain-apps-metadata-endpoints' into 1752-no-response-on-blockchain-apps-metadata-endpoints
…pps-metadata-endpoints No response on blockchain apps metadata endpoints
Update Lisk SDK to v6.0.0-rc.0
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
const { cacheCleanup } = require('./cache'); | ||
const { formatTransaction } = require('./formatter'); |
Check notice
Code scanning / Semgrep
Semgrep Finding: javascript.lang.correctness.useless-assign.useless-assignment Note
const { formatTransaction } = require('./formatter'); | ||
const { encodeCCM } = require('./encoder'); |
Check notice
Code scanning / Semgrep
Semgrep Finding: javascript.lang.correctness.useless-assign.useless-assignment Note
Welcome to Codecov 🎉Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment. Thanks for integrating Codecov - We've got you covered ☂️ |
da0a0b8
to
f836ba9
Compare
What was the problem?
This PR resolves #62