[BUG] 无法添加PikPak分享
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend
Research direction
The error comes from the PikPak share storage driver's credential check, which rejects a configuration with no username or password and no refresh_token. Find where the Worker validates PikPak share settings and compare it with the Go version's PikPak share driver, which accepts the same input. Done means adding a PikPak share with only the share ID succeeds on a local Worker setup, and the change is confirmed by that same add flow.
Written by the indexing model from the issue text.
Description
请确认以下事项
- 我确认描述清晰有礼貌，已提供必要诊断信息，在最新版本上可以复现。
- 我确认已经查过相关文档和已有问题和讨论，本次反馈并非是重复提问。
- 我确认这是Worker项目问题，并非网络和操作导致，也不是Go版的问题。
- 我确认已阅读开源许可/免责条款/使用政策，理解使用的风险自行承担。
版本（必填）
No response
平台（必填）
Cloudflare Workers
DB_FORMAT（必填）
sql（关系表）
DB_DRIVER（必填）
d1
存储驱动（必填）
PikPak分享
问题描述（必填）
无法成功添加PikPak分享，填入分享id后显示PikPak username or password is required when refresh_token is not provided
但是Go版不存在此问题
报错信息（必填）
PikPak username or password is required when refresh_token is not provided
相关配置（必填）
PikPak username or password is required when refresh_token is not provided
复现链接（可选）
No response
- Dominant language
- TypeScript
- Stars
- 573
- Forks
- 926
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenListTeam/OpenList-Worker
-
115open 添加后无法使用Openbug
Difficulty 4/5 3-5 days Newbie friendliness 22/100
OpenListTeam/OpenList-Worker#128 ·
Maintainers usually reply within 3 days
-
[BUG] 139云盘139 Cloud token is near expiry; configure user_domain_id to use the PC refreshToken APIOpenbug
Difficulty 3/5 1-2 days Newbie friendliness 47/100
OpenListTeam/OpenList-Worker#122 · 2 comments ·
Maintainers usually reply within 3 days
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 22/100
OpenListTeam/OpenList-Worker#115 · 3 comments ·
Maintainers usually reply within 3 days
-
[BUG] 移动云盘访问子目录出现根目录套娃情况Possibly taken @PIKACHUIM claimed this 5 days ago. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 56/100
OpenListTeam/OpenList-Worker#112 · 8 comments ·
Maintainers usually reply within 3 days
All issues in OpenListTeam/OpenList-Worker
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug category:ai category:devices effort:s
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LanternOps/breeze#8943 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
area:reliability difficulty:easy help wanted points:100 Stellar Wave
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Divinity-Labs/Lens#341 · 1 comment ·
Maintainers usually reply within 1 day