josh-fell commented on issue #14162:
URL: https://github.com/apache/airflow/issues/14162#issuecomment-1144103758

   FWIW, I'm not able to reproduce this on `main` with Breeze, 2.0.0 in Breeze, 
nor 2.3.0 with Astro CLI. I used the tutorial_taskflow_api_etl example DAG and 
changed `schedule_interval="@daily"`.
   
   **Breeze (Airflow 2.0.0)**
   Commands: `breeze exec`, `airflow dags backfill 
test_tutorial_taskflow_api_etl --start-date 2022-05-01 --end-date 2022-05-05`
   <img width="1439" alt="image" 
src="https://user-images.githubusercontent.com/48934154/171493809-db374bd7-7098-43dc-9acc-1c84c66471b3.png";>
   
   
   **Breeze (main)**
   Commands: `breeze exec`, `airflow dags backfill tutorial_taskflow_api_etl -s 
2022-05-01 -e 2022-05-05`
   <img width="1440" alt="image" 
src="https://user-images.githubusercontent.com/48934154/171489681-a13b98b7-3a87-47c6-835e-448eabc3ac37.png";>
   
   
   **Astro CLI (Astro Runtime 5.0.0, Airflow 2.3.0)**
   Command (directly on webserver container): `docker exec -it 
2-3-0_d06ac9-webserver-1 airflow dags backfill tutorial_taskflow_api_etl -s 
2022-05-01 -e 2022-05-05`
   <img width="1436" alt="image" 
src="https://user-images.githubusercontent.com/48934154/171488115-d3494db2-79d6-4262-b29f-f504880c38f3.png";>
   Command (using built-in Astro CLI command): `astrocloud dev run dags 
backfill tutorial_taskflow_api_etl -s 2022-05-06 -e 2022-05-10`
   <img width="1438" alt="image" 
src="https://user-images.githubusercontent.com/48934154/171488616-0d19a26b-827d-4dcc-a6f0-fae5f7f650be.png";>
   
   @gschwim Does this pickling error still occur on Airflow 2.3.0 with your 
environment setup? Is the only modification made to the example DAG was the 
`schedule_interval` initially? Does setting the `--donot-pickle` flag alleviate 
the issue?
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to