-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Actions upload-artifact fails when using MinIO storage #28279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@cennis91 Can you provide your minio storage settings ? I find something wrong when |
@fuxiaohei my |
lunny
pushed a commit
that referenced
this issue
Dec 21, 2023
…28555) Related to #28279 When merging artifact chunks, it lists chunks from storage. When storage is minio, chunk's path contains `MINIO_BASE_PATH` that makes merging break. <del>So trim the `MINIO_BASE_PATH` when handle chunks.</del> Update the chunk file's basename to retain necessary information. It ensures that the directory in the chunk's path remains unaffected.
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Dec 21, 2023
…o-gitea#28555) Related to go-gitea#28279 When merging artifact chunks, it lists chunks from storage. When storage is minio, chunk's path contains `MINIO_BASE_PATH` that makes merging break. <del>So trim the `MINIO_BASE_PATH` when handle chunks.</del> Update the chunk file's basename to retain necessary information. It ensures that the directory in the chunk's path remains unaffected.
lunny
pushed a commit
that referenced
this issue
Dec 21, 2023
…28555) (#28568) Backport #28555 by @fuxiaohei Related to #28279 When merging artifact chunks, it lists chunks from storage. When storage is minio, chunk's path contains `MINIO_BASE_PATH` that makes merging break. <del>So trim the `MINIO_BASE_PATH` when handle chunks.</del> Update the chunk file's basename to retain necessary information. It ensures that the directory in the chunk's path remains unaffected. Co-authored-by: FuXiaoHei <[email protected]>
fuxiaohei
added a commit
to fuxiaohei/gitea
that referenced
this issue
Jan 17, 2024
…o-gitea#28555) Related to go-gitea#28279 When merging artifact chunks, it lists chunks from storage. When storage is minio, chunk's path contains `MINIO_BASE_PATH` that makes merging break. <del>So trim the `MINIO_BASE_PATH` when handle chunks.</del> Update the chunk file's basename to retain necessary information. It ensures that the directory in the chunk's path remains unaffected.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
The following action with
upload-artifact@v3
works fine when artifact storage is set tolocal
, but fails when set tominio
on v.1.21. The file is successfully uploaded to the MinIO storage, but fails onconfirmUploadChunk
.Might be related: #26400.
On success:
On failure:
Gitea Version
v1.21.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Docker: gitea/gitea:1.21.1
Database
None
The text was updated successfully, but these errors were encountered: