Skip to content
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

Publish block V1 flag fix #585

Merged
merged 3 commits into from
Feb 15, 2024
Merged

Publish block V1 flag fix #585

merged 3 commits into from
Feb 15, 2024

Conversation

avalonche
Copy link
Collaborator

@avalonche avalonche commented Feb 13, 2024

πŸ“ Summary

Same as #582 but with some linter fixes and comments addressed as for some reason the linter was panicking

β›± Motivation and Context

See #581

πŸ“š References


βœ… I have run these commands

  • make lint
  • make test-race
  • go mod tidy
  • I have seen and agree to CONTRIBUTING.md

USE_V1_PUBLISH_BLOCK_ENDPOINT was accidentally using the v2 publish endpoint when set instead of v1, and vice versa.
@codecov-commenter
Copy link

codecov-commenter commented Feb 13, 2024

Codecov Report

Attention: 9 lines in your changes are missing coverage. Please review.

Comparison is base (d8a0d7b) 36.22% compared to head (7ae5cbc) 30.44%.

Files Patch % Lines
common/types.go 0.00% 6 Missing ⚠️
beaconclient/prod_beacon_instance.go 0.00% 3 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #585      +/-   ##
==========================================
- Coverage   36.22%   30.44%   -5.79%     
==========================================
  Files          24       41      +17     
  Lines        5267     6268    +1001     
==========================================
  Hits         1908     1908              
- Misses       3112     4113    +1001     
  Partials      247      247              
Flag Coverage Ξ”
unittests 30.44% <0.00%> (-5.79%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

β˜” View full report in Codecov by Sentry.
πŸ“’ Have feedback on the report? Share it here.

@avalonche avalonche force-pushed the publish-block-fix branch 10 times, most recently from 7ae5cbc to 0e75ea2 Compare February 14, 2024 01:36
@avalonche
Copy link
Collaborator Author

for some reason the linter was panicking in #582, this includes a linter upgrade

@avalonche avalonche changed the title Publish block fix Publish block V1 flag fix Feb 14, 2024
@avalonche avalonche marked this pull request as ready for review February 14, 2024 16:50
@@ -30,6 +30,7 @@ linters:
- deadcode
- varcheck
- interfacebloat
- exhaustruct
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why disable this linter rule?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it was causing too many linter issues as there are many paths that are not ignored. I will have a follow up to properly update the go version and linter

@@ -14,7 +14,7 @@ jobs:
- name: Set up Go
uses: actions/setup-go@v3
with:
go-version: ^1.20
go-version: ^1.21
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could use go 1.22

@@ -1,6 +1,6 @@
module github.com/flashbots/mev-boost-relay

go 1.20
go 1.21
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could use go 1.22

Copy link
Collaborator

@metachris metachris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@avalonche avalonche merged commit 108d5e3 into main Feb 15, 2024
6 checks passed
@avalonche avalonche deleted the publish-block-fix branch February 15, 2024 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants