sigoden/dufs
1
0
Fork 0
mirror of https://github.com/sigoden/dufs.git synced 2026-04-08 16:49:02 +03:00
Code Issues 8 Packages Projects Releases 10 Wiki Activity

[PR #566] [CLOSED] Maximum archive size and --follow-symlinks flag #642

New Issue
Closed
opened 2026-04-08 16:53:47 +03:00 by zhus · 0 comments
zhus commented 2026-04-08 16:53:47 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/sigoden/dufs/pull/566
Author: @falko17
Created: 4/4/2025
Status: ❌ Closed

Base: main ← Head: dev

📝 Commits (3)

  • e60d52a feat: add --follow-symlinks flag to follow links for search/archiving
  • baa8bab feat: allow configuring maximum archive size
  • 7474d79 fix: incorrect directory size due to wrong variable being used

📊 Changes

3 files changed (+81 additions, -18 deletions)

View changed files

📝 assets/index.js (+2 -2)
📝 src/args.rs (+27 -0)
📝 src/server.rs (+52 -16)

📄 Description

This PR adds the following changes:

  • A --follow-symlinks flag has been added. When set (false by default), searching and archiving will follow symlinks (i.e., include targets in searches/ZIP files).
  • A --max-archive-size flag has been added with which a maximum byte size for archives can be set. The purpose of this is to prevent huge downloads, which could use up more resources than desired (bandwidth/CPU if compression is enabled).
    • Implementing this feature itself was pretty straightforward, but I had to refactor the handle_zip_files function a little to make it possible to display an error message to the user when the archive turns out too big.
  • A small bug has been fixed that lead to an incorrect item count being displayed for directories.

🔄 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/sigoden/dufs/pull/566 **Author:** [@falko17](https://github.com/falko17) **Created:** 4/4/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `dev` --- ### 📝 Commits (3) - [`e60d52a`](https://github.com/sigoden/dufs/commit/e60d52a13698479279c0d20fb9aaee8b37d55081) feat: add --follow-symlinks flag to follow links for search/archiving - [`baa8bab`](https://github.com/sigoden/dufs/commit/baa8babc59788ad5e304133c48d33d6dbaf799f8) feat: allow configuring maximum archive size - [`7474d79`](https://github.com/sigoden/dufs/commit/7474d79948b7123cbb155cabf73395e0683e52fc) fix: incorrect directory size due to wrong variable being used ### 📊 Changes **3 files changed** (+81 additions, -18 deletions) <details> <summary>View changed files</summary> 📝 `assets/index.js` (+2 -2) 📝 `src/args.rs` (+27 -0) 📝 `src/server.rs` (+52 -16) </details> ### 📄 Description This PR adds the following changes: * A `--follow-symlinks` flag has been added. When set (`false` by default), searching and archiving will follow symlinks (i.e., include targets in searches/ZIP files). * A `--max-archive-size` flag has been added with which a maximum byte size for archives can be set. The purpose of this is to prevent huge downloads, which could use up more resources than desired (bandwidth/CPU if compression is enabled). * Implementing this feature itself was pretty straightforward, but I had to refactor the `handle_zip_files` function a little to make it possible to display an error message to the user when the archive turns out too big. * A small bug has been fixed that lead to an incorrect item count being displayed for directories. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
zhus added the pull-request label 2026-04-08 16:53:47 +03:00
zhus closed this issue 2026-04-08 16:53:47 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zhus
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sigoden/dufs#642
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?