mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[PR #764] [MERGED] Remove false multihead warnings #1631
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#1631
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/764
Author: @orozery
Created: 5/22/2018
Status: ✅ Merged
Merged: 5/23/2018
Merged by: @ggtakec
Base:
master← Head:remove_false_multihead_warnings📝 Commits (1)
0bd875eremove false readdir_multi_head warnings📊 Changes
3 files changed (+10 additions, -3 deletions)
View changed files
📝
src/curl.cpp(+8 -2)📝
src/curl.h(+1 -0)📝
src/s3fs.cpp(+1 -1)📄 Description
Details
I encountered a few false warning messages (when setting dbglevel=warn):
`s3fs.cpp:append_objects_from_xml_ex(2575): contents_xp->nodesetval is empty.
this happens whenever the XML listing does not contain either or , which is very very common.
curl.cpp:MultiRead(3956): failed a request(404: ...andcurl.cpp:MultiPerform(3928): thread failed - rc(-2)These warnings appear whenever we get a 404 response on a HEAD request sent as part of
readdir_multi_head. This can happen if the object is not yet updated in the bucket listing, or if the object is a CommonPrefix.This PR removes those false warnings.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.