Investigate possible race conditions when gitsync-ing DAG submodules
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by examining the gitsync behavior around DAG submodules. Reproduce syncs while a DAG is running and add a new submodule, then verify that the running DAG remains consistent and that the new submodule's DAGs are loaded and registered.
Written by the indexing model from the issue text.
Description
Description
As a user of Airflow I want to be sure that DAGs that use submodules are seamlessly updated and registered with Airflow via gitsync. This covers the following:
### Tasks
- [ ] Check that DAGs are consistent i.e. that the state when the DAG is started is the same despite subsequent syncs while the DAG is still running
- [ ] Check that "new" submodules are correctly loaded/registered
- Dominant language
- Rust
- Stars
- 32
- Forks
- 6
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/airflow-operator
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
stackabletech/airflow-operator#898 ·
Maintainers usually reply within 1 day
-
good first issue type/feature-improvement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
stackabletech/airflow-operator#760 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
stackabletech/airflow-operator#697 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
stackabletech/airflow-operator#638 ·
Maintainers usually reply within 1 day
-
type/feature-new
Difficulty 5/5 Over a week Newbie friendliness 25/100
stackabletech/airflow-operator#593 ·
Maintainers usually reply within 1 day
All issues in stackabletech/airflow-operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)Possibly taken @zyl71 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
stackabletech/druid-operator#905 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
bytecodealliance/wrpc#1785 ·
Maintainers usually reply within 1 day
-
2 advisory ignore entries no longer match anything (`quick-xml` already patched in `Cargo.lock`)Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day