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

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

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

2023-12-07 Thread via GitHub
melugoyal commented on issue #36117: URL: https://github.com/apache/airflow/issues/36117#issuecomment-1846304738 #35694 working as expected -- 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 spe

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

2023-12-08 Thread via GitHub
atrbgithub commented on issue #36117: URL: https://github.com/apache/airflow/issues/36117#issuecomment-1847548472 An issue has been raised with https://github.com/apache/airflow/pull/34919 Unfortunately it looks like it has broken `GCSObjectsWithPrefixExistenceSensor`. -- This is

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

2023-12-09 Thread via GitHub
eladkal commented on issue #36117: URL: https://github.com/apache/airflow/issues/36117#issuecomment-1848360928 Docker provider will be excluded from rc1 -- 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

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

2023-12-09 Thread via GitHub
hussein-awala commented on issue #36117: URL: https://github.com/apache/airflow/issues/36117#issuecomment-1848434947 I tested my change on the Kubernetes executor, and most of the changes in the Amazon provider, all work as expected. -- This is an automated message from the Apache Git Ser

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

2023-12-09 Thread via GitHub
pankajastro commented on issue #36117: URL: https://github.com/apache/airflow/issues/36117#issuecomment-1848445737 As @atrbgithub has mentioned above https://github.com/apache/airflow/pull/34919 is breaking an existing DAG. so we might need to exclude Google provider -- This is an automa

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

2023-12-09 Thread via GitHub
eladkal commented on issue #36117: URL: https://github.com/apache/airflow/issues/36117#issuecomment-1848482088 > so we might need to exclude Google provider Yes. Google provider will also have RC2 -- This is an automated message from the Apache Git Service. To respond to the message

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

2023-12-10 Thread via GitHub
potiuk commented on issue #36117: URL: https://github.com/apache/airflow/issues/36117#issuecomment-1848947322 Tested mssql - all looks good. One more thing I noticed - the removed `daskexecutor` has not been prepared. We have this in the release process, so it's easy to miss:

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

2023-12-10 Thread via GitHub
potiuk commented on issue #36117: URL: https://github.com/apache/airflow/issues/36117#issuecomment-1848959588 One small update - as @pankajastro noticed in https://github.com/apache/airflow/pull/32319#discussion_r1421437350 - there is a case where we are not handling properly the fact that

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

2023-12-10 Thread via GitHub
potiuk commented on issue #36117: URL: https://github.com/apache/airflow/issues/36117#issuecomment-1849123662 Fix to the process to automatically generate removed providers here: https://github.com/apache/airflow/pull/36160 -- This is an automated message from the Apache Git Service. To r

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

2023-12-10 Thread via GitHub
Joffreybvn commented on issue #36117: URL: https://github.com/apache/airflow/issues/36117#issuecomment-1849141625 Fix for https://github.com/apache/airflow/pull/32319#discussion_r1421437350 is here -> #36161 -- This is an automated message from the Apache Git Service. To respond to the me

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

2023-12-11 Thread via GitHub
nathadfield commented on issue #36117: URL: https://github.com/apache/airflow/issues/36117#issuecomment-1849939531 #36072 has been tested and working as expected. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

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

2023-12-11 Thread via GitHub
eladkal commented on issue #36117: URL: https://github.com/apache/airflow/issues/36117#issuecomment-1851385174 Providers: Google, ODBC, Databricks, Docker are excluded from RC1. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

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

2023-12-11 Thread via GitHub
eladkal commented on issue #36117: URL: https://github.com/apache/airflow/issues/36117#issuecomment-1851438066 Thank you everyone. Providers are released (excluding Google, ODBC, Databricks, Docker which we will have RC2 soon) I invite everyone to help improve providers for the next re

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

2023-12-11 Thread via GitHub
eladkal closed issue #36117: Status of testing Providers that were prepared on December 08, 2023 URL: https://github.com/apache/airflow/issues/36117 -- 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 t