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

External Library enables file system change monitoring, it will ignore the configured ignore paths and directly add the file to the file processing queue. #14637

Open
1 of 3 tasks
Gloryandel opened this issue Dec 11, 2024 · 1 comment
Assignees

Comments

@Gloryandel
Copy link

Gloryandel commented Dec 11, 2024

The bug

When External Library enables file system change monitoring, it will ignore the configured ignore paths and directly add the file to the file processing queue.Manual scanning of newly added files in the same path External Library ignore configuration works fine

It led to another chain reaction #14636

The OS that Immich Server is running on

ArchLinux

Version of Immich Server

v1.122.2

Version of Immich Mobile App

v1.122.2

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

none

Your .env content

none

Reproduction steps

  1. Enable file system change monitoring
  2. Configure External Library, configure the ignore path settings, and modify the files in the ignore path.
  3. Files in the ignore path are immediately queued for processing.

Relevant log output

none

Additional information

No response

@Gloryandel Gloryandel changed the title When External Library enables file system change monitoring, it will ignore the configured ignore paths and directly add the file to the file processing queue. External Library enables file system change monitoring, it will ignore the configured ignore paths and directly add the file to the file processing queue. Dec 11, 2024
@etnoy etnoy self-assigned this Dec 19, 2024
@etnoy
Copy link
Contributor

etnoy commented Dec 19, 2024

Thanks for the report. We have a library refresh refactor coming that should fix this

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

No branches or pull requests

2 participants