Closed mzampetakis closed 1 year ago
Looks like pagination done wrong. Do you know how you can paginate in bitbucket?
Indeed. It seems that the specific request is missing the pagination parameters. I have paginated other requests towards bitbucket, so I will find that out and open a PR when possible.
Component
server
Describe the bug
As soon as I activate a repo from bitbucket forge through UI, It sends multiple request to fetch the repo's branches for different pages. So we have consecutive requests with page incrementing by 1 after each call:
All of then result in http 200 but with the exact same result:
It seems that UI expects to receive an empty response (
[]
) in order to stop invoking for the next page.System Info
9:54PM DBG server/router/middleware/logger.go:59 > ip=XXX latency=287.846458 method=GET path=/api/repos/5/branches status=200 user-agent="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36"