Skip to content
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

[source-zendesk-chat] Connector not working in PyAirbyte #52063

Closed
1 task done
yohannj opened this issue Jan 21, 2025 · 0 comments · Fixed by #52065
Closed
1 task done

[source-zendesk-chat] Connector not working in PyAirbyte #52063

yohannj opened this issue Jan 21, 2025 · 0 comments · Fixed by #52065

Comments

@yohannj
Copy link
Contributor

yohannj commented Jan 21, 2025

Connector Name

source-zendesk-chat

Connector Version

1.0.1

What step the error happened?

During the sync

Relevant information

pyproject.toml specifies the cdk version to be airbyte-cdk = "^0".

However there are breaking changes between v0.72.2 (version locked in poetry.lock) and v0.90.0 (latest v0 of the cdk).
In particular the file cursor.py has been moved in this commit to airbyte_cdk/sources/streams/checkpoint/cursor.py.

While the poetry.lock committed still specifies cdk v0.72.2, the pyproject.toml specifies airbyte-cdk = "^0" and this is what is published in pypi.
You can check that by downloading the wheel, unzip and check the METADATA file, it says:

Requires-Dist: airbyte-cdk (>=0,<1)

When working with PyAirbyte we build a venv based on the wheel, which installs v0.90.0 of the cdk and so the source fails because of the breaking change.

This is easily testable locally in this repository:

rm poetry.lock # remove the cached result of poetry dependencies.
poetry install # rebuild poetry.lock
poetry run source-zendesk-chat read --config secrets/config.json --catalog integration_tests/configured_catalog.json

the last command will quickly return:

{"type": "LOG", "log": {"level": "FATAL", "message": "No module named 'airbyte_cdk.sources.declarative.incremental.cursor ...

Relevant log output

Contribute

  • Yes, I want to contribute
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants