forked from smartcontractkit/chainlink
-
Notifications
You must be signed in to change notification settings - Fork 0
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
[pull] develop from smartcontractkit:develop #630
Open
pull
wants to merge
10,000
commits into
kingdavid6336:develop
Choose a base branch
from
smartcontractkit:develop
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1,502,034
−372,659
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
* add helper to build solana programs * unused var * wip * remove extra file * wip after rebase * move file * add file * bump sha * bump sha * fix path * allow optional cleaning * remove test helper change * test commit * feat: solana tooling dev * test * Update cs_deploy_chain_test.go * Revert "feat: solana tooling dev" This reverts commit 6bb66ee. * cleaning * cleaning * cleaning --------- Co-authored-by: yashnevatia <[email protected]>
* deploy transferable * feat: solana tooling dev * cleaning * Revert "feat: solana tooling dev" This reverts commit 6bb66ee. * cleaning --------- Co-authored-by: yashnevatia <[email protected]>
* prepping to run load tests on aws * load test adjustments * working refactor to speed up deployment * 10 lanes load test, working loki * somec hanges * changes for pr * changesets keep changing * add concurrency * go lint * 30 chains * add logging, make the setup functional * pr changes * export functions for crib to use * PR comments * revert import changes that was breaking build * PR comments, improvements to metrics management * cleanup * fix imports * imports * all changes, mostly imports and parallelization of changesets * parallelization * lint * lint * changes to support round num meetric * Deploy transferable tokens to test message and tokens with data * metrics management * revert changeset parallelization, go mods * shadow variables * go mod * lint * WIP add token pools for link token in crib deployment * WIP making link work * cleaning up and parallelizing router approval per sender * use enum names in merics * use sync map to coordinate map changes * merge issues * golint, goimports * Grant burn and mint roles to token pools * clean up * goimport --------- Co-authored-by: asoliman <[email protected]>
* fix(cre-300): allow state view missing evm * linter, test
Currently a new sub-package /deployment/ccip/changeset/solana was added, and only one team was added. Refactors and infra changes have no global owner there.
* changes * mcms state updates * more update * fix lint
* try to cache build artifacts * use bash * change dir * add token back * try artifact found * allow upload failure * try query param * remove apostrophe * use curl to download * try with header * loop through unexpired
This preserves the existing function type (as an alias to a new function type, ChangeLogic). It adds also two function types ChangeLogic and PreconditionVerifier, to encapsulate the logic of these two functions. The interface exposes an Apply and a VerifyPreconditions method. The aforementioned function types can be used with a convenience function to generate an implementation of ChangeSetV2. Alternatively, a full implementation of the interface can be built using a struct that implements those methods. Also: * Rework ChangesetApplication to pass around an interface ConfiguredChangeSet, which can be generic, and therefore avoid a lot of mess in dealing with the WrapChangeset stuff. * Pull out WrapChangeset, which existed to handle some generics which are now handled by the ConfiguredChangeSet interface. * Wire in validation to the execution of changesets in the test infrastructure, and add some tests to make sure that works.
* chore(cre): refactor startup * cleanup
* small fixes here and there * use event resubscriber to bypass websocket issues * use lggr instead of fmt.println * goimport
* Add AptChain to deployments * Update aptos-go-sdk and use interfaces for environment * go mod tidy * Update names * Add changeset
* WIP, almost working... last step fails, when forwarder calls DF cache * working version * use newer PoR workflow * now its broken again * Update gethwrappers * go back to previous config, where all steps were correcty configured * use older config * fix port * use debug consumer contract * WORKING VERSION * remove mock streams capability * passes with workflow registry deployed with c/d * passes with keystone consumer deployed with c/d * passes with keystone forwarder deployed with c/d * remove some deps * allow to use chainlink-cli * restore old KeystoneFeedsConsumer.sol contract * try to run the test in CI * fix integration workflow * move the function * use existing env vars to get the image, use e2e tests workflow version that sets GH_TOKEN as env var available to tests * add missing PRIVATE_KEY env var * pass optional roles for GATI to be able to read from repositories * add some comments, update e2e workflow commit * add comments * fix integration tests workflow file * newer workflow version * update token name and workflow version * do not use chainlink CLI in the CI for now (we need a token that can access it) * fix env var name in CI * fix capability reference * clean up the workflow test * move capability test to smoke subfolder * restore old versions of feeds consumer wrapper * rename GITHUB_TOKEN env var to GITHUB_API_TOKEN * try one more approach to resolving placeholder env var * adjust env file to new location * revert testing-related changes to integration tests workflow * fix lints * use function from chainlink-common to generate workflow id, define new constants for binary file names * add JD * use C/D to setup all contracts * add extra debug information * fix lint * poll config every 500ms * change polling interval to 1s * fix config polling intervnal * use only chainlink/deployments when interacting with contract * JD is failing to create jobs due to a bug and authorization issue * do not use JD to setup jobs * CR changes * adjust to latest changes, move some configs to TOML * CR changes * move comments around * add test modification guideline and better debugging * fix config validations * fix lints * use fixed JD version in the CI * remove workflow registration artifact file * restore older environment file * get p2p ide from node labels, more comments, use contractset * fix lints and remove superfluous methods * dynamic transmission schedule * try out chainlink-cli in the CI * use configurable workflow_id also when registering the workflow * support configurable capabilities/chainlink-cli versions * remove unused struct * fix TOML * make chainlink-cli os/arch aware and extract it to the current folder * run chainlink-cli from current directory * use absolute path when running chainlink-cli * fix if condition * add ocr3 config accidentally deleted when resolving merge conflicts * add info about JD image to guidelines * code review changes + renaming of chainlink-cli to CRE CLI + configuration simplification * try 2 dons * works, but only write is remote, not any other capability * added code that allows to create 1-2 dons easily * add bit more logging, do not add capabilities don to p2p mesh * working 2 don version * support don type & capabilities in TOML config * streamline code further * always intialise peering * use same transmission schedule regardless of DON number * fix go.mods + changeset * fix lint and ci config * add nodeset flags validations * update config for CI test * typos, better comments, clean imports, cleaner clean up function and failure debugging working with multiple DONs * update PoR test documentation * CR#1: 1 environment to rule them all * use string flags * extract worker node config to separate function * update guidelines.md * fix lints --------- Co-authored-by: app-token-issuer-infra-releng[bot] <120227048+app-token-issuer-infra-releng[bot]@users.noreply.github.com>
* bump foundry * bump npm deps * bump solhint * changeset * add default.allow_internal_expect_revert
* deployment: support config overrides in memory nodes * bump cl-ccip * bump cl-ccip to main sha * fix lint * goimports * bump again
* Migrate CCIP releated changesets to dedicated dir * Use corrected package name in changesets * Fix path to changelog generator * WIP: temporarily delete unused and non-CCIP changesets * Run pnpm install * Consume changesets for CCIP Contracts v1.6.0 Signed-off-by: chainchad <[email protected]> * Add changeset configs back --------- Signed-off-by: chainchad <[email protected]>
…16368) * fix: execute all operations from proposals when using new mcms lib As opposed to executing "per chain". The existing code that executed per chain was broken as it (1) did not build the executors map properly, (2) did not skip execution of operations from different chains in the inner for loop, and (3) uses the `IsReady` call, which checks the readiness of *all* operations, regardless of chain. The new implementations simply executes all the proposal operations, in order, regardless of chain. It seems to suit the requirements of the existing changeset tests. * review: drop unnecessary "chains" map * review: drop unnecessary chainSelectors map
* parallelize operations in the deployer group * goimport
* nonce manager checks * fixes
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )