-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[Bug]: Cron Error: Call to undefined method OC\Files\Node\File::getDirectoryListing()
#32450
Closed
5 of 8 tasks
Labels
Comments
OC\Files\Node\File::getDirectoryListing()
assuming you're using Nextcloud 24.0.0 @icewind1991 might look like the issue we fixed recently ? |
Yes, but happening since 22 I think... |
At the moment the error is thrown once per day. Interesstingly the time is moving, every day it's 5 minutes later than the day before. |
CarlSchwan
added a commit
that referenced
this issue
Jun 21, 2022
Fix #32450 Signed-off-by: Carl Schwan <carl@carlschwan.eu>
Fix in #32956 |
CarlSchwan
added a commit
that referenced
this issue
Jun 21, 2022
Fix #32450 Signed-off-by: Carl Schwan <carl@carlschwan.eu>
CarlSchwan
added a commit
that referenced
this issue
Jun 21, 2022
Fix #32450 Signed-off-by: Carl Schwan <carl@carlschwan.eu>
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug description
Executing the cron.php from time to time causes this error:
This is already happening longer time but just maybe once a week or so.
Steps to reproduce
unknown
Expected behavior
no error
Installation method
Official Docker image
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.0
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
No response
Are you using the Nextcloud Server Encryption module?
No response
What user-backends are you using?
Configuration report
No response
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: