Does not work on purge-days #168

New Issue

michael · 2026-01-19T18:29:15Z

michael commented

2026-01-19 18:29:15 +00:00

Originally created by @wc7086 on GitHub.

I used purge-days in the command, but MaxDate in metadata still shows as 0001-01-01T00:00:00Z

transfer.sh version: transfer.sh 1.2.4: Easy file sharing from the command line

os: Linux 5.10.0-0.bpo.7-amd64 #1 SMP Debian 5.10.40-1~bpo10+1 (2021-06-04) x86_64 GNU/Linux

Debian 10

Originally created by @wc7086 on GitHub. I used `purge-days` in the command, but `MaxDate` in `metadata` still shows as `0001-01-01T00:00:00Z` transfer.sh version: transfer.sh 1.2.4: Easy file sharing from the command line os: Linux 5.10.0-0.bpo.7-amd64 #1 SMP Debian 5.10.40-1~bpo10+1 (2021-06-04) x86_64 GNU/Linux Debian 10

michael closed this issue

2026-01-19 18:29:15 +00:00

michael commented

2026-01-19 18:29:16 +00:00

@paolafrancesca commented on GitHub:

@wc7086 purge-days does not effect MaxDate in metadata. it deletes the files from the storage after the number of days setup

@paolafrancesca commented on GitHub: @wc7086 `purge-days` does not effect `MaxDate` in metadata. it deletes the files from the storage after the number of days setup

michael commented

2026-01-19 18:29:16 +00:00

@paolafrancesca commented on GitHub:

When I change servers, how does the program know when files need to be deleted?

sorry, I forgot to answer your question

the logic is different according to backend storage: on s3 and storj the expiration date of the object for the bucket is set on upload, on local storage and gdrive it will delete any file that at any purge scans has the creation date + purge days after the time of the scan

@paolafrancesca commented on GitHub: > When I change servers, how does the program know when files need to be deleted? sorry, I forgot to answer your question the logic is different according to backend storage: on s3 and storj the expiration date of the object for the bucket is set on upload, on local storage and gdrive it will delete any file that at any purge scans has the creation date + purge days after the time of the scan

michael commented

2026-01-19 18:29:16 +00:00

@paolafrancesca commented on GitHub:

0 is the zero value: it means that the feature is disabled.
In REAMDE.md no zero default value are reported.

@stefanbenten what do you think? Should we report them with something like 0 (disabled)?

@paolafrancesca commented on GitHub: `0` is the zero value: it means that the feature is disabled. In `REAMDE.md` no zero default value are reported. @stefanbenten what do you think? Should we report them with something like `0 (disabled)`?

michael commented

2026-01-19 18:29:16 +00:00

@wc7086 commented on GitHub:

I think the necessary Value in Usage in README.md needs to be filled in, even if the default value is 0.

@wc7086 commented on GitHub: I think the necessary `Value` in `Usage` in README.md needs to be filled in, even if the default value is `0`.

michael commented

2026-01-19 18:29:16 +00:00

@wc7086 commented on GitHub:

@wc7086 purge-days does not effect MaxDate in metadata. it deletes the files from the storage after the number of days setup

When I change servers, how does the program know when files need to be deleted?

@wc7086 commented on GitHub: > @wc7086 `purge-days` does not effect `MaxDate` in metadata. it deletes the files from the storage after the number of days setup When I change servers, how does the program know when files need to be deleted?

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dutchcoders/transfer.sh#168