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

GitHub v3 API fields cause error in github_search_repository table #336

Closed
cbruno10 opened this issue Sep 18, 2023 · 1 comment · Fixed by #337
Closed

GitHub v3 API fields cause error in github_search_repository table #336

cbruno10 opened this issue Sep 18, 2023 · 1 comment · Fixed by #337
Assignees
Labels
bug Something isn't working

Comments

@cbruno10
Copy link
Contributor

Describe the bug
If I run a query trying to get any v3 API fields, I get this error:

> select topics from github_search_repository where query = 'repo:turbot/.github'

Error: rpc error: code = Internal desc = hydrate function hydrateRepositoryDataFromV3 failed with panic interface conversion: interface {} is struct { TextMatches []models.TextMatch; Node struct { models.Repository "graphql:\"... on Repository\"" } }, not models.Repository (SQLSTATE HV000)

+--------+
| topics |
+--------+
+--------+

Steampipe version (steampipe -v)
v0.20.9

Plugin version (steampipe plugin list)
v0.33.0

To reproduce
See above

Expected behavior
Results should be returned or those columns should not be available in the github_search_repository table if not compatible

Additional context
Add any other context about the problem here.

@cbruno10 cbruno10 added the bug Something isn't working label Sep 18, 2023
@graza-io
Copy link
Contributor

Ah, some oversight on my part, should be relatively easy to resolve.

@graza-io graza-io linked a pull request Sep 18, 2023 that will close this issue
cbruno10 pushed a commit that referenced this issue Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants