TRASH test debug logging for config poller in staging

[samsondav]

Requires

Supports

[github-actions]

AER Report: CI Core

aer_workflow , commit , Detect Changes , Clean Go Tidy & Generate , Scheduled Run Frequency , Flakeguard Root Project / Get Tests To Run , GolangCI Lint (.) , Core Tests (go_core_tests) , test-scripts , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , Flakeguard Deployment Project , Core Tests (go_core_fuzz) , Core Tests (go_core_race_tests) , Flakeguard Root Project / Run Tests , Flakeguard Root Project / Report , lint , SonarQube Scan , Flakey Test Detection

1. Integer overflow conversion error: Golang Lint

Source of Error:

Golang Lint (.) 2024-12-19T19:16:05.6365784Z ##[error]core/services/llo/delegate.go:149:56: G115: integer overflow conversion int -> int32 (gosec)
Golang Lint (.) 2024-12-19T19:16:05.6367536Z 				Database: d.cfg.NewOCR3DB(int32(i)),
Golang Lint (.) 2024-12-19T19:16:05.6368552Z 				 ^

Why: The error is caused by a potential integer overflow when converting an int to an int32. This can happen if the int value exceeds the range that can be represented by an int32.

Suggested fix: Ensure that the value being converted to int32 is within the range of int32 before performing the conversion. You can add a check to validate the value or handle the overflow case appropriately.

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

[github-actions]

I see you added a changeset file but it does not contain a tag. Please edit the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

🎖️ No JIRA issue number found in: PR title, commit message, or branch name. Please include the issue ID in one of these.

[cl-sonarqube-production]

Quality Gate failed

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

See analysis details on SonarQube

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