-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status of testing Providers that were prepared on April 13, 2024 #38997
Comments
For the databricks provider, for PRs #38741 and #38918 to work well, we would need PR #38962 to be included as well 😐 cc: @SubhamSinghal @Lee-W |
Why? It looks like a feature not a fix to regression from rc1 |
It's that the work done in PR #38741 contained a couple of issues of which one was fixed in #38918 , however the work that has been done in #38741 will not work as expected due to another issue which is getting fixed in #38962 . Essentially, the permissions endpoint call introduced in #38741 expects a job ID which was missing in it, and PR #38962 fixes that. So it will be like if we do not include #38962 , we're releasing #38741 which we know has an issue/bug. |
Thanks for the explnation. I will exclude databricks and prepare RC3. |
Testes #38702, working as expected. |
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. |
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 databricks: 6.3.0rc2
Linked issues:
DatabricksSqlOperator
's fields' names to comply with templated fields validation (#38052): @shahar1Linked issues:
Provider yandex: 3.10.0rc2
assert
outside of the tests (#37718): @TaragolisAll users involved in the PRs:
@Lee-W @SubhamSinghal @uzhastik @shahar1 @Taragolis
Committer
The text was updated successfully, but these errors were encountered: