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

deployment changeset - deploy verifier proxy #16601

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

akuzni2
Copy link
Contributor

@akuzni2 akuzni2 commented Feb 27, 2025

No description provided.

@cl-sonarqube-production
Copy link

Quality Gate failed Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube

Catch issues before they fail your Quality Gate with our IDE extension SonarQube IDE SonarQube IDE

Copy link
Contributor

AER Report: CI Core

aer_workflow , commit , Clean Go Tidy & Generate , Detect Changes , Scheduled Run Frequency , GolangCI Lint (deployment) , Core Tests (go_core_tests) , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , test-scripts , Core Tests (go_core_fuzz) , Core Tests (go_core_race_tests) , lint , SonarQube Scan

1. File is not properly formatted (goimports):[Golang Lint (deployment)]

Source of Error:
Golang Lint (deployment)	2025-02-27T02:20:19.8813316Z ##[error]deployment/data-streams/changeset/v0_5_0/cs_deploy_verifier_proxy.go:5:1: File is not properly formatted (goimports)
Golang Lint (deployment)	2025-02-27T02:20:19.8814498Z 	"github.com/ethereum/go-ethereum/common"
Golang Lint (deployment)	2025-02-27T02:20:19.8814942Z ^

Why: The Go file cs_deploy_verifier_proxy.go is not formatted according to the goimports tool, which checks for proper formatting and organization of imports.

Suggested fix: Run goimports -w deployment/data-streams/changeset/v0_5_0/cs_deploy_verifier_proxy.go to automatically format the file and organize the imports correctly.

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.

1 participant