-
Notifications
You must be signed in to change notification settings - Fork 12
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
user_table not returning all results #68
Comments
Thanks for raising the bug @rmaalouf. Sorry to see that you are bumping into issues. Could you please share the plugin-level logs when you run the query |
Hey @rmaalouf ... Steampipe does sub-API calls for some columns to get their data. In this case, the problem is the Notice the https://github.com/turbot/steampipe-plugin-jira/blob/main/jira/table_jira_user.go#L69-L75 As a workaround, does this work? (Avoiding the group_names column):
For a more permanent solution, I think we need to add retry / backoff to the https://github.com/turbot/steampipe-plugin-jira/blob/main/jira/table_jira_user.go#L148-L164 |
Thanks for the assistance. On previous days I was able to replicate this on every query. This morning
|
@e-gineer that appears to do the trick. After hitting the 429 issue several times in a row I avoided selecting the |
Does this approach make sense:
|
Hello @rmaalouf, thanks a lot for extensively testing out the table and providing valuable insights on the error logs 👍 . Apologies for the delay, but I was finally able to get a hold of this issue. Initially, I was inclined towards reducing the I have created a PR - #72 which fixes the issue of API Rate limiting in the |
Hi @misraved, thank you for taking the time to look into this. I tested it by first reproducing the issue and then I rebuilt the plugin using this PR and ran the following 10 times in a row:
The query returned all users (~700) every time. |
Describe the bug
select * from jira_user
doesn't display all records and returns an inconsistent number of records every time it is run (even without clearing the cache)Additional information
select count(*) from jira.jira_user
does display the correct number of usersorder by
causes a 429 error every time. Example:select * from jira.jira_user order by display_name
Error: table 'jira_user' column 'group_names' requires hydrate data from getUserGroups, which failed with error 429 Too Many Requests: local_rate_limited: request failed. Please analyze the request body for more details. Status code: 429.
MaxConcurrency
seems to fix the issue. I reduced it from 50 to 5 and consistently get all records.Steampipe version (
steampipe -v
)Example: v0.16.4
Plugin version (
steampipe plugin list
)Example: v0.6.1
The text was updated successfully, but these errors were encountered: