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

CCIP-3414: Make gas fee staleness threshold configurable per chain (#1491) #14734

Merged
merged 10 commits into from
Oct 16, 2024

Conversation

RyanRHall
Copy link
Contributor

Cherry-pick of this PR
On some chains, it is possible the gas price will just always be zero or will be fixed at some constant fee. Make stalenessThreshold per dest chain and have 0 mean no staleness check.

Copy link
Contributor

github-actions bot commented Oct 11, 2024

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

WF: CI Core#7cb01cb

Error 1: Undefined Field in FeeQuoterStaticConfig

Source of Error:
##[error]deployment/ccip/view/v1_6/feequoter.go:83:36: staticConfig.StalenessThreshold undefined (type fee_quoter.FeeQuoterStaticConfig has no field or method StalenessThreshold)

Why:
The error indicates that the StalenessThreshold field or method does not exist in the FeeQuoterStaticConfig type within the feequoter.go file. This could be due to a typo, a missing implementation, or an outdated reference in the codebase.

Suggested fix:
Review the FeeQuoterStaticConfig definition to confirm if StalenessThreshold should be a part of it. If it should, add the missing field or method. If not, remove or update the reference in feequoter.go to align with the current structure of FeeQuoterStaticConfig.

Error 2: Process Completed with Exit Code 1

Source of Error:
##[error]Process completed with exit code 1.

Why:
This error typically indicates that the program terminated with an error state, which in this context is likely due to the previously mentioned compilation error in the Go code.

Suggested fix:
Resolve the compilation error detailed in Error 1. Ensure that all unit tests pass and that there are no compile-time errors in the code before rerunning the workflow. This should help the process exit with a successful code.

@RyanRHall RyanRHall force-pushed the cherry-pick-fee-quoter-staleness-threshold-changes branch from bc8695b to ba02b5f Compare October 11, 2024 15:15
Copy link
Contributor

github-actions bot commented Oct 11, 2024

WF: CI Core#bc8695b

No errors found in this run. 🎉

@RyanRHall RyanRHall requested a review from a team as a code owner October 11, 2024 15:29
@RyanRHall RyanRHall changed the title Make gas fee staleness threshold configurable per chain (#1491) CCIP-3414: Make gas fee staleness threshold configurable per chain (#1491) Oct 11, 2024
Copy link
Contributor

github-actions bot commented Oct 11, 2024

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

WF: CI Core#bd4ce26

Error: Unknown Field in Struct Literal

Source of Error:
##[error]deployment/ccip/deploy.go:550:6: unknown field StalenessThreshold in struct literal of type fee_quoter.FeeQuoterStaticConfig

Why:
The error indicates that the StalenessThreshold field does not exist in the FeeQuoterStaticConfig struct. This could be due to a typo, a recent change in the struct definition, or the field being deprecated or renamed.

Suggested fix:
Check the definition of FeeQuoterStaticConfig in the relevant Go package to confirm the available fields. If StalenessThreshold has been renamed or removed, update the code to use the correct field name or handle the logic differently if the field is deprecated. If it's a typo, correct it to match the intended field name.

@RyanRHall RyanRHall force-pushed the cherry-pick-fee-quoter-staleness-threshold-changes branch from bd4ce26 to 136febb Compare October 15, 2024 14:24
Copy link
Contributor

Solidity Review Jira issue

Hey! We have taken the liberty to link this PR to a Jira issue for Solidity Review.

This is a new feature, that's currently in the pilot phase, so please make sure that the linkage is correct. In a contrary case, please update it manually in JIRA and replace Solidity Review issue key in the changeset file with the correct one.
Please reach out to the Test Tooling team and notify them about any issues you encounter.

Any changes to the Solidity Review Jira issue should be reflected in the changeset file. If you need to update the issue key, please do so manually in the following changeset file: contracts/.changeset/tricky-cups-hammer.md

This PR has been linked to Solidity Review Jira issue:

Copy link
Contributor

github-actions bot commented Oct 15, 2024

WF: CI Core#4939394

No errors found in this run. 🎉

@RyanRHall RyanRHall force-pushed the cherry-pick-fee-quoter-staleness-threshold-changes branch from 0cbcb43 to 4939394 Compare October 15, 2024 14:31
Copy link
Contributor

github-actions bot commented Oct 15, 2024

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

WF: CI Core#c5205c2

1. HTTP 503 Service Temporarily Unavailable error during push request:Flakey Test Detection

Source of Error:
Flakey Test Detection	Re-run tests	2024-10-16T14:31:34.9644495Z 2024/10/16 14:31:34 Error re-running flakey tests: push request failed: status=503, body=<html>
Flakey Test Detection	Re-run tests	2024-10-16T14:31:34.9646642Z <head><title>503 Service Temporarily Unavailable</title></head>
Flakey Test Detection	Re-run tests	2024-10-16T14:31:34.9647703Z <body>
Flakey Test Detection	Re-run tests	2024-10-16T14:31:34.9648621Z <center><h1>503 Service Temporarily Unavailable</h1></center>
Flakey Test Detection	Re-run tests	2024-10-16T14:31:34.9649677Z <hr><center>nginx</center>
Flakey Test Detection	Re-run tests	2024-10-16T14:31:34.9650329Z </body>
Flakey Test Detection	Re-run tests	2024-10-16T14:31:34.9651221Z </html>
Flakey Test Detection	Re-run tests	2024-10-16T14:31:34.9668185Z ##[error]Process completed with exit code 1.

Why: The error occurred because the service that the GitHub Action was trying to push a request to was temporarily unavailable, likely due to server issues or maintenance.

Suggested fix: Implement retry logic with exponential backoff in the GitHub Action to handle temporary unavailability of external services. Alternatively, check the service status and ensure it's available before attempting requests.

@RyanRHall RyanRHall enabled auto-merge October 15, 2024 15:40
RyanRHall and others added 6 commits October 15, 2024 13:30
On some chains, it is possible the gas price will just always be zero or
will be fixed at some constant fee

Make stalenessThreshold per dest chain and have 0 mean no staleness
check
@RyanRHall RyanRHall force-pushed the cherry-pick-fee-quoter-staleness-threshold-changes branch from ceaf096 to 8506e22 Compare October 15, 2024 18:24
@RyanRHall RyanRHall force-pushed the cherry-pick-fee-quoter-staleness-threshold-changes branch from 8506e22 to c5205c2 Compare October 15, 2024 18:38
Copy link
Contributor

github-actions bot commented Oct 16, 2024

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

@cl-sonarqube-production
Copy link

@RyanRHall RyanRHall added this pull request to the merge queue Oct 16, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 16, 2024
@RyanRHall RyanRHall added this pull request to the merge queue Oct 16, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 16, 2024
@RyanRHall RyanRHall added this pull request to the merge queue Oct 16, 2024
Merged via the queue into develop with commit ca71878 Oct 16, 2024
167 checks passed
@RyanRHall RyanRHall deleted the cherry-pick-fee-quoter-staleness-threshold-changes branch October 16, 2024 20:59
@timweri timweri restored the cherry-pick-fee-quoter-staleness-threshold-changes branch October 21, 2024 13:35
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.

5 participants