Enable writing to the verifier alliance test database in staging #1719
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
* Refactor database utils into class * add commented SOURCIFY_POSTGRES_SCHEMA, ALLIANCE_POSTGRES_SCHEMA in .env.dev * add custom schema comment default public
add metis mainnet and testnet
* Added Zircuit Testnet and Mainnet * Zircuit update
* Enabling Flare Mainnet Chain-14 support * Fixing issue * Fixing issue
…CE2dF4C69aA809De5b9318a3D4452D86BE to partial (#1705)
* Add generic APIKey support in chain RPCs, instead of Alchemy Infura etc. * Mark rpcs with trace_transaction support * Throw when API key not found, add QUICKNODE_API_KEY env * Fix typo in RPC type * Fix extracting wrong fields from the traces * Fix checking address created by the creatorTxHash for create2 For contracts created with create2 and factories, the old way of checking the address being created with tx.from and tx.nonce does not work. Instead we can use the already provided address in the trace. For EOA created ones, we can use the one found in the txReceipt. * Fix build due to unused function * Add tests for traces, install sinon et. al. to lib-sourcify * Add chains that have `trace_transaction` support in Quicknode * Add creationbytecode extractor for `debug_traceTransaction` traces. * Add chains with trace `debug_traceTransaction", add Arbitrum Nova Etherscan * Fix Alchemy type chain * Show traceSupportedRPCs in /chains response. Don't show API Keys in the response * Fix type error `findCreateInDebugTraceTransactionCalls` not being copied over to `testChains` * Add comments to `traceSupportedRPCs` * Add quicknode subdomains as option * Fix typing and env handling * Fix typo
The changes adds the sourcify-server package to be published to npm. It also adds a check to only publish the packages in their own tagged CI runs. Previously e.g. when there was a new tag for theese packages, both lib-sourcify and bytecode-utils's CI runs tried to publish both packages. This results in the first one succeeding and publishing both packages but the second one to fail. Now we check to only publish the package in their corresponding tag CI builds.
|
This needs a rebase after rewriting the staging history |
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.
This PR simply enables the
WStorageIdentifiers.AllianceDatabasein the staging configuration underwriteOrWarnstorage services.