Skip to content

Cleanup to not handle memory allocation failure#1882

Merged
revonateB0T merged 2 commits intomainfrom
quota
Nov 4, 2024
Merged

Cleanup to not handle memory allocation failure#1882
revonateB0T merged 2 commits intomainfrom
quota

Conversation

@revonateB0T
Copy link
Copy Markdown
Collaborator

No description provided.

@revonateB0T revonateB0T requested a review from FooIbar November 4, 2024 11:37
@revonateB0T revonateB0T requested a review from FooIbar November 4, 2024 11:59
@revonateB0T
Copy link
Copy Markdown
Collaborator Author

revonateB0T commented Nov 4, 2024

archive_read_open_memory may fail on illegal archive format
Mostly when user rename something to .zip and open it...

Copy link
Copy Markdown
Owner

@FooIbar FooIbar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unrelated, but although we return 0 on failure here, 0 is not considered a failure in ArchivePageLoader.

@revonateB0T revonateB0T enabled auto-merge (squash) November 4, 2024 12:04
@revonateB0T
Copy link
Copy Markdown
Collaborator Author

Unrelated, but although we return 0 on failure here, 0 is not considered a failure in ArchivePageLoader.

Anyway they are the same meaning, "we cannot find sth. to read"

@revonateB0T revonateB0T merged commit 8ca0a32 into main Nov 4, 2024
@revonateB0T revonateB0T deleted the quota branch November 4, 2024 12:06
@FooIbar
Copy link
Copy Markdown
Owner

FooIbar commented Nov 4, 2024

Unrelated, but although we return 0 on failure here, 0 is not considered a failure in ArchivePageLoader.

Anyway they are the same meaning, "we cannot find sth. to read"

0 is treated as a success there so no error message will be displayed, just a blank screen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants