-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Move databricks provider to new structure #46207
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
Move databricks provider to new structure #46207
Conversation
ba47389 to
47e80ce
Compare
|
conflicts again (but I hope this time things will be green). |
47e80ce to
ddd7062
Compare
|
Thanks! Let me fix this first, I guess the patch for |
ddd7062 to
a251efc
Compare
Cool :) |
a251efc to
c938dcb
Compare
o-nikolas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you just barely missed a fix in main when you rebased an hour ago 😢
c938dcb to
6906290
Compare
|
Hmmm... I rebased after #46291 merged, and it indeed fixed the issues that caused the previous failed tests in |
732343e to
8bc5b21
Compare
|
I'll continue fixing the flaky caplog-related unit tests once the lazy consensus is reached. |
5d71eca to
9f3d6b5
Compare
9f3d6b5 to
3e78d05
Compare
|
Rebased - and the consensus is reached so ..... you can fix it :) |
|
Some errors to look at :( . Happy to help if needed. |
3e78d05 to
ccc1f6e
Compare
|
Yeah, let me circle back to this. Sorry for being busy the past two days, but thankfully, I just finished it and can now focus on this issue. |
No worries at all :), It's open -source. We do stuff when we can ! |
ccc1f6e to
6efc3e7
Compare
|
The wasb tests should be "fine" after this is merged #46539 -> then you can rebase and 🤞 we should get this one green. |
|
OK. you can rebase it now :) |
6efc3e7 to
4a1dad1
Compare
|
Thanks, @potiuk! It turns out that the issue is caused from caplog, just as my initially assumed. However, I still can't figure out why it is related to building connection, given that the error shows |
Beats me... No idea other than there are side effects from other tests. I know removing it and replacing with direct mocking helped in pretty much all cases where it happened (many) - I am not going to lose any more time on diving deeper :) - we all lost already far too much time on looking at caplog issues IMHO. |
aba0a22 to
93f2853
Compare
|
Pushed a fixup with conflict resolution :) |
|
wooohooo |
* refactor(providers/databricks): move databricks provider to new structure * remove unused caplog --------- Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
* refactor(providers/databricks): move databricks provider to new structure * remove unused caplog --------- Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
related: #46045
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.