-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
refactor(source-mixpanel): migrate to CDK v3 #41969
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
regression tests - https://github.com/airbytehq/airbyte/actions/runs/9947855021 |
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.
Added some initial comments, will continue reviewing some of the custom components and error handlers, but wanted to first discuss the large amount of ignore
mypy statements.
I think that at best, there are some places where we can fix the actual mypy issues instead of ignoring them (see one of my comments below), and at worst, we need to include more comments on the annotations to explain why we have to ignore the type check
airbyte-integrations/connectors/source-mixpanel/source_mixpanel/utils.py
Outdated
Show resolved
Hide resolved
airbyte-integrations/connectors/source-mixpanel/source_mixpanel/streams/base.py
Outdated
Show resolved
Hide resolved
airbyte-integrations/connectors/source-mixpanel/source_mixpanel/streams/base.py
Outdated
Show resolved
Hide resolved
@brianjlai We had a discussion with @girarda and decided that, since mypy checks are not required for connectors, we can skip fixing those issues and focus only on changes related to error handling. |
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 have some comments about how we're structuring the custom components, but I think this is very close
airbyte-integrations/connectors/source-mixpanel/source_mixpanel/components.py
Outdated
Show resolved
Hide resolved
airbyte-integrations/connectors/source-mixpanel/source_mixpanel/streams/base.py
Outdated
Show resolved
Hide resolved
...tegrations/connectors/source-mixpanel/source_mixpanel/errors_handlers/base_errors_handler.py
Show resolved
Hide resolved
airbyte-integrations/connectors/source-mixpanel/source_mixpanel/streams/base.py
Show resolved
Hide resolved
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.
looks good to me thanks for making the changes asked. But since regression tests were last run 2 weeks ago, can you kick off one more regression test run before merging?
@lazebnyi Hey where does this PR stand? Looks like it should be ready to merge after resolving conflicts? |
/approve-regression-tests
|
regression tests - https://github.com/airbytehq/airbyte/actions/runs/10390977148 |
/approve-regression-tests
|
What
migrate to CDK v3;
Fix https://github.com/airbytehq/airbyte-internal-issues/issues/8387
How
migrate:
def backoff_time
->def get_backoff_strategy
def should_retry
->def get_error_handler
Can this PR be safely reverted and rolled back?