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 Github: bad bool value MERGEABLE #15919

Closed
ball-hayden opened this issue Aug 24, 2022 · 2 comments
Closed

Source Github: bad bool value MERGEABLE #15919

ball-hayden opened this issue Aug 24, 2022 · 2 comments

Comments

@ball-hayden
Copy link

Environment

  • Airbyte version: 0.40.0-alpha
  • OS Version / Instance: Official Docker Image
  • Deployment: Kubernetes
  • Source Connector and version: GitHub 0.2.46
  • Destination Connector and version: BigQuery
  • Step where error happened: Normalization

Current Behavior

GitHub connector fails to sync pull_request_stats due to normalization error

Expected Behavior

GitHub connector should sync without errors

Logs

logs-316.txt

Steps to Reproduce

  1. Set up connection between GitHub and BigQuery
  2. Enable pull_request_stats Incremental | Deduped + History
  3. ??? Probably some state required on GitHub as well, but unknown what.

Are you willing to submit a PR?

With guidance, if I can find time, sure.

@ball-hayden ball-hayden added needs-triage type/bug Something isn't working labels Aug 24, 2022
@marcosmarxm marcosmarxm changed the title GitHub Connector: Bad bool value: MERGEABLE Source Github: bad bool value MERGEABLE Nov 30, 2022
@grubberr
Copy link
Contributor

grubberr commented Apr 30, 2023

@lazebnyi

As for me, it's already not actual, I think we can just close it
this could happen a year ago when stream pull_request_stats switched from REST API -> GraphQL
and this field mergeable change type from bool -> string

62626ee#diff-37ed591961d08ded524ef9d930eb4f84d8b6997c8364206f67d573df473b4bc3L20

@grubberr grubberr self-assigned this May 3, 2023
@lazebnyi
Copy link
Collaborator

lazebnyi commented May 4, 2023

Fixed in - #13763

@lazebnyi lazebnyi closed this as completed May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants