-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add zkevm to safe models #5758
Add zkevm to safe models #5758
Conversation
L1 singleton 0x41675C099F32341bf84BFc5382aF534df5C7461a L2 singleton 0x29fcB43b46531BcA003ddC8FCB67FFE91900C76
Models updated are: - safe_native_transfers.all.sql -> Added safe_zkevm_matic_transfers - safe_safes_all.sql -> Added safe_zkevm_safes - safe_transactions_all.sql -> safe_zkevm_transactions
Workflow run id 8616763482 approved. |
Workflow run id 8616849715 approved. |
Workflow run id 8616849913 approved. |
Workflow run id 8616976835 approved. |
Workflow run id 8616977066 approved. |
Workflow run id 8617132586 approved. |
Workflow run id 8617132912 approved. |
gm @jeff-dude, We are implementing the spells for tracking Safe data on zkevm. Currently, we have an error showing that one of our spells depends on the model |
gm daniel. dbt requires you to establish the sources in yml files. please look to add new base sources here: |
Workflow run id 8627008775 approved. |
Workflow run id 8627008824 approved. |
# Conflicts: # sources/_base_sources/zkevm_base_sources.yml
Workflow run id 8627075190 approved. |
Workflow run id 8627075278 approved. |
Workflow run id 8633229278 approved. |
Workflow run id 8633229382 approved. |
Base model is implemented @jeff-dude Now facing an error that a decoded smart contract is not found (1st screenshot). But I see in the decoded contracts that the smart contract exists |
Co-authored-by: jeff-dude <102681548+jeff-dude@users.noreply.github.com>
Co-authored-by: jeff-dude <102681548+jeff-dude@users.noreply.github.com>
Workflow run id 8800647074 approved. |
Workflow run id 8800647247 approved. |
Workflow run id 8800649180 approved. |
Workflow run id 8800649527 approved. |
Workflow run id 8800721358 approved. |
Workflow run id 8800721486 approved. |
Workflow run id 8800726275 approved. |
Workflow run id 8800726757 approved. |
Workflow run id 8801274135 approved. |
Workflow run id 8801274446 approved. |
Co-authored-by: jeff-dude <102681548+jeff-dude@users.noreply.github.com>
Workflow run id 8812118137 approved. |
Workflow run id 8812118513 approved. |
Workflow run id 8812122551 approved. |
Workflow run id 8812123092 approved. |
Thank you for the latest feedback @jeff-dude @Hosuke. Once again, all tests passed. Hopefully we can merge this PR now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the patience, let's get it merged now
Thank you for contributing to Spellbook!
Thank you for taking the time to submit code in Spellbook. A few things to consider:
Best practices
To speed up your development process in PRs, keep these tips in mind:
readme
) and rundbt compile
target/
directory to copy/paste and run on Dune directly for initial query testingWHERE
filter for only ~7 days of history on large source tables, i.e.ethereum.transactions
Incremental model setup
COALESCE()
as needed on key column(s), otherwise the tests may fail on duplicates🪄 Use the built CI tables for testing 🪄
Once CI completes, you can query the CI tables and errors in dune when it finishes running.
run initial models
andtest initial models
, there will be a schema that looks like this:test_schema.git_dunesql_4da8bae_sudoswap_v2_base_pool_creations
Leverage these tables to perform QA testing on Dune query editor -- or even full test dashboards!
Spellbook contribution docs
The docs directory has been implemented to answer as many questions as possible. Please take the time to reference each
.md
file within this directory to understand how to efficiently contribute & why the repo is designed as it is 🪄Example questions to be answered:
Please navigate through the docs directory to find as much info as you can.
Note: happy to take PRs to improve the docs, let us know 🤝