Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Apr 29, 2025

The exampleinclude of ours used to have generated "sources" link to link to sources of the examples. This was however gone after recent doc build refactoring.

The problem was the example directive include import and lack of tests folder available on the python path. Both issues fixed in this PR.

Fixes: #49893


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

@boring-cyborg boring-cyborg bot added area:production-image Production image improvements and fixes kind:documentation labels Apr 29, 2025
@potiuk
Copy link
Member Author

potiuk commented Apr 29, 2025

I will have to regenerate the docs for airflow and providers released since the doc restructuring once this one is merged :)

@potiuk potiuk added this to the Airflow 3.0.1 milestone Apr 29, 2025
@potiuk potiuk added the backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch label Apr 29, 2025
@potiuk
Copy link
Member Author

potiuk commented Apr 29, 2025

Hah. Turns out a numbef of examples will need to be moved

@gopidesupavan
Copy link
Member

Hah. Turns out a numbef of examples will need to be moved

oh.. can we patch some paths?

@potiuk potiuk force-pushed the fix-source-linx-in-generated-docs branch from 10f2014 to 58f879e Compare April 29, 2025 19:09
@potiuk potiuk requested a review from ashb as a code owner April 29, 2025 19:09
@potiuk
Copy link
Member Author

potiuk commented Apr 29, 2025

No.. I really had to move a number of examples to "standar" provider - because they belonged there

@potiuk potiuk force-pushed the fix-source-linx-in-generated-docs branch from 58f879e to 0aade65 Compare April 29, 2025 20:07
@potiuk potiuk requested a review from vincbeck as a code owner April 29, 2025 20:07
@potiuk
Copy link
Member Author

potiuk commented Apr 30, 2025

Question. That change will lead to less number of example dags visible when Airflow starts with "load example dags"- becuase most of the example dags belong to "standard" provider now.

But I think it's not necessary a bad thing - because IMHO we had far too many of those there. I'd say we should maybe (separately) make a small change when loading example dags will only load a subset of those, and maybe even load some from the standard provider? WDYT? This would be by far cleanest solution I think.

@kaxil
Copy link
Member

kaxil commented Apr 30, 2025

But I think it's not necessary a bad thing - because IMHO we had far too many of those there.

Agreed

@potiuk potiuk force-pushed the fix-source-linx-in-generated-docs branch from 0aade65 to d2a3ab5 Compare April 30, 2025 10:05
@potiuk potiuk force-pushed the fix-source-linx-in-generated-docs branch from f9f7f14 to 1d0e0f3 Compare April 30, 2025 13:30
@potiuk potiuk force-pushed the fix-source-linx-in-generated-docs branch 3 times, most recently from 7ea66b0 to d58d66a Compare April 30, 2025 15:16
@kaxil kaxil mentioned this pull request Apr 30, 2025
potiuk added a commit that referenced this pull request May 21, 2025
…ath (#50843) (#50877)

The original PR #49978 that fixed generation of proper documentation for
standard provider examples added retrieval of the path by checking
import location for the standard provider. Instead we are now using
direct path to the provider.
(cherry picked from commit 13c6020)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
nailo2c pushed a commit to nailo2c/airflow that referenced this pull request May 21, 2025
…50843)

The original PR apache#49978 that fixed generation of proper documentation for
standard provider examples added retrieval of the path by checking
import location for the standard provider. Instead we are now using
direct path to the provider.
potiuk added a commit to potiuk/airflow that referenced this pull request May 21, 2025
There were two issues with the test after migrating standard provider
examples to ... standard provider (apache#49978) that made the test work only
in Breeze and not in local env:

* bad import of AIRFLOW_ROOT_PATH from scripts
* reading system.standard import during parsing the pytest file

Both issuses fixed here.
potiuk added a commit to potiuk/airflow that referenced this pull request May 21, 2025
There was an issue with the test after migrating standard provider
examples to ... standard provider (apache#49978) that made the test work only
in Breeze and not in local env.
potiuk added a commit that referenced this pull request May 21, 2025
There were two issues with the test after migrating standard provider
examples to ... standard provider (#49978) that made the test work only
in Breeze and not in local env:

* bad import of AIRFLOW_ROOT_PATH from scripts
* reading system.standard import during parsing the pytest file

Both issuses fixed here.
github-actions bot pushed a commit that referenced this pull request May 21, 2025
…50916)

There were two issues with the test after migrating standard provider
examples to ... standard provider (#49978) that made the test work only
in Breeze and not in local env:

* bad import of AIRFLOW_ROOT_PATH from scripts
* reading system.standard import during parsing the pytest file

Both issuses fixed here.
(cherry picked from commit 396810d)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk added a commit to potiuk/airflow that referenced this pull request May 21, 2025
There was an issue with the test after migrating standard provider
examples to ... standard provider (apache#49978) that made the test work only
in Breeze and not in local env.
potiuk added a commit that referenced this pull request May 22, 2025
…50916) (#50924)

There were two issues with the test after migrating standard provider
examples to ... standard provider (#49978) that made the test work only
in Breeze and not in local env:

* bad import of AIRFLOW_ROOT_PATH from scripts
* reading system.standard import during parsing the pytest file

Both issuses fixed here.
(cherry picked from commit 396810d)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk added a commit to potiuk/airflow that referenced this pull request May 22, 2025
There was an issue with the test after migrating standard provider
examples to ... standard provider (apache#49978) that made the test work only
in Breeze and not in local env.
potiuk added a commit to potiuk/airflow that referenced this pull request May 22, 2025
There was an issue with the test after migrating standard provider
examples to ... standard provider (apache#49978) that made the test work only
in Breeze and not in local env.
dadonnelly316 pushed a commit to dadonnelly316/airflow that referenced this pull request May 26, 2025
…50843)

The original PR apache#49978 that fixed generation of proper documentation for
standard provider examples added retrieval of the path by checking
import location for the standard provider. Instead we are now using
direct path to the provider.
dadonnelly316 pushed a commit to dadonnelly316/airflow that referenced this pull request May 26, 2025
There were two issues with the test after migrating standard provider
examples to ... standard provider (apache#49978) that made the test work only
in Breeze and not in local env:

* bad import of AIRFLOW_ROOT_PATH from scripts
* reading system.standard import during parsing the pytest file

Both issuses fixed here.
@kneepdee kneepdee mentioned this pull request May 27, 2025
2 tasks
potiuk added a commit that referenced this pull request May 29, 2025
There was an issue with the test after migrating standard provider
examples to ... standard provider (#49978) that made the test work only
in Breeze and not in local env.
github-actions bot pushed a commit that referenced this pull request May 29, 2025
#50917)

There was an issue with the test after migrating standard provider
examples to ... standard provider (#49978) that made the test work only
in Breeze and not in local env.
(cherry picked from commit 21f4a40)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk added a commit that referenced this pull request Jun 2, 2025
#50917)

There was an issue with the test after migrating standard provider
examples to ... standard provider (#49978) that made the test work only
in Breeze and not in local env.
(cherry picked from commit 21f4a40)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk added a commit that referenced this pull request Jun 2, 2025
#50917) (#51221)

There was an issue with the test after migrating standard provider
examples to ... standard provider (#49978) that made the test work only
in Breeze and not in local env.
(cherry picked from commit 21f4a40)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
kaxil pushed a commit that referenced this pull request Jun 3, 2025
…ath (#50843) (#50877)

The original PR #49978 that fixed generation of proper documentation for
standard provider examples added retrieval of the path by checking
import location for the standard provider. Instead we are now using
direct path to the provider.
(cherry picked from commit 13c6020)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
kaxil pushed a commit that referenced this pull request Jun 3, 2025
…50916) (#50924)

There were two issues with the test after migrating standard provider
examples to ... standard provider (#49978) that made the test work only
in Breeze and not in local env:

* bad import of AIRFLOW_ROOT_PATH from scripts
* reading system.standard import during parsing the pytest file

Both issuses fixed here.
(cherry picked from commit 396810d)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
kaxil pushed a commit that referenced this pull request Jun 3, 2025
#50917) (#51221)

There was an issue with the test after migrating standard provider
examples to ... standard provider (#49978) that made the test work only
in Breeze and not in local env.
(cherry picked from commit 21f4a40)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
sanederchik pushed a commit to sanederchik/airflow that referenced this pull request Jun 7, 2025
…50843)

The original PR apache#49978 that fixed generation of proper documentation for
standard provider examples added retrieval of the path by checking
import location for the standard provider. Instead we are now using
direct path to the provider.
sanederchik pushed a commit to sanederchik/airflow that referenced this pull request Jun 7, 2025
There were two issues with the test after migrating standard provider
examples to ... standard provider (apache#49978) that made the test work only
in Breeze and not in local env:

* bad import of AIRFLOW_ROOT_PATH from scripts
* reading system.standard import during parsing the pytest file

Both issuses fixed here.
sanederchik pushed a commit to sanederchik/airflow that referenced this pull request Jun 7, 2025
)

There was an issue with the test after migrating standard provider
examples to ... standard provider (apache#49978) that made the test work only
in Breeze and not in local env.
jose-lehmkuhl pushed a commit to jose-lehmkuhl/airflow that referenced this pull request Jul 11, 2025
)

There was an issue with the test after migrating standard provider
examples to ... standard provider (apache#49978) that made the test work only
in Breeze and not in local env.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:production-image Production image improvements and fixes backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch kind:documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Example Operator usage does not include import statements

6 participants