Bug Report: Empty Directories Reported as "file does not exist" and Summary Accounting Appears Inconsistent
Environment
- immich-go 0.32.0
- macOS (Apple Silicon)
upload from-folder- Recursive import
Summary
When importing a folder tree containing empty date directories,
immich-go logs errors such as:
ERR 2017/11/14: file does not exist
The directories exist; they are simply empty.
The final summary also appears internally inconsistent.
Reproduction
Example hierarchy:
Bruno_WorkHobby/
└── 2017/
├── 07/01/
├── 07/10/
└── 11/14/
where the listed directories are empty.
Run:
immich-go upload from-folder --recursive ...
Observed Behavior
The log contains:
ERR 2017/11/14: file does not exist
ERR 2017/10/01: file does not exist
ERR 2022/09/13: file does not exist
Verification:
find "/Volumes/Photos/Photo Library/Bruno_WorkHobby" -type d -empty
returns those exact directories.
Example:
ls -al "/Volumes/Photos/Photo Library/Bruno_WorkHobby/2017/11/14"
shows only:
indicating the directory exists and is simply empty.
Summary Inconsistency
Example:
Total Assets: 3716
Processed: 3686
Discarded: 30
Errors: 0
Pending: 0
Asset Lifecycle (PROCESSED):
metadata updated : 3716
Asset Lifecycle (DISCARDED):
server has duplicate : 3686
These values are difficult to reconcile.
In this dataset:
- 19 empty directories generated "file does not exist" errors.
- 1 banned
.DS_Store was reported.
- The remaining discarded count is unexplained.
Expected Behavior
- Empty directories should either be ignored silently or logged as:
Skipping empty directory: 2017/11/14
Impact
The current logging suggests missing media files when the issue is
actually empty directories. The summary also makes it difficult to
verify that every asset was processed correctly.
Bug Report: Empty Directories Reported as "file does not exist" and Summary Accounting Appears Inconsistent
Environment
upload from-folderSummary
When importing a folder tree containing empty date directories,
immich-go logs errors such as:
The directories exist; they are simply empty.
The final summary also appears internally inconsistent.
Reproduction
Example hierarchy:
where the listed directories are empty.
Run:
Observed Behavior
The log contains:
Verification:
find "/Volumes/Photos/Photo Library/Bruno_WorkHobby" -type d -emptyreturns those exact directories.
Example:
ls -al "/Volumes/Photos/Photo Library/Bruno_WorkHobby/2017/11/14"shows only:
indicating the directory exists and is simply empty.
Summary Inconsistency
Example:
These values are difficult to reconcile.
In this dataset:
.DS_Storewas reported.Expected Behavior
They should not produce "file does not exist" errors.
The summary should account for every discarded item consistently.
Impact
The current logging suggests missing media files when the issue is
actually empty directories. The summary also makes it difficult to
verify that every asset was processed correctly.