narrowizard opened a new issue, #5663:
URL: https://github.com/apache/incubator-devlake/issues/5663

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   Currently, when the connection API request rate limit is not set in DevLake, 
the platform uses a default value. However, the API response for the 
"connection" endpoint returns a rate_limit value of 0, which leads to a 
discrepancy between the displayed rate limit and the actual rate limit being 
executed. This inconsistency can confuse users and provide inaccurate 
information about their rate limits.
   
   ### What do you expect to happen
   
   When the API returns a "connection" object, it is expected that the 
rate_limit value accurately represents the current rate limit being enforced 
for that connection. This ensures transparency and allows users to have an 
accurate understanding of their rate limits.
   
   ### How to reproduce
   
   1. Set up a DevLake instance and configure it with third-party platforms(eg: 
jira) for data collection.
   2. Make sure the connection API rate limit is not explicitly set for 
connection.
   3. Send a request to the API to retrieve the connection information.
   4. Examine the response and observe that the rate_limit value returned for 
the connection is 0, regardless of the actual rate limit being enforced.
   
   ### Anything else
   
   Please let me know if there's anything else you'd like to include or if you 
need further assistance.
   
   ### Version
   
   release-v0.17
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: dev-unsubscr...@devlake.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to