cloudflare / cloudflare/developer-platform

🐛 BUG: R2 Multipart upload doesn't return custom metadata

未关闭
#3 3 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
product:r2
主要语言
没有语言数据
星标
1
派生
0
PR 合并指标
30 天内没有已合并 PR

描述

### Which Cloudflare product(s) does this pertain to?

R2

### What version(s) of the tool(s) are you using?

3.57.2 Wrangler

### What version of Node are you using?

20.12.2

### What operating system and version are you using?

Windows 11

### Describe the Bug

### Observed behavior
Custom metadata is missing when completing a R2 multipart upload. However when fetching the head of the r2Object the metadata is there. Strangely enough when running locally with `wrangler pages dev` the example works as expected. Only once you deploy your site the custom metadata is missing.

```js
const upload = await env.BUCKET.createMultipartUpload(key, {
customMetadata: {
hallo: 'zwallo',
},
});

const uploadPart = await upload.uploadPart(1, request.body);

const r2Object = await upload.complete([uploadPart]);
console.log(r2Object.customMetadata) // logs an empty object: {}

const r2Head = await env.BUCKET.head(key);
console.log(r2Head.customMetadata) // logs the correct metadata: {hallo: "zwallo"}
```

### Expected behavior
`multipartUpload.complete()` should return an `R2Object` with the field `customMetadata` populated

### Steps to reproduce
1. clone repository
2. run `cd multipart-upload-missing-metadata && npm i`
3. run `npm run dev` for a working example
4. run `npm run deploy` for the example to fail on the deployed site

### Please provide a link to a minimal reproduction

https://github.com/YannicEl/cloudflare_worker_bugs/tree/main/multipart-upload-missing-metadata

### Please provide any relevant error logs

_No response_

贡献指南

打开贡献指南

调研方向

从 multipart-upload-missing-metadata 复现开始,并使用 npm i 安装其依赖项。运行 npm run dev 和 npm run deploy,然后将 multipartUpload.complete() 返回的 customMetadata 与 head() 中的 metadata 进行比较;部署的示例返回已填充的 metadata 即表示完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
javascript, node.js
领域
api, backend, cloud
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
描述清楚
新手友好度
32/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。