With a newer Gitlab version, we have started seeing error messages like this randomly, but quite often:
Exception during item execution (RepositoryWorkItem@XXX): Initial paginated response no longer paginated:
This seems to be a change of behavior in Gitlab for paginated results. We need to investigate if this affects the data being returned or not, and if so we can ignore it. The error implies that while following "next" links in the result header to request the next page, suddenly we receive a page with no links in the header.
It could also be that this is a symptom of the server giving us bogus results. In that case we will need some kind of better handling to not get overwhelmed by error log messages from Skara.
Exception during item execution (RepositoryWorkItem@XXX): Initial paginated response no longer paginated:
This seems to be a change of behavior in Gitlab for paginated results. We need to investigate if this affects the data being returned or not, and if so we can ignore it. The error implies that while following "next" links in the result header to request the next page, suddenly we receive a page with no links in the header.
It could also be that this is a symptom of the server giving us bogus results. In that case we will need some kind of better handling to not get overwhelmed by error log messages from Skara.