ccip: Use new unknown address types

[winder]

Use new address types in chainlink-common and chainlink-ccip.

Related:

• https://github.com/smartcontractkit/chainlink-common/pull/832
• https://github.com/smartcontractkit/chainlink-ccip/pull/212

[github-actions[bot]]

WF: CI Core#99aa0ae

No errors found in this run. 🎉

[github-actions[bot]]

Below is an analysis created by an LLM. Be mindful of hallucinations and verify accuracy.

WF: CI Core#03900ae

Error: Incorrect Data Type in Struct Literal

Source of Error:

##[error]deployment/ccip/add_chain_test.go:39:23: cannot use feeds[LinkSymbol].Address().String() (value of type string) as ccipocr3.UnknownEncodedAddress value in struct literal

Why:
The error occurs because the code attempts to assign a string value to a struct field that expects a value of type ccipocr3.UnknownEncodedAddress. This type mismatch leads to a compilation error in the Go language, which is strongly typed.

Suggested fix:
Modify the assignment to convert the string to the expected type ccipocr3.UnknownEncodedAddress. If a direct conversion is not possible, you may need to implement a helper function or method that correctly transforms a string to this type, ensuring that the transformation adheres to the expected format and data integrity required by ccipocr3.UnknownEncodedAddress.

[github-actions[bot]]

WF: CI Core#3071dca

No errors found in this run. 🎉

[github-actions[bot]]

Below is an analysis created by an LLM. Be mindful of hallucinations and verify accuracy.

WF: CI Core#601ab69

Error 1: Test Failures in Go Core Tests

Source of Error:

Core Tests (go_core_tests)	Run tests	2024-10-07T20:13:09.0186351Z Encountered test failures.
Core Tests (go_core_tests)	Run tests	2024-10-07T20:13:09.0186890Z go_core_tests exiting with code 1
Core Tests (go_core_tests)	Run tests	2024-10-07T20:13:09.0206746Z ##[error]Process completed with exit code 1.

Why: The error logs indicate that the Go core tests encountered failures, which caused the test script to exit with a non-zero status code (exit code 1). This typically happens when one or more tests fail their assertions or encounter runtime errors.

Suggested fix: Review the specific test cases that failed, as indicated in the detailed test output. Fix the assertions or handle the runtime errors in the test cases to ensure all tests pass successfully.

Error 2: API Server Not Ready

Source of Error:

Core Tests (go_core_tests)	Print Filtered Test Results	2024-10-07T20:13:10.3744747Z API server not ready yet (attempt 1): exit status 7
...
Core Tests (go_core_tests)	Print Filtered Test Results	2024-10-07T20:13:10.3761599Z API server not ready yet (attempt 29): exit status 7
Core Tests (go_core_tests)	Print Filtered Test Results	2024-10-07T20:13:10.3762174Z API server not ready yet (attempt 30): exit status 7

Why: The logs show repeated attempts to connect to an API server that was not ready, each attempt ending with an "exit status 7". This error typically indicates that the server could not start or become ready within the expected time, possibly due to configuration issues or resource constraints.

Suggested fix: Check the server configuration and ensure it is set up correctly with the right ports and accessible endpoints. Increase the timeout or delay between attempts if the server requires more time to initialize. Additionally, ensure that no other processes are blocking the required ports.

[cl-sonarqube-production[bot]]

Quality Gate passed

Issues
3 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube