Github source fails to sync when you check teams and issue_events in the schema

[Moofasax]

Expected Behavior

Expect a successful sync from source: Github and destination: Postgres

Current Behavior

If you leave "teams" and "issue_events" checked in the schema when setting up this integration, the sync will fail.

Github sync will work if you remove "teams" and "issue_events" from the schema.

Logs

If applicable, please upload the logs from the failing operation. For sync jobs, you can download the full logs from the UI by going to the sync attempt page and clicking the download logs button at the top right of the logs display window.

Steps to Reproduce

1. Create source github
2. Create destination Postgres
3. Leave "teams" and "issue_events" checked in the schema

Severity of the bug for you

Critical

Airbyte Version

0.17.0-alpha

Connector Version (if applicable)

GitHub | airbyte/source-github-singer | 0.2.0

[sherifnada]

@Moofasax thanks for reporting the issue. Could you help us with debugging by providing the log from the failing sync job? you can find it by going to the sources page, clicking on the github source, then on postgres, then find the failing sync job and click the "download logs" button on the top right of the logs console.

We already have #2365 for the Teams stream in the case that the repo being replicated is not an organization. But the issue_events one is new, so having logs would help us debug.

[Moofasax]

logs-51-0.txt

Attached are the logs, the sync never stops failing as well, so hope i let it run long enough for you to get the logs (see this issue as well: #2452

[sherifnada]

@Moofasax the issue with issue_labels has been fixed and should be released on version 0.17.2-alpha very soon (tomorrow or Wednesday). The fix for the issue with teams is currently WIP in #2472 and will likely be released by EOW .

[Moofasax]

Oh nice man, by issue_labels do you mean issue_events? Just checking! And thanks man!

[sherifnada]

@Moofasax yup I meant issue_events, mb

[sherifnada]

Also, version 0.17.2-alpha containing the bugfix has been released. To upgrade Airbyte:

1. pull the latest version of the github repository using git pull
2. From the repo root, run docker-compose down to turn off the running instance of Airbyte
3. Run docker-compose up to turn it on. You should see that some the newest Airbyte images are being downloaded

Once the server is running you should be good to go.

[vitaliizazmic]

@Moofasax

We just merged this bugfix and into master a released a new version of the connector.

Upgrade your connector to version 0.2.1 and get started. To upgrade your connector version, go to the admin panel in the left hand side of the UI, find this connector in the list, and input the latest connector version.

Please let us know if you have any further questions.

Enjoy!

[Moofasax]

Oh nice, will check it out!