search

kriskbx / gitlab-time-tracker

🦊🕘 A command line interface for GitLab's time tracking feature.
GNU General Public License v2.0
458 stars 82 forks source link

Report fails if the number of issues is too high #82

Closed embeddedLance closed 4 years ago

embeddedLance commented 5 years ago

The report fails if the number of issues in a group or project is too high. I can look into the source code if you point me in the right direction, although I have no experience with NodeJS.

kriskbx commented 5 years ago

How many issues are we talking about?

To reproduce and hopefully fix a problem like this I will probably need a dump with your data. Please check it for sensitive information. You can email it to "m at kris dot cool", I will delete it afterwards and never send it to anyone.

stanvc commented 5 years ago

For a project with 500 issues the gtt tool is rate-limited during the processing if issues phase of the report command. Gitlab server responds with "Too many requests received. Please try again later."

embeddedLance commented 5 years ago

Right! Can we change this rate limit??

maks-io commented 5 years ago

I had the same problem with an app, that uses gitlab-time-tracker. Since the app itself was deprecated anyhow and i was not planning to further improve it/use it, the only important thing to me was to get one final report from it, containing all my gitlab issues. My workaround was to simply use the Chrome DevTools, go to the Network tab and set Throttling to Preset Slow 3G. This way the frequency of sent requests is way lower, which leads to bypassing the rate limit. I thought I'd share this because maybe some of you are in a similar situation and just need a quick workaround.

jdecaron commented 4 years ago

I submitted a pull request that can fix this issue: https://github.com/kriskbx/gitlab-time-tracker/pull/106