Drive item `discardCheckout` fails with `resourceCheckedOut` error when using application permissions, despite docs stating this should work
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 57/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- api
调研方向
Start by comparing the issue’s delegated and application permission requests with the driveitem-discardcheckout documentation linked in the report. Determine whether the observed error conflicts with the documented application permission behavior, and identify the relevant metadata or documentation entry in this repository; the issue does not name a file. Done means the behavior and documentation discrepancy is resolved or clearly explained.
由索引模型根据 Issue 内容生成。
描述
Summary
The documentation for discardCheckout states that application permissions can discard any checkout, regardless of who created it. In practice, discarding a checkout that was created via delegated auth fails with notAllowed / resourceCheckedOut when called with application permissions.
Steps to reproduce
- Checkout a file using delegated credentials:
POST https://graph.microsoft.com/v1.0/drives/{DriveID}/items/{ItemID}/checkout
- Discard the checkout using application credentials:
POST https://graph.microsoft.com/v1.0/drives/{DriveID}/items/{ItemID}/checkout
Expected behavior
Per the docs, application access should be able to discard any checkout.
Requests made with application access can discard any checkout.
Actual behavior
{
"error": {
"code": "notAllowed",
"message": "The resource has been checked-out by another user",
"innerError": {
"code": "resourceLocked",
"innerError": {
"code": "resourceCheckedOut"
},
"date": "2026-09-30T09:39:25",
"request-id": "588b93bb-eb52-4d98-879c-74c5cd475338",
"client-request-id": "588b93bb-eb52-4d98-879c-74c5cd475338"
}
}
}
Reference
- 主要语言
- XSLT
- 星标
- 171
- 派生
- 56
- 平均合并
- 1 天 11 小时
- 30 天内合并 PR
- 9
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoftgraph/msgraph-metadata 的其他 Issue
-
ToTriage
难度 2/5 1-3 小时 新手友好度 86/100
microsoftgraph/msgraph-metadata#1217 ·
维护者通常 2 天内回复
-
ToTriage
难度 2/5 1-3 小时 新手友好度 68/100
microsoftgraph/msgraph-metadata#1192 ·
维护者通常 2 天内回复
-
`microsoft.graph.managedDevice` is missing a filter restrictions annotation.可能已有人在做 @esidorenko-sl 于 86 天前认领。 未关闭ToTriage
难度 3/5 1-2 天 新手友好度 72/100
microsoftgraph/msgraph-metadata#1193 · 2 条评论 ·
维护者通常 2 天内回复
-
ToTriage
难度 4/5 3-5 天 新手友好度 45/100
microsoftgraph/msgraph-metadata#1169 · 1 个 reaction ·
维护者通常 2 天内回复
-
ToTriage
难度 3/5 1-2 天 新手友好度 55/100
microsoftgraph/msgraph-metadata#1166 ·
维护者通常 2 天内回复
查看 microsoftgraph/msgraph-metadata 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
fb55/htmlparser2#2579 ·
维护者通常 1 天内回复
-
bug good first issue needs-review
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
trycua/hermes-cua-spaces#17 ·
-
area/channels kind/bug priority/medium
难度 2/5 1-3 小时 新手友好度 78/100
nanocoai/nanoclaw#4501 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 69/100
AndyHazz/bookends.koplugin#134 ·