Add chain reader and codec EVM implementation #11842
Merged
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
… POC - Read ChainReader config in from RelayConfig - Add some initialization and validation relay skeletons - Use medianProviderWrapper instead of passing medianContract separately This avoids us having to modify the signature of NewMedianFactory, which would require further modifications to all non-evm repos and chainlink-relay - Add chain_reader_test.go with some basic relay tests Co-authored-by: Jordan Krage <jmank88@gmail.com> - Add chain reader config validation - Add chain reader config validation tests - Add config for chain reader median contract to cr validation testcases - Add unimplemented Encode(), Decode(), GetMaxEncodingSize(), GetMaxDecodingSize() - Add ChainReader() method to mock provider for plugin test - Rename relaymercury.ChainReader to MercuryChainReader, resolve name collisions - Add tests for errors during ChainReader construction - Propagate InvalidConfig & any other errors back to client We should ignore Unsupported until node ops have been given ample time to migrate to the new job spec (including a section for ChainReader config) so that we can remove the old product-specific MedianContract component from MedianProvider. All other errors we can immediately start passing back to the client, letting the core node decide how to handle them (eg. displaying an "invalid job spec" message to the UI if the RelayConfig was invalid or the ContractID missing)
Co-authored-by: Jordan Krage <jmank88@gmail.com>
We had this before, at some point it accidentally got dropped
Also: move test for invalid contract ID to evm_test.go, & add mismatched ChainID test while we're here since it's pretty similar
Co-authored-by: Jordan Krage <jmank88@gmail.com>
…EVM-POC-fix-logs-dir fix logs dir for Solana tests
…er-EVM-POC # Conflicts: # integration-tests/go.mod
nolag
requested review from
samsondav,
RensR,
bolekk,
justinkaseman,
KuphJr,
sdrug,
martin-cll,
connorwstein and
a team
as code owners
|
I see that you haven't updated any README files. Would it make sense to do so? |
nolag
force-pushed
the
rtinianov_different_next_run_sonar_plz
branch
from
e905c3b to
640e138
Compare
|
SonarQube Quality Gate
|
reductionista
approved these changes
Jan 22, 2024
jmank88
approved these changes
Jan 22, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
This was referenced Feb 22, 2024
This was referenced Mar 21, 2024
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.
No description provided.