carocad commented on issue #7435:
URL: 
https://github.com/apache/incubator-devlake/issues/7435#issuecomment-2122001087

   > @carocad Sure, you may find the "Custom Rate Limit" on the connection page.
   
   Unfortunately that didn't work either. See logs below
   
   ```log
   time="2024-05-21 07:48:30" level=info msg=" [pipeline service] [pipeline 
#145] [task #971] start executing task: 971"
   time="2024-05-21 07:48:30" level=info msg=" [pipeline service] [pipeline 
#145] [task #971] start plugin"
   time="2024-05-21 07:48:30" level=info msg=" [pipeline service] [pipeline 
#145] [task #971] [api async client] creating scheduler for api 
\"https://github.boschdevcloud.com/api/v3/\";, number of workers: 6, 4500 reqs / 
1h0m0s (interval: 800ms)"
   time="2024-05-21 07:48:31" level=error msg=" [pipeline service] [pipeline 
#145] [task #971] run task failed with panic\n\tcaused by: run task failed with 
panic 
(github.com/apache/incubator-devlake/helpers/pluginhelper/api.CreateAsyncGraphqlClient:71)\n\tWraps:
 (2) non-200 OK status code: 404 Not Found body: \"{\\\"message\\\":\\\"Not 
Found\\\",\\\"documentation_url\\\":\\\"https://docs.github.com/[email protected]/rest\\\"}\"\n\tWraps:
 (3) non-200 OK status code: 404 Not Found body: \"{\\\"message\\\":\\\"Not 
Found\\\",\\\"documentation_url\\\":\\\"https://docs.github.com/[email protected]/rest\\\"}\"\n\tError
 types: (1) *hintdetail.withDetail (2) *hintdetail.withDetail (3) 
*errors.errorString"
   ```
   
   I can only assume from this that DevLake would check the rate limit endpoint 
regardless of the custom rate limit and only after it receives a response it 
would then overwrite it. If you agree that this is a bug, I would happily try 
to create a PR to fix it :)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to