nextcloud / nextcloud/previewgenerator
Exclude folders from the initial generation by their names
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 520
- Forks
- 55
- PR merge metrics
- No merged PRs in 30d
Description
HI,
I tried that app and relaized it tries to permutate through all folders.
The folder "dot" .zfs is a default virtual folder that contains all zfs snapshots of the past which will show my file system in read only mode as it was the day before and so on...
That means
a) I cannot add a .nomedia file
b) it contains all my images over and over and over again with a different path as my server creates a sbapshot every day....
and it failed anyway ;) but I won't be able to debug...
2024-06-25T13:01:42+00:00 Scanning folder /main/files
2024-06-25T13:01:42+00:00 Scanning folder /main/files/content_main
2024-06-25T13:01:42+00:00 Scanning folder /main/files/content_main/.Trash-1000
2024-06-25T13:01:42+00:00 Scanning folder /main/files/content_main/.Trash-1000/files
2024-06-25T13:01:42+00:00 Scanning folder /main/files/content_main/.Trash-1000/files/bridge
2024-06-25T13:01:42+00:00 Scanning folder /main/files/content_main/.Trash-1000/info
2024-06-25T13:01:42+00:00 Scanning folder /main/files/content_main/.zfs
2024-06-25T13:01:42+00:00
2024-06-25T13:01:42+00:00 In Parser.php line 157:
2024-06-25T13:01:42+00:00
2024-06-25T13:01:42+00:00 Malformed state response from server
2024-06-25T13:01:42+00:00
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading Parser.php around line 157 and tracing the initial-generation folder traversal shown in the issue logs. Determine where folder names can be excluded before scanning, then verify that .zfs and other excluded names are not traversed and that generation no longer reaches the reported malformed state response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100