starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[PR #651] [MERGED] Gracefully handle unexpected end of file when listing backup files #3390

New Issue
Closed
opened 2026-04-25 00:15:28 +02:00 by adam · 0 comments
adam commented 2026-04-25 00:15:28 +02:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/advplyr/audiobookshelf/pull/651
Author: @selfhost-alt
Created: 5/31/2022
Status: ✅ Merged
Merged: 6/2/2022
Merged by: @advplyr

Base: master ← Head: handle-another-backup-parse-error

📝 Commits (1)

  • 1350a91 Handle another type of corrupted backup file

📊 Changes

1 file changed (+3 additions, -0 deletions)

View changed files

📝 server/managers/BackupManager.js (+3 -0)

📄 Description

A few weeks ago I added some logic to handle one kind of backup file corruption when listing backups in #555. Today when looking at my backups, I found that there's another type of error that should also be handled. Namely, when a backup file is unexpectedly truncated.

🔄 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/advplyr/audiobookshelf/pull/651 **Author:** [@selfhost-alt](https://github.com/selfhost-alt) **Created:** 5/31/2022 **Status:** ✅ Merged **Merged:** 6/2/2022 **Merged by:** [@advplyr](https://github.com/advplyr) **Base:** `master` ← **Head:** `handle-another-backup-parse-error` --- ### 📝 Commits (1) - [`1350a91`](https://github.com/advplyr/audiobookshelf/commit/1350a91fba3e0319e207a2b00ee6d92ba97517fc) Handle another type of corrupted backup file ### 📊 Changes **1 file changed** (+3 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `server/managers/BackupManager.js` (+3 -0) </details> ### 📄 Description A few weeks ago I added some logic to handle one kind of backup file corruption when listing backups in #555. Today when looking at my backups, I found that there's another type of error that should also be handled. Namely, when a backup file is unexpectedly truncated. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2026-04-25 00:15:28 +02:00
adam closed this issue 2026-04-25 00:15:28 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#3390
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?