Skip to content

Status of testing Providers that were prepared on May 01, 2024 #39346

Closed

Description

@eladkal

Body

I have a kind request for all the contributors to the latest provider packages 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 comment, whether the issue is addressed.

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

Provider airbyte: 3.8.0rc1

Provider amazon: 8.21.0rc1

Provider apache.beam: 5.7.0rc1

Provider apache.livy: 3.8.0rc1

Provider apache.spark: 4.8.0rc2

Provider cncf.kubernetes: 8.2.0rc1

Provider common.sql: 1.13.0rc1

Provider databricks: 6.4.0rc1

Provider datadog: 3.6.0rc1

Provider dbt.cloud: 3.8.0rc1

Provider fab: 1.1.0rc1

Provider google: 10.18.0rc1

Provider hashicorp: 3.7.0rc2

Provider http: 4.11.0rc1

Provider jdbc: 4.3.0rc1

Provider microsoft.azure: 10.1.0rc1

Provider odbc: 4.6.0rc1

Provider openai: 1.2.0rc1

Provider openlineage: 1.7.1rc1

Provider pagerduty: 3.7.0rc2

Provider pinecone: 2.0.0rc1

Provider postgres: 5.11.0rc1

Provider qdrant: 1.1.0rc1

Provider salesforce: 5.7.0rc2

Provider slack: 8.7.0rc1

Provider snowflake: 5.5.0rc1

Provider teradata: 2.1.0rc1

All users involved in the PRs:
@mobuchowski @josix @mateuslatrova @kacpermuda @dabla @anush008 @jedcunningham @boraberke @pankajastro @Taragolis @gopidesupavan @hussein-awala @wlinamchurch @nathadfield @pankajkoti @potiuk @Kylea650

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 May 1, 2024
  2. nathadfield commented on May 1, 2024

    @nathadfield
    Contributor

    @eladkal #39248 and #38736 tested and working correctly.

  3. dabla commented on May 1, 2024

    @dabla
    Contributor

    I know there is still an issue with the MSGraphSensor in that sense that it’s not working correctly in an async way and sometimes an event loop closed error can occur. This PR will fix it so dunno how to proceed for the msgraph part with this RC?

  4. wlinamchurch commented on May 1, 2024

    @wlinamchurch
    Contributor

    @eladkal #38911 tested and working correctly.

  5. gopidesupavan commented on May 1, 2024

    @gopidesupavan
    Member

    @eladkal #39300 tested and working correctly.

  6. anush008 commented on May 1, 2024

    @anush008

    Provider qdrant: 1.1.0rc1
    #39273

    Tested. Works as expected.

  7. dondaum commented on May 1, 2024

    @dondaum
    Contributor

    #38961 is good. ✅

  8. dabla commented on May 2, 2024

    @dabla
    Contributor

    Following 3 PR suffer from the same issues with the MSGraphSenor which has been fixed in #39304:
    #38111
    #39237
    #39207

  9. eladkal commented on May 2, 2024

    @eladkal
    ContributorAuthor

    I know there is still an issue with the MSGraphSensor in that sense that it’s not working correctly in an async way and sometimes an event loop closed error can occur. This PR will fix it so dunno how to proceed for the msgraph part with this RC?

    It's not merged. Only merged PR before release are included.

  10. dabla commented on May 2, 2024

    @dabla
    Contributor

    I know there is still an issue with the MSGraphSensor in that sense that it’s not working correctly in an async way and sometimes an event loop closed error can occur. This PR will fix it so dunno how to proceed for the msgraph part with this RC?

    It's not merged. Only merged PR before release are included.

    I know there is still an issue with the MSGraphSensor in that sense that it’s not working correctly in an async way and sometimes an event loop closed error can occur. This PR will fix it so dunno how to proceed for the msgraph part with this RC?

    It's not merged. Only merged PR before release are included.

    I know Elad I just wanted to make you guys aware of it.

  11. pankajastro commented on May 2, 2024

    @pankajastro
    Member

    Tested #39279 and #38536 looks good

  12. eladkal commented on May 2, 2024

    @eladkal
    ContributorAuthor

    I know Elad I just wanted to make you guys aware of it.

    If there is regression we can make RC2 then it will be included. What do you recommend ?

  13. paolo-moriello commented on May 2, 2024

    @paolo-moriello
    Contributor

    #39325 tested 👍

  14. Kylea650 commented on May 2, 2024

    @Kylea650
    Contributor

    Anybody with an Azure account able to test #39156? I can provide an example DAG I just don’t have access to my work Azure account right now and don’t want to block the release.

  15. rawwar commented on May 2, 2024

    @rawwar
    Contributor

    Pineconepinecone: 2.0.0rc1

    PR: #37307 is has bugs.

    Fix is being implemented in #39365

  16. tomrutter commented on May 2, 2024

    @tomrutter
    Contributor

    Happy with #38747

  17. dabla commented on May 2, 2024

    @dabla
    Contributor

    I know Elad I just wanted to make you guys aware of it.

    If there is regression we can make RC2 then it will be included. What do you recommend ?

    Yes an RC2 would be great.

  18. pankajkoti commented on May 2, 2024

    @pankajkoti
    Member

    Verified #39178 , works all fine

  19. boraberke commented on May 2, 2024

    @boraberke
    Contributor

    #39266 looks good.

  20. zstrathe commented on May 2, 2024

    @zstrathe
    Contributor

    #38716 tested and verified #38713 is resolved

  21. nyoungstudios commented on May 3, 2024

    @nyoungstudios
    Contributor

    Tested #39139 and looks good!

  22. Taragolis commented on May 4, 2024

    @Taragolis
    Contributor

    Tests my changes (most of them just cosmetic), look good

  23. Lee-W commented on May 6, 2024

    @Lee-W
    Member

    for #38912, we might introduce a potential bug as commented in #36090 (comment)

  24. pankajkoti commented on May 6, 2024

    @pankajkoti
    Member

    for #38912, we might introduce a potential bug as commented in #36090 (comment)

    Similar risk for #39130 and #39230

  25. eladkal commented on May 6, 2024

    @eladkal
    ContributorAuthor

    Thank you everyone. Providers are released.
    Google, microsoft.azure and pinecone are excluded from this wave.

    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

    kind: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