Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Azure Data Factory Activity Iterator Bug

Aperta
  • Qualcosa non va?
#166 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
azure, python
Ambito
backend, testing-qa

Direzione di ricerca

Start by placing pl_package_import.json in pipeline and test_package_import.py in tests, then run the supplied test to reproduce NoRemainingPipelineActivitiesMeetDependencyConditionsError. Inspect activity iteration and dependency evaluation around the Until loop, including the success and failure branches; done means the test completes and activities run in the expected order across iterations.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

The activity iterator does not handle events in the same order that I would expect it to.

In the following scenario:

Image

With activities within the Until loop as below:

Image

The behaviour is not as would be expected. It appears that the addition of the failure condition to refresh the token causes the final activities (within the next If conditional) to not be evaluated. In addition, on the second iteration of the loop, the activities are evaluated out of sequence.

pl_package_import.json
test_package_import.py

Attached above are the files, to run successfully these would need to be added to a directory pipeline for pl_package_import.json and tests for test_package_import.py.

In this particular test, it is expected that it goes into the loop, then it processes the next activity in sequence. As it is incomplete, the condition should assess that it goes onto the next iteration of the Until loop. However, it raises exception NoRemainingPipelineActivitiesMeetDependencyConditionsError.

Removing lines 113 to 278 of the pipeline file fixes this, see the file below. This suggests that there is a bug where activities have a success and failure branch in terms of evaluating the next activities.
pl_package_import.json

I also note that the activities in the next iterations are evaluated out of order. For the second pl_package_import.json (i.e. the one that passes the test) where it compares if it goes into the if statement and runs a pipeline in the event of the conditional being false, the next activity should be a Wait activity, being the first one in the loop, but in reality it is the Web Activity, the second activity in the loop.

Lingua principale
Python
Stelle
135
Fork
43
Merge medio
1h 14m
PR unite (30g)
1

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/data-factory-testing-framework

Tutte le issue di microsoft/data-factory-testing-framework

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.