Skip to content
This repository has been archived by the owner on Jan 24, 2025. It is now read-only.

Randomly cannot unpack error from trigger_manual_sync_connection #17

Closed
lucienfregosibodyguard opened this issue Sep 2, 2022 · 1 comment · Fixed by #20
Closed

Randomly cannot unpack error from trigger_manual_sync_connection #17

lucienfregosibodyguard opened this issue Sep 2, 2022 · 1 comment · Fixed by #20
Assignees
Labels
bug Something isn't working

Comments

@lucienfregosibodyguard
Copy link

Hi,

I'm reporting a weird behavior I'm facing while trying to trigger prefect-airbyte task. Most of the time it works well but sometimes I got this error :

job_id, job_created_at = airbyte.trigger_manual_sync_connection(
TypeError: cannot unpack non-iterable NoneType object

It would mean that this function returns a None object but not specific errors which makes the debugging pretty tricky.

On the airbyte side, the prefect task has created 2 jobs: one failing and one successful.

Full log https://pastebin.com/4xZBJAYd

@desertaxle
Copy link
Member

Based on the code in trigger_manual_sync_connection, I suspect that the Airbyte server is returning a status code other than 200 or 404. We'll need to add some additional status code handling.

@desertaxle desertaxle self-assigned this Sep 7, 2022
@desertaxle desertaxle added the bug Something isn't working label Sep 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants