-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
fix(TaskProcessing): Log mime_content_type() failure at info level
#54673
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
Conversation
mime_content_type() with Nextcloud’s internal APIs
|
This does not work because the file name has no extension. We have to get the file content to guess the mimetype. The warning mentioned in #54669 does not prevent |
Oh, good point 👍
Since
Or are you suggesting to just |
|
I think it's fine like it is now. |
|
Confirmed in the issue. It's working fine. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
1b91819 to
7b86624
Compare
Signed-off-by: Git'Fellow <[email protected]>
7b86624 to
8557f66
Compare
Lowered to info as per your suggestion. |
mime_content_type() with Nextcloud’s internal APIsmime_content_type() failure at info level
|
According to the logs, I'm not sure there is an exception thrown. It's just a log line written by |
Try to fix #54669
Summary
Replaced the
mime_content_type()call with Nextcloud’s internal APIs.Checklist