-
Notifications
You must be signed in to change notification settings - Fork 53
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
Release/2.12.0 ccip1.4 #1164
Closed
Closed
Release/2.12.0 ccip1.4 #1164
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(cherry picked from commit 15fab1d)
…ctx-v2.12.0 Cherry pick BCF-3221 - core/services: fix ocrWrapper saveError contexts
(cherry picked from commit 3502176)
changed spammy error log to debug
Signed-off-by: Sneha Agnihotri <[email protected]>
…g_cherrypick Updating changelog for 2.12.0 with cherry pick fix
… transmitter on OCR2 aggregator (#13221) * Implement forwarder OCR2 fallback if fwd not present as a transmitter * Add changeset
…allback-feature-cherry-pick BCF-3225 - Implement forwarder fallback if forwarder not present as a…
* Fix changelog
* Fixed CPU usage issues caused by inefficiencies in HeadTracker * added comments * revert heads back to the fix (cherry picked from commit 6f1ebca)
…ise-headtracker-2-12 Hotfix/bci 3285 optimise headtracker (cherry pick for 2.12)
Signed-off-by: Sneha Agnihotri <[email protected]>
…2.12.0-changelog-bugfixes Update CHANGELOG for 2.12.0 bugfixes
* fix: Decouple ChainType from config string * fix: receiver name and failing test * test: enhance config test to test for xdai specifically * refactor: directly unmarshal into ChainType * fix: validation * test: fix TestDoc/EVM * test: add xdai to warnings.xtar
[SHIP-2001] Cherry Pick - Decouple ChainType Setting (#13272)
Co-authored-by: Domino Valdano <[email protected]>
…nly-fifth-word BCF-3244 Index only the fifth word to reduce the db size overhead #13315
* Add special transmitter for OCR2 feeds * Add ocr2FeedsTransmitter FromAddress() * Cherry-pick some forwarders context changes from (#13171)
* Improve ocr2FeedsTransmitter FromAddress() fallback * Fix forwarders test error assert
…r2-transmitter BCF-3243 - Cherry pick Add special transmitter for OCR2 feeds (#13323)
Signed-off-by: Sneha Agnihotri <[email protected]>
…changelog-update Update 2.12.0 Changelog with bugfixes
…dge-task-timeout core/services/pipeline: bridge task must continue after cancellation (
core/services/pipeline: hide deadline from monitor
Signed-off-by: Sneha Agnihotri <[email protected]>
…changelog-date-2.12.0 Finalize date on changelog for 2.12.0
## Motivation ## Solution
* zkSync L1 Oracle gas Price * fix tests & issues * addressed comments * added changeset * Addressed comments Merging the commit smartcontractkit/chainlink@c6f1b30 ## Motivation Adding a Rollup GasPrice calculation oracle for zksync DA gasPrices Ticket - https://smartcontract-it.atlassian.net/browse/SHIP-1988 ## Solution --------- Co-authored-by: Rens Rooimans <[email protected]>
…s (#13336) (#1058) Cherry-pick of #13336 Similar to what we have for 2.11 release #946 --------- Co-authored-by: Dmytro Haidashenko <[email protected]>
…1157) Commit's Roots cache stores block_timestamps for the CommitReports, but when reorgs happens block_timestamp can also change because TX could be included in a different block. Example scenario: CommitRoot with 10:30:00 UTC block timestamp is inserted with `AppendUnexecutedRoot` (so it's block_timestamp is persisted in the cache). Then reorg happens on the destination and the same CommitRoot is inserted into the blockchain but let's say with 10:29:00 UTC (different block_time), which is never updated. Commit Roots cache returns persisted 10:30:00 as the oldest block timestamp and we keep searching LogPoller using the wrong lower bound filter - this Commit Root never pops up in the execution because it's never returned from DB ## Motivation ## Solution
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Solution