[I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-22 Thread via GitHub
potiuk opened a new issue, #36384: URL: https://github.com/apache/airflow/issues/36384 ### 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

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-22 Thread via GitHub
Lee-W commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868192250 We've tested the following provider RCs with our example DAGs without encountering issues. apache-airflow-providers-microsoft-azure==8.5.0rc1 apache-airflow-providers-sftp==

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-22 Thread via GitHub
dirrao commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868204994 I have tested the following Kubernetes provider fixes. They are working as expected. I am eagerly waiting for the release that has a critical performance bug. - Kube

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-22 Thread via GitHub
utkarsharma2 commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868220019 Hey Jarek, Would it be possible to have an RC2 to include this commit for the W

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-23 Thread via GitHub
Joffreybvn commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868292197 Databricks and ODBC providers work fine. Tested #36205 and #36000 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to G

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-23 Thread via GitHub
potiuk commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868298706 > Would it be possible to have an RC2 to include this commits <[75d74b1](https://github.com/apache/airflow/commit/75d74b1f3a535fdc3624077bde3a34d1abcf641e)> and <[ff3b8da](https://

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-23 Thread via GitHub
potiuk commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868299418 As you can see - for example - in the past wave we had to withdraw google and databricks, so while we are releasing new changes in other providers, in this wave the google and datab

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-23 Thread via GitHub
guillaumeblaquiere commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868322265 Ok for #36133 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specifi

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-23 Thread via GitHub
shohamy7 commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868327063 I've tested #36241, all looks good -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-23 Thread via GitHub
spencertollefson commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868353719 I tested #36273. All good. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-23 Thread via GitHub
hussein-awala commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868361666 I tested all my changes, and all work as expected. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use th

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-23 Thread via GitHub
adam133 commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868383200 I won't get a chance to test the RC until late next week, but https://github.com/apache/airflow/pull/36248 worked when I ran the changes locally. -- This is an automated message

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-23 Thread via GitHub
utkarsharma2 commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868425100 > > I am not sure if there will be RC2 for Waeviate, but we can release a new > version right after this one gets released as well. > Thanks for your consideration,

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-23 Thread via GitHub
ankurbajaj9 commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868437758 This probably also needs changing the connection type in default connections https://github.com/apache/airflow/pull/36145 . but in itself it is ok -- This is an automated mes

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-24 Thread via GitHub
vchiapaikeo commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868524593 Has anyone noticed unusual behavior with the DagFileProcessor lately? I've observed some unusual behavior where a relatively simple dag is continually getting removed and added

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-24 Thread via GitHub
potiuk commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868552426 I think there are some main changes that influence that - I already saw one change while I was testing Python Client https://github.com/apache/airflow/issues/36377 - but it works fi

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-24 Thread via GitHub
potiuk commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868552590 BTW. Happy Holidays everyone ! - this one will continue after 26th of December 🎄 -- This is an automated message from the Apache Git Service. To respond to the message, please lo

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-24 Thread via GitHub
josh-fell commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1868584576 #36198 and #36262 verified in packaged files. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abo

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-26 Thread via GitHub
potiuk commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1869810531 Back after holidays :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific c

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-27 Thread via GitHub
nathadfield commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1870531266 All good on #36072 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-27 Thread via GitHub
potiuk commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1870705343 Thank you everyone. Providers are released I invite everyone to help improve providers for the next release, a list of open issues can be found [here](https://github.c

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2023-12-27 Thread via GitHub
potiuk closed issue #36384: Status of testing Providers that were prepared on December 23, 2023 URL: https://github.com/apache/airflow/issues/36384 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to th

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2024-01-02 Thread via GitHub
ginolegigot commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1874032435 Hello! Small question relative to this thread, do you know when this file https://raw.githubusercontent.com/apache/airflow/constraints-2.8.0/constraints-3.11.txt or any pyth

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2024-01-02 Thread via GitHub
potiuk commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1874050313 > https://raw.githubusercontent.com/apache/airflow/constraints-2.8.0/constraints-3.11.txt or any python versions will be updated to take into account the latest providers versions

Re: [I] Status of testing Providers that were prepared on December 23, 2023 [airflow]

2024-01-02 Thread via GitHub
ginolegigot commented on issue #36384: URL: https://github.com/apache/airflow/issues/36384#issuecomment-1874314997 Many thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific commen