-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Use mimetype from cache for workflow checks #25768
Conversation
264c449
to
de77189
Compare
That renders the check fairly useless when working with non-local files, doesn't it? |
I'm unsure about having the content-based detection in the first place, having the filecache and workflow both use different sources of mimetypes is bound to lead to confusion |
CI is unhappy |
/rebase |
de77189
to
919e256
Compare
Signed-off-by: Robin Appelman <[email protected]>
the method is only called if the file exists already a check against storing the fallback mimetype is added as a safety instead Signed-off-by: Robin Appelman <[email protected]>
Signed-off-by: Robin Appelman <[email protected]>
919e256
to
cb4648d
Compare
rebased and conflict solved |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
I wasn't able to run into such situation myself with minio as primary object store, however I sent this to someone having issues with flow and mime types and can confirm that this fixed the problem. Let's ship this!
/backport to stable25 |
/backport to stable24 |
file_exists
checkMotivation is that when using object stores, the file is added to the cache (and thus triggering workflow hooks) before it's written to the storage.