fix(pikpak): send initial page token - #7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
page_tokenquery parameter, including an explicit empty value on the first pagepage_token=from an omitted parameterContext
Production connection tests still returned
PIKPAK_UPSTREAM_FAILEDafter the CAPTCHA retry fix, for both a configured folder and the drive root. Comparing the list request with rclone's current PikPak backend showed that rclone always sendspage_token, while ilist omitted it for the initial page.Validation
npm run checkFollow-up to #6, #5, and #4.