-
Notifications
You must be signed in to change notification settings - Fork 183
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
Add linter to CI pipeline #844
Conversation
begmaroman
commented
Jun 22, 2022
•
edited
Loading
edited
- Added linter to CI pipeline
- Fixed all linter nits in the code
Codecov Report
@@ Coverage Diff @@
## develop #844 +/- ##
===========================================
+ Coverage 73.82% 75.61% +1.79%
===========================================
Files 49 49
Lines 5348 5282 -66
===========================================
+ Hits 3948 3994 +46
+ Misses 1170 1055 -115
- Partials 230 233 +3
Continue to review full report at Codecov.
|
…pipeline # Conflicts: # .github/workflows/ci.yml
@begmaroman Could you hold this PR until we merge this one #842? 🙏 There will be many new changes coming from v0.3.0. It might be easier to lint everything after we merge everything from v0.3.0. |
…pipeline # Conflicts: # bridge/setu/processor/clerk_test.go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving because can't review 212 files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to test it very carefully.
Looks like integration tests are failing. Could you check the logs and see why it failed? |
@cffls fixed |
* task delay change * fix * add checks in clu * remove cli checks * add testcase * Set default max number of open files for heimdall service * Add 'heimdall' user during package installation * Fixed helper.UnpackLog function call in the self-healing process (#853) * Add linter to CI pipeline (#844) * Remove dependency on mainnet.toml and mumbai.toml In new CLI, a single binary should work for both mainnet and testnet. This change will remove the dependency on mainnet.toml and mumbai.toml in build time so we won't need to build two different binaries for each network. * fix: remove duplicate import Co-authored-by: Arpit Temani <temaniarpit27@gmail.com> Co-authored-by: Jerry <jerrycgh@gmail.com> Co-authored-by: Roman Behma <13855864+begmaroman@users.noreply.github.com>