[Bug][/api/plugins/gitlab/connections/{connectionId}/remote-scopes] Bug title - can't get the results with page 2

[usst830514]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Url: /api/plugins/gitlab/connections/{connectionId}/remote-scopes
Query: groupId: xxx
Method: GET
When I accessed the api above, I got the response body with nextPageToken(eyJwYWdlIjoyLCJwZXJfcGFnZSI6MTAwLCJzdGVwIjoicHJvamVjdCJ9).
The decoded content of nextPageToken is {"page":2,"per_page":100,"step":"project"}.
But when I continued accessing the api above with extra queryParam - pageToken: eyJwYWdlIjoyLCJwZXJfcGFnZSI6MTAwLCJzdGVwIjoicHJvamVjdCJ9, I got the same result with the first result

What do you expect to happen

I want to get the result with page 2, but also get the result with page 1

How to reproduce

Also see "What happened"

Anything else

nothing

Version

v1.0.1

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[dosubot]

Hello @usst830514! I'm here to help you with any software bugs, questions, or becoming a contributor. Let's work together to resolve the issue you're facing.

The issue you're experiencing, where the same page of results is returned despite using a different pageToken, could be due to how the pageToken is processed. If the pageToken is invalid or cannot be decoded properly, the function responsible for handling it defaults to returning the first page. This could explain why you're seeing the same results for both page 1 and page 2.

The function getPageDataFromPageTokenWithTag decodes the pageToken from Base64 and unmarshals it into a struct. If there's an error during this process, it defaults to the first page ^[1].

To troubleshoot this issue, ensure that the pageToken is correctly encoded and passed to the API. You might also want to check if there are any errors in the decoding or unmarshalling process that could be causing the default behavior.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[odorT]

I am also facing similar problem with the latest version : 1.0.2 beta5