-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Description
The bug
After scanning images from my external library, the deduplication tool prompted me to review duplicate images. I stacked all of them. But when I refreshed the page, the same set of images appeared again for me to review.
Later on I found clicking "keep all" had the same issue.
Before:
Then I clicked keep all:
Refresh the page:
Reran the dedup job and the same issue persisted.
If I trashed photos then they would disappear.
The OS that Immich Server is running on
Ubuntu 24.04
Version of Immich Server
v1.125.7
Version of Immich Mobile App
NA
Platform with the issue
- Server
- Web
- Mobile
Your docker-compose.yml content
Identical to https://github.com/immich-app/immich/blob/v1.125.7/docker/docker-compose.yml with external library and userns_mode: "keep-id"
Your .env content
Identical to https://github.com/immich-app/immich/blob/v1.125.7/docker/example.env
Reproduction steps
- Scan from external library
- Resolve duplicates in one go
- Refresh and same photos show up
...
Relevant log output
Additional information
At one time I held Shift+S to stack all duplicates and because it was too fast, the server ran into an error
ERROR [Api:ErrorInterceptor~xa7l1wf4] Unknown error: PostgresError: duplicate key value violates unique constraint "REL_91704e101438fd0653f582426d"
PostgresError: duplicate key value violates unique constraint "REL_91704e101438fd0653f582426d"
at ErrorResponse (/usr/src/app/node_modules/postgres/cjs/src/connection.js:788:26)
at handle (/usr/src/app/node_modules/postgres/cjs/src/connection.js:474:6)
at Socket.data (/usr/src/app/node_modules/postgres/cjs/src/connection.js:315:9)
at Socket.emit (node:events:524:28)
at addChunk (node:internal/streams/readable:561:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
at Readable.push (node:internal/streams/readable:392:5)
at TCP.onStreamRead (node:internal/stream_base_commons:189:23)
at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
I wonder if this could be related, but probably not. And if this was a user error, how should one remedy it?

