Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Diplay order oldest first doesn't work #17101

Closed
2 of 4 tasks
FideliusFalcon opened this issue Mar 25, 2025 · 14 comments · Fixed by #17106
Closed
2 of 4 tasks

Diplay order oldest first doesn't work #17101

FideliusFalcon opened this issue Mar 25, 2025 · 14 comments · Fixed by #17106

Comments

@FideliusFalcon
Copy link

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.

  • Yes

The bug

After upgrading to v1.130.0 the album display order "oldest first" doesn't work, and is showing newest first.

I can't replicate this on the iOS mobile app running v1.129.0

The OS that Immich Server is running on

Ubuntu 24.04.2

Version of Immich Server

v1.130.0

Version of Immich Mobile App

v1.129.0

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

name: immich

services:
  immich-server:
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    networks:
      default:
      nginx-proxy-manager_overlay:
    ports:
      - '2283:2283'
    depends_on:
      - redis
      - database
    restart: always
    healthcheck:
      disable: false
    deploy:
      resources:
        limits:
          cpus: '1'

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    #   file: hwaccel.ml.yml
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always
    healthcheck:
      disable: false
    deploy:
      resources:
        limits:
          cpus: '2'

  redis:
    container_name: immich_redis
    image: docker.io/redis:6.2-alpine@sha256:905c4ee67b8e0aa955331960d2aa745781e6bd89afc44a8584bfd13bc890f0ae
    healthcheck:
      test: redis-cli ping || exit 1
    restart: always
    
  database:
    container_name: immich_postgres
    image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
    volumes:
      # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCAT>
      - ${DB_DATA_LOCATION}:/var/lib/postgresql/data
    healthcheck:
      test: >-
        pg_isready --dbname="$${POSTGRES_DB}" --username="$${POSTGRES_USER}" || exit 1;
        Chksum="$$(psql --dbname="$${POSTGRES_DB}" --username="$${POSTGRES_USER}" --tuples-only --no-align
        --command='SELECT COALESCE(SUM(checksum_failures), 0) FROM pg_stat_database')";
        echo "checksum failure count is $$Chksum";
        [ "$$Chksum" = '0' ] || exit 1
      interval: 5m
      start_interval: 30s
      start_period: 5m
    command: >-
      postgres
      -c shared_preload_libraries=vectors.so
      -c 'search_path="$$user", public, vectors'
      -c logging_collector=on
      -c max_wal_size=2GB
      -c shared_buffers=512MB
      -c wal_compression=on
    restart: always

volumes:
  model-cache:

networks:
  default:
  nginx-proxy-manager_overlay:
    external: true

Your .env content

# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables

# The location where your uploaded files are stored
UPLOAD_LOCATION=./library
# The location where your database files are stored
DB_DATA_LOCATION=./postgres

# To set a timezone, uncomment the next line and change Etc/UTC to a TZ identifier from this list: https://en.wikipedia.org/wiki/List_>
# TZ=Etc/UTC

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release

# Connection secret for postgres. You should change it to a random password
# Please use only the characters `A-Za-z0-9`, without special characters or spaces
DB_PASSWORD=redacted

# The values below this line do not need to be changed
###################################################################################
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

Reproduction steps

  1. Open album
  2. Open Options
  3. Set Display order -> "Oldest First"

Relevant log output

Additional information

No response

@frederikb96
Copy link

Same problem for me. After upgrade to 130 the display order is not recognized anymore. The new UI is super nice, so I hope that this tiny bug can be fixed soon :)
It also appears in the web view for externally shared albums.

@alextran1502
Copy link
Contributor

@FideliusFalcon Have you tried clicking on the button again? it would resort the order

@frederikb96
Copy link

I realized that for some albums the sorting works, but for some it doesn't. I will check if I can see why it is working for some but not the others.

@FideliusFalcon
Copy link
Author

@FideliusFalcon Have you tried clicking on the button again? it would resort the order

Yes I have tried many times

@alextran1502
Copy link
Contributor

alextran1502 commented Mar 25, 2025

I can't reproduce it. Do you mind create a video capture to show how you use the feature?

@FideliusFalcon
Copy link
Author

I can't reproduce it. Do you mind create a video capture to show how you use the feature?

Here: https://github.com/user-attachments/assets/35771e78-eb68-4d19-b688-a5b1b838898f

@frederikb96
Copy link

Yes sure, I made two videos.
First video is about the problem the sorting is not happening .

Screencast.From.2025-03-25.19-40-56.webm

Second video is about a strange bug that only a few pictures are sorted out of order.

Screencast.From.2025-03-25.19-39-42.webm

@alextran1502
Copy link
Contributor

Ohh, within the album, I was checking at the album page

@frederikb96
Copy link

frederikb96 commented Mar 25, 2025

@alextran1502 Thanks for the swift fix, but sadly the issue still persists for me on 130.1.

Maybe this sample album helps debugging the issue with some images which are sorted in some strangely wrong order:
https://photos.bergrunde.net/share/GIgfVkLJ2FmzhD85Sy9bxS8AzjmsLli_FQCWf1S70iEholjaBV_7UOXo1Yl65rax1s4?at=689eec21-5838-4d22-8f19-e4a16ef5858e

Image

@FideliusFalcon
Copy link
Author

The sort on specific days is now correct, but it is still sorting days from newest.

See screenshot, with sort by oldest first

Image

@alextran1502
Copy link
Contributor

@FideliusFalcon do you mind send me those assets? They are handy for testing

@FideliusFalcon
Copy link
Author

@alextran1502
Sure but you need to modify the date of one of the assets yourself to see the issue.

Test-20250325_224756.zip

@FideliusFalcon
Copy link
Author

@alextran1502 I can validate that it's now fixed with version v1.130.2
Thanks for the great work!

@alextran1502
Copy link
Contributor

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants