[PR #2741] [MERGED] Improved handling of XML parser errors #2759

New issue

Closed

opened 2026-03-04 02:07:09 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 02:07:09 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/2741
Author: @ggtakec
Created: 10/13/2025
Status: ✅ Merged
Merged: 10/13/2025
Merged by: @gaul

Base: master ← Head: update/xmlerror

📝 Commits (1)

b533091 Improved handling of XML parser errors

📊 Changes

3 files changed (+56 additions, -1 deletions)

View changed files

📝 src/s3fs.cpp (+8 -1)
📝 src/s3fs_xml.cpp (+8 -0)
📝 src/s3fs_xml.h (+40 -0)

📄 Description

Relevant Issue (if applicable)

#2740 #2739

Details

XML parsing errors that occur when calling xmlReadMemory are output to stderr, so I've changed it so that these are handled by s3fs.
This allows the error content to be treated as an s3fs error.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/s3fs-fuse/s3fs-fuse/pull/2741 **Author:** [@ggtakec](https://github.com/ggtakec) **Created:** 10/13/2025 **Status:** ✅ Merged **Merged:** 10/13/2025 **Merged by:** [@gaul](https://github.com/gaul) **Base:** `master` ← **Head:** `update/xmlerror` --- ### 📝 Commits (1) - [`b533091`](https://github.com/s3fs-fuse/s3fs-fuse/commit/b5330912bb5b9b329dd53059b3f87b674dd30dff) Improved handling of XML parser errors ### 📊 Changes **3 files changed** (+56 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/s3fs.cpp` (+8 -1) 📝 `src/s3fs_xml.cpp` (+8 -0) 📝 `src/s3fs_xml.h` (+40 -0) </details> ### 📄 Description ### Relevant Issue (if applicable) #2740 #2739 ### Details XML parsing errors that occur when calling `xmlReadMemory` are output to stderr, so I've changed it so that these are handled by s3fs. This allows the error content to be treated as an s3fs error. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>