<@ULVA73B9P> why this is not working binance_data...
# ask-marvin
a
@Marvin why this is not working binance_data = btc_market_data_binance_pipeline.submit() glassnode_data = btc_market_data_pipeline.submit() market_metrics = btc_market_metrics_pipeline.submit(wait_for=[binance_data, glassnode_data]) onchain = btc_market_onchain_pipeline.submit(wait_for=[binance_data, glassnode_data]) profile = btc_market_profile_pipeline.submit(wait_for=[binance_data, glassnode_data]) indicators_shift = btc_market_indicators_shift_pipeline.submit(wait_for=[binance_data, glassnode_data, market_metrics, onchain, profile])
m
thought for 257.9 seconds
Based on the code you've shared and recent GitHub discussions, I can provide some guidance, but I'll need to know what specific error or behavior you're encountering. However, I can point out a few potential issues and best practices: 1. Modern Dependency Pattern: In Prefect, there's a newer, more type-safe way to handle dependencies. Instead of using
wait_for
, you can use the
depends_on()
method. Your code could be rewritten as:
Copy code
python
binance_data = btc_market_data_binance_pipeline.submit()
glassnode_data = btc_market_data_pipeline.submit()

market_metrics = (
    btc_market_metrics_pipeline
    .depends_on([binance_data, glassnode_data])
    .submit()
)

onchain = (
    btc_market_onchain_pipeline
    .depends_on([binance_data, glassnode_data])
    .submit()
)

profile = (
    btc_market_profile_pipeline
    .depends_on([binance_data, glassnode_data])
    .submit()
)

indicators_shift = (
    btc_market_indicators_shift_pipeline
    .depends_on([binance_data, glassnode_data, market_metrics, onchain, profile])
    .submit()
)
2. Potential Issues to Check: - Are all the pipeline objects actually flow or task objects? They need to be decorated with
@flow
or
@task
- Are you running this code within a parent flow? - Are you getting any specific error messages? To help you more effectively, please provide: 1. The error message you're seeing (if any) 2. The Prefect version you're using 3. How these pipeline objects are defined (are they flows or tasks?) This will help me give you a more targeted solution to your specific issue.