Change Details

This may be an expected behavior, but today I was working on setting up video embedding. I dropped a sample mp4 onto our phab homepage to upload and it worked as expected. However, I was having trouble getting it to display/embed using the {FXXX media=video} syntax. I looked at the file details and its mime type had been changed to application/octet-stream. This may be intended behavior, but it wasn't clear to me. {F1706779} What I think is especially noteworthy is that going into the Files application and uploading a file through the picker behaves differently. Specifically, in our install it threw an exception about not having a configured storage engine (I realize this may be an issue specific to our instance/config, but I would expect the two ways of upload files to behave the same...?) {F1706777}

This may be an expected behavior, but today I was working on setting up video embedding. I dropped a sample mp4 onto our phab homepage to upload and it worked as expected. However, I was having trouble getting it to display/embed using the {FXXX media=video} syntax. I looked at the file details and its mime type had been changed to application/octet-stream. This may be intended behavior, but it wasn't clear to me. {F1706779} What I think is especially noteworthy is that going into the Files application and uploading a file through the picker behaves differently. Specifically, in our install it threw an exception about not having a configured storage engine (I realize this may be an issue specific to our instance/config, but I would expect the two ways of upload files to behave the same...?) {F1706777} Edit: We're fairly up to date, but here you go nonetheless phabricator cadac75b82bbed18d52c3ee7ba6d396bff69c009 (Fri, Jun 24) arcanist 18b27b03fa3d9f2439bf998c5fa2e4f5bd93db16 (Sat, Jun 18) phutil 8aa8612a094b4dafcf5c461b746a613a1e229b86 (Sat, Jun 18)

This may be an expected behavior, but today I was working on setting up video embedding. I dropped a sample mp4 onto our phab homepage to upload and it worked as expected. However, I was having trouble getting it to display/embed using the {FXXX media=video} syntax. I looked at the file details and its mime type had been changed to application/octet-stream. This may be intended behavior, but it wasn't clear to me. {F1706779} What I think is especially noteworthy is that going into the Files application and uploading a file through the picker behaves differently. Specifically, in our install it threw an exception about not having a configured storage engine (I realize this may be an issue specific to our instance/config, but I would expect the two ways of upload files to behave the same...?) {F1706777} Edit: We're fairly up to date, but here you go nonetheless phabricator cadac75b82bbed18d52c3ee7ba6d396bff69c009 (Fri, Jun 24) arcanist 18b27b03fa3d9f2439bf998c5fa2e4f5bd93db16 (Sat, Jun 18) phutil 8aa8612a094b4dafcf5c461b746a613a1e229b86 (Sat, Jun 18)