Skip to content

Status of testing Providers that were prepared on August 07, 2025 #54209

Closed

Description

@eladkal

Body

I have a kind request for all the contributors to the latest provider distributions release.
Could you please help us to test the RC versions of the providers?

The guidelines on how to test providers can be found in

Verify providers by contributors

Let us know in the comments, whether the issue is addressed.

These are providers that require testing as there were some substantial changes introduced:

Provider airbyte: 5.2.3rc1

Provider amazon: 9.12.0rc1

Provider apache.tinkerpop: 1.0.3rc1

Provider cncf.kubernetes: 10.7.0rc1

Provider common.sql: 1.27.5rc1

Provider databricks: 7.7.1rc1

Provider edge3: 1.1.3rc1

Provider fab: 2.4.0rc1

Provider google: 17.1.0rc1

Provider microsoft.azure: 12.6.1rc1

Provider microsoft.winrm: 3.11.0rc1

Provider openlineage: 2.6.1rc1

Provider postgres: 6.2.3rc1

Provider redis: 4.3.0rc1

Provider samba: 4.10.3rc1

Provider sftp: 5.3.4rc1

Provider slack: 9.1.4rc1

Provider smtp: 2.2.0rc1

Provider snowflake: 6.5.2rc1

Provider standard: 1.6.0rc1

Provider trino: 6.3.3rc1

All users involved in the PRs:
@fritz-astronomer @Dev-iL @eladkal @Lee-W @gopidesupavan @dominikhei @isaiahiruoha @Prasanth345 @seanghaeli @vincbeck @jroachgolf84 @nailo2c @sjyangkevin @MaksYermak @LipuFei @Jasperora @GrumpyCat51

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.

Activity

  1. added
    kind:metaHigh-level information important to the community
    on Aug 7, 2025
  2. LipuFei commented on Aug 7, 2025

    @LipuFei
    Contributor

    Hi @eladkal , #53542 works for me.

  3. potiuk commented on Aug 7, 2025

    @potiuk
    Member

    Did the PMC member verification all looks good. But I am -1 on standard. Repeating the arguments from devlist discussion:

    Technically this is not a regression - because we have released it in 1.5.0 but we had #54124 (comment) that Pavan found and already fixed (I just merged) in #54214

    Since this is affects PythonVirtualenv (badly), I think we should fix it rather quickly and have rc2 for standard provider (especially that the fix is already in)

  4. gopidesupavan commented on Aug 7, 2025

    @gopidesupavan
    Member

    found one more issue, created latest package locally and ran example its giving me this error. it seems atleast the default python version needs to be set for uv.

    Image

    Fix is coming..

  5. gopidesupavan commented on Aug 7, 2025

    @gopidesupavan
    Member

    It affects mainly when UV is installed and here its default to auto to check https://github.com/apache/airflow/blob/main/providers/standard/src/airflow/providers/standard/utils/python_virtualenv.py#L48, i think its better to handle this setting default python version?

  6. potiuk commented on Aug 7, 2025

    @potiuk
    Member

    I think you should use "path to python" (that's what venv expects) - "python" is not a valid path ?

  7. gopidesupavan commented on Aug 7, 2025

    @gopidesupavan
    Member

    I think you should use "path to python" (that's what venv expects) - "python" is not a valid path ?

    nah this was failing to create venv given provided path, the command its running this one eg:

    Executing cmd: uv venv --allow-existing --seed --python python /var/folders/36/wmkhxjrx523cl98ggtm496m00000gn/T/venvwf85vx2b
    
    Output:: source="airflow.utils.process_utils"
    [2025-08-07, 16:25:34] INFO -   × No interpreter found for executable name `python` in managed installations: source="airflow.utils.process_utils"
    [2025-08-07, 16:25:34] INFO -   │ or search path: source="airflow.utils.process_utils"
    

    so here --python python is not recognising python as valid interpreter. as per this https://docs.astral.sh/uv/reference/cli/#uv-python the request format we are using wrong? 🤔

  8. gopidesupavan commented on Aug 7, 2025

    @gopidesupavan
    Member

    okay i just ran that command in breeze it gives me this: so if the interpreter is set as python in system then there is no issue, otherwise its failing.

    Should we default to some version or leave it as empty ? i think this error is valid if there is no interpreter configures then user should provide which python version they want use ?

    Image
  9. aaron-y-chen commented on Aug 8, 2025

    @aaron-y-chen
    Contributor

    I've tested my part on my local device, looking good!

  10. potiuk commented on Aug 8, 2025

    @potiuk
    Member

    okay i just ran that command in breeze it gives me this: so if the interpreter is set as python in system then there is no issue, otherwise its failing.

    Let's take it offline :) -> I don't think that is a "bug" - possibly an improvement in diagnostics/defaults :)

  11. Prasanth345 commented on Aug 8, 2025

    @Prasanth345
    Contributor

    Hi @eladkal , #53927, Tested the fix for duplicate edge_job insertions in edge3 provider (v1.1.3). Everything is working as expected — no issues found.

  12. Lee-W commented on Aug 8, 2025

    @Lee-W
    Member

    Tested apache-airflow-providers-standard==1.5.0 with apache-airflow==3.0.4rc2.

    If a dag does not have HITLOperator, it works as expected. If a dag contains HITLOperators, it failed as expected.


    I'd like to point out that a dag containing HITLOperators with Airflow < 3.1 kills the dag processor due to AirflowOptionalProviderFeatureException not caught in

    def _pre_import_airflow_modules(file_path: str, log: FilteringBoundLogger) -> None:
    """
    Pre-import Airflow modules found in the given file.
    This prevents modules from being re-imported in each processing process,
    saving CPU time and memory.
    (The default value of "parsing_pre_import_modules" is set to True)
    :param file_path: Path to the file to scan for imports
    :param log: Logger instance to use for warnings
    """
    if not conf.getboolean("dag_processor", "parsing_pre_import_modules", fallback=True):
    return
    for module in iter_airflow_imports(file_path):
    try:
    importlib.import_module(module)
    except ModuleNotFoundError as e:
    log.warning("Error when trying to pre-import module '%s' found in %s: %s", module, file_path, e)
    . It failed as expected, but I'm a bit not sure whether it's how we want it to fail

    or should we change it to ImportError instead

  13. olegkachur-e commented on Aug 8, 2025

    @olegkachur-e
    Contributor

    Checked the #53707, #53865, #54014, all looks good.

  14. pierceroberts commented on Aug 8, 2025

    @pierceroberts
    Contributor

    @eladkal Anything I need to do specifically for #51503?
    It's adding a few debug logs and updating a test.
    The pipeline passed and tests passed locally.

  15. gopidesupavan commented on Aug 8, 2025

    @gopidesupavan
    Member

    Verified my changes LGTM.

  16. jason810496 commented on Aug 9, 2025

    @jason810496
    Member

    There are still some concerns regarding the Redis provider that need to be discussed for AIP-82: Add RedisPubSubMessageQueueProvider, related dicussion #53556 (review) .

    We might need to exclude Redis Provider for this batch release.
    cc @eladkal

  17. sjyangkevin commented on Aug 10, 2025

    @sjyangkevin
    Contributor

    The following tests have been done for #54043. In 3.1.0+, should be good, but some caveats we can have a look into it.
    CC: @Lee-W , @guan404ming

    Unit Test

    breeze shell --python 3.12 --backend postgres --db-reset
    pip install apache-airflow-providers-fab==2.4.0rc1
    cd providers/fab/tests/unit/
    pytest --log-level=INFO -s fab/auth_manager
    

    HITL-related permission test
    Image
    other tests related to fab/auth_manager
    Image

    Airflow Manual Functional Test

    In Airflow < 3.1.0, DAG processor will not start when there is a HITL DAG.
    Image

    In Airflow 3.1.0+

    breeze start-airflow --python 3.12 --backend postgres --auth-manager FabAuthManager --db-reset --load-default-connections
    pip install apache-airflow-providers-fab==2.4.0rc1
    >restart all the Airflow services
    

    Initialization

    1. Create a new user
    2. Create a new role
    Image Image

    Test without permission, access is forbidden
    Image
    Image

    Test with permission, access is good task can be triggered, but pop up 409 Conflict even task can be successfully run.
    Image
    Image

    DAG is executed successfully if a user is assigned both edit permission to DAG and HITL_Detail resource
    Image

  18. eladkal commented on Aug 11, 2025

    @eladkal
    ContributorAuthor

    Thank you everyone. Providers are released.
    Providers Standard and Redis are excluded from this release

    I invite everyone to help improve providers for the next release, a list of open issues can be found here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:providerskind:metaHigh-level information important to the communitytesting statusStatus of testing releases

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions