immich has randomized temporal parsing of a series of photos with similar timestamps to an external library. #12942
Replies: 3 comments 1 reply
-
|
Appearance is not related to additional metadata information and has been tested several times. The metadata removal on the way to the test was all carried out using the specialized software XnViewMP. |
Beta Was this translation helpful? Give feedback.
-
Your files don't have a valid exif date, so it uses the filesystem time, which you're changing by messing with the files. |
Beta Was this translation helpful? Give feedback.
-
I modified the file creation time and modification time to simulate usage scenarios, and deliberately cleared metadata to ensure variable uniqueness, because the situation I encountered was more complex than such a simple simulation. This is the way I can try my best to minimize operations and reproduce exceptions. The retrieval of the same file time by immich appears to be inconsistent multiple times. |
Beta Was this translation helpful? Give feedback.
-
|
Same issue here I think, clean install, just testing. Im using an external library and some files upload fine but some have this error. Immich takes 3 different photos and creates an identical ID, seems like a bug. 2 of the photos have the same timestamp, 1 is 2 minutes later. All 3 have different names. `[Nest] 243 - 12/08/2024, 9:56:06 PM ERROR [Microservices:JobService] Unable to run job handler (library/library-sync-file): QueryFailedError: duplicate key value violates unique constraint "UQ_assets_owner_library_checksum" [Nest] 243 - 12/08/2024, 9:56:06 PM ERROR [Microservices:JobService] Unable to run job handler (library/library-sync-file): QueryFailedError: duplicate key value violates unique constraint "UQ_assets_owner_library_checksum" [Nest] 243 - 12/08/2024, 9:56:07 PM ERROR [Microservices:JobService] Unable to run job handler (library/library-sync-file): QueryFailedError: duplicate key value violates unique constraint "UQ_assets_owner_library_checksum" Edit: If I disable "Library Watching" the issue goes away for me... |
Beta Was this translation helpful? Give feedback.
-
The bug
immich has randomized temporal parsing of a series of photos with similar timestamps to an external library.Repeatedly putting the same file in and out of the external library will have a probability that some of the files will have time recognition anomalies.
Move the recognized abnormal file out of the external library and put it in again with the probability that it will be recognized correctly again.
The OS that Immich Server is running on
Linux Arc 6.10.10-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 12 Sep 2024 17:21:02 +0000 x86_64 GNU/Linux && podman version 5.2.2
Version of Immich Server
v1.115.0
Version of Immich Mobile App
v1.115.0
Platform with the issue
Your docker-compose.yml content
No special configuration, only add external librariesYour .env content
Reproduction steps
1.Arbitrary screenshot as a template, store it locally, copy it many times (enough, 100+ probability of time recognition anomaly)
2.Modify the timestamps of all test files to find past world errors recognized as current time. (I use Directory Opus to modify to past time)
3.Place all test files into any path in the external library and observe if the test files appear in today's image area.
4.If it does not appear, the test file will be moved out of the external library, put it in again, continue to observe, in general, 100 test files, repeat 1 to 3 times must appear a small number of time recognition error.
5.If there is a time recognition error, it is moved out of the external library individually and has a probability of being recognized correctly again.
...
Relevant log output
Additional information
In practice recognition errors can occur by placing enough temporally similar images into an external library.
Beta Was this translation helpful? Give feedback.
All reactions