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: created_at field parsing error in Bans stream #8819

Closed
brebuanirello-equinix opened this issue Dec 15, 2021 · 1 comment · Fixed by #7313
Closed

Comments

@brebuanirello-equinix
Copy link
Contributor

brebuanirello-equinix commented Dec 15, 2021

Environment

Is this your first time deploying Airbyte: No
OS Version / Instance: Ubuntu 20.04
Machine type e2-standard-8 ( 8 CPU )
Memory / Disk: 32Gb / 100 GB ssd
Deployment: Docker
Airbyte Version: 0.33.9-alpha
Source name/version: airbyte/source-zendesk-chat:0.1.5
Destination name/version: airbyte/destination-bigquery:0.5.0
Severity: medium
Step where error happened: Sync job

Current Behavior

Pendulum parsing the date column created_at return TypeError: expected string or bytes-like object

Expected Behavior

Parse the date correctly

logs

logs-18-2.txt

Steps to Reproduce

  1. Sync every table without the big ones agent_timeline and triggers
  2. Try to sync start date = "2021-12-14T00:00:00Z

Are you willing to submit a PR?

Yes

@brebuanirello-equinix brebuanirello-equinix added needs-triage type/bug Something isn't working labels Dec 15, 2021
@alafanechere alafanechere changed the title Source zendesk chat sync with parse error 🐛 Source Zendesk chat: sync with parse error Dec 16, 2021
@alafanechere alafanechere added area/connectors Connector related issues and removed needs-triage labels Dec 16, 2021
@alafanechere
Copy link
Contributor

It looks like the created_at fields returned by the API on the Bans stream cannot be parsed by pendulum. This bug might occur because the created_at field is optional according to the API doc..

@alafanechere alafanechere changed the title 🐛 Source Zendesk chat: sync with parse error 🐛 Source Zendesk chat: created_at field parsing error in Bans stream Dec 16, 2021
@grubberr grubberr self-assigned this Dec 22, 2021
@grubberr grubberr linked a pull request Dec 22, 2021 that will close this issue
16 tasks
@bazarnov bazarnov linked a pull request Dec 22, 2021 that will close this issue
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

6 participants