-
Notifications
You must be signed in to change notification settings - Fork 0
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
increase Google Sheets API reads per minute per user quota etc #87
Comments
@turbomam will push code to include a sleep step between cogs operations |
see #61 |
@ssarrafan this is frustrating, but shouldn't be a priority in terms of theJune 2022 DOE funding renewal. Please move to the July sprint. If you have contacts at Google, I can describe this more technically. |
@turbomam I checked with Ed who works for JGI and used to work at Google but he is not familiar with the API. Sorry! I will move this to July. |
@ssarrafan @sujaypatil96 @mcovalt this hasn't been a problem for me recently. I was thinking about decreasing or eliminating the sleep step @sujaypatil96 were you granted an increase to this quota? Did you apply it? How could one of see that to better understand what you did? |
@turbomam so we requested for an increase of the requests per min per user quota from the same Google account that was used to create the client secret JSON file. If we look through the inbox for that account, we should see an email response from Google Cloud support regarding our request. |
Sure Mark, I'll look into this issue. Will ping you if I have any questions
about the account.
…On Fri, Jul 29, 2022 at 10:52 AM Mark Miller ***@***.***> wrote:
I think that was a service account, so I don't know how to check the
email. Can you look into that please @sujay Patil ***@***.***> ?
On Fri, Jul 29, 2022, 1:47 PM Sujay Patil ***@***.***>
wrote:
> @turbomam <https://github.com/turbomam> so we requested for an increase
> of the requests per min per user quota from the same Google account that
> was used to create the client secret JSON file. If we look through the
> inbox for that account, we should see an email response from Google Cloud
> support regarding our request.
>
> —
> Reply to this email directly, view it on GitHub
> <#87 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AGAEX6OLP4Q3TRGMPVRTFLLVWQKK3ANCNFSM5ROVA75Q>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Based on Sujay's note I will close this issue but let me know if it should be re-opened. |
I think that was a service account, so I don't know how to check the email.
Can you look into that please @sujay Patil ***@***.***> ?
…On Fri, Jul 29, 2022, 1:47 PM Sujay Patil ***@***.***> wrote:
@turbomam <https://github.com/turbomam> so we requested for an increase
of the requests per min per user quota from the same Google account that
was used to create the client secret JSON file. If we look through the
inbox for that account, we should see an email response from Google Cloud
support regarding our request.
—
Reply to this email directly, view it on GitHub
<#87 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGAEX6OLP4Q3TRGMPVRTFLLVWQKK3ANCNFSM5ROVA75Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
May need to do this through LBL, or tie existing project to LBL first
The text was updated successfully, but these errors were encountered: