feat: add build depends libfreetype-dev - #28
Merged
Conversation
add build depends libfreetype-dev Log:
max-lvs
approved these changes
Mar 28, 2024
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: max-lvs, Zeno-sole The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Contributor
Author
|
/merge |
pppanghu77
added a commit
to pppanghu77/docparser
that referenced
this pull request
Jun 22, 2026
…<Default> - Wrap the <Default> branch in iterate_files_by_contenttype_expat_callback_element_start (xlsxio_read.c) with #ifndef USE_MINIZIP so the minizip backend skips the zip directory traversal at compile time; previously the traversal ran inside an expat callback while [Content_Types].xml was open for streaming read, reentering the minizip single-state handle and crashing in unzGetCurrentFileInfo (upstream issue linuxdeepin#28, unfixed in xlsxio 0.2.36) - Add regression sample tests/file/test_xlsxio_default_crash.xlsx whose [Content_Types].xml declares the main content type via <Default> to cover the former crash path 修复(excel): 修复 main contenttype 经 <Default> 声明的 xlsx 解析段错误 - 在 iterate_files_by_contenttype_expat_callback_element_start 的 <Default> 分支用 #ifndef USE_MINIZIP 包裹，使 minizip 后端编译期跳过 zip 目录遍历；原实现该遍历在 expat 回调内执行，而此时 [Content_Types].xml 已打开流式读取，对同一 unzFile 重入导致 minizip 单状态机冲突，在 unzGetCurrentFileInfo 处段错误（上游 issue linuxdeepin#28，xlsxio 0.2.36 未修复） - 新增回归样本 tests/file/test_xlsxio_default_crash.xlsx，其 [Content_Types].xml 将 main contenttype 经 <Default> 声明，覆盖原崩溃路径 Log: 修复 xlsxio 在 minizip 后端下解析 [Content_Types].xml 中经 <Default> 声明的 main contenttype 时，因目录遍历重入已打开文件的流式读取状态而在 unzGetCurrentFileInfo 处段错误的问题，并补充回归样本 Task: https://pms.uniontech.com/task-view-391297.html brechtsanders/xlsxio#28
deepin-bot Bot
pushed a commit
that referenced
this pull request
Jun 22, 2026
…<Default> - Wrap the <Default> branch in iterate_files_by_contenttype_expat_callback_element_start (xlsxio_read.c) with #ifndef USE_MINIZIP so the minizip backend skips the zip directory traversal at compile time; previously the traversal ran inside an expat callback while [Content_Types].xml was open for streaming read, reentering the minizip single-state handle and crashing in unzGetCurrentFileInfo (upstream issue #28, unfixed in xlsxio 0.2.36) - Add regression sample tests/file/test_xlsxio_default_crash.xlsx whose [Content_Types].xml declares the main content type via <Default> to cover the former crash path 修复(excel): 修复 main contenttype 经 <Default> 声明的 xlsx 解析段错误 - 在 iterate_files_by_contenttype_expat_callback_element_start 的 <Default> 分支用 #ifndef USE_MINIZIP 包裹，使 minizip 后端编译期跳过 zip 目录遍历；原实现该遍历在 expat 回调内执行，而此时 [Content_Types].xml 已打开流式读取，对同一 unzFile 重入导致 minizip 单状态机冲突，在 unzGetCurrentFileInfo 处段错误（上游 issue #28，xlsxio 0.2.36 未修复） - 新增回归样本 tests/file/test_xlsxio_default_crash.xlsx，其 [Content_Types].xml 将 main contenttype 经 <Default> 声明，覆盖原崩溃路径 Log: 修复 xlsxio 在 minizip 后端下解析 [Content_Types].xml 中经 <Default> 声明的 main contenttype 时，因目录遍历重入已打开文件的流式读取状态而在 unzGetCurrentFileInfo 处段错误的问题，并补充回归样本 Task: https://pms.uniontech.com/task-view-391297.html brechtsanders/xlsxio#28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
add build depends libfreetype-dev
Log: