You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you know where the max connection reached error came from. Never saw that before. Do you have anything in the console? Incase of http2 the browser should share the connection shouldn't it.
Yes, that's from Traefik. It's HTTP 429 Too Many Requests with response body max connections reached: 10. Seems, in the test cluster I have a lower value of 10. That is why I wrote Optionally, see ... in 5.
Despite my configuration, the point is still valid, IMO. There is a request per repo. How many repos per pagination-page? 50? So there will be at least 50+1 requests, if I have > 50 repos. That is not good to me. If my proposals 1 and 2 do not suit you, what is about reducing pagination-page size to... let's say 10? (Added this as proposal 4).
Component
server, web-ui
Describe the bug
Testing new repo list, sometimes I get errors
: max connections reached: 10
.Having 7 repos:
pipeline
endpointpipeline
endpointSteps to reproduce
: max connections reached: 10
errorsExpected behavior
pipelines/last?repo_ids=[1,2,3,4,5]
System Info
Additional context
#4386 (comment)
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: