-
Notifications
You must be signed in to change notification settings - Fork 26
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
bugfix/unique-temp-filenames #225
bugfix/unique-temp-filenames #225
Conversation
…validator for time duration, add range filter to ffmpeg audio split, update tests
…mpeg error logging
… host when limiting video to a range, updated mp4 conversion to allow a range, connected mp4 to clip functionality, updated tests and tried to make testing slightly more consistent, added Session ingestion verification to test out
…ix in cdp_will_host control structure
Codecov Report
@@ Coverage Diff @@
## main #225 +/- ##
==========================================
+ Coverage 72.40% 72.68% +0.28%
==========================================
Files 64 64
Lines 3541 3581 +40
==========================================
+ Hits 2564 2603 +39
- Misses 977 978 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
Thank you Chris! Just one question.
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 think this all looks good to me with two caveats:
- the thing @dphoria already mentioned about pulling in the correct extension
- a bit more complicated, one of the things that is decently important is that the produced files related to a session are all uploaded with deterministic names. I think a prior version of this PR actually used the
session_content_hash
which I think is the correct thing to use instead of auuid
. The reasoning here is that when it comes time to pulling down audio files from the database (which is never done for the app side of things but is done in my research) we need a deterministic name. If all of that made sense, the question is: after these changes, do the files that are ultimately stored to the file storage system / Google Cloud Storage have deterministic naming?
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.
Assuming the correct extension gets passed through. Then all looks good. Thanks @chrisjkhan for checking the determinism aspect ❤️
Will merge once I see the extension work go through and tests pass.
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.
Looks good to me! @dphoria can you also check this. Will merge soon!
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.
Ship it~ 🚀
@evamaxfield actually, it's not working right now. I was wanting to reach out to see if you knew what might be wrong. The temporary video file exists in the context of the File exists here: But not here: cdp-backend/cdp_backend/utils/file_utils.py Line 724 in 01595c3
@dphoria let me know if you have any ideas |
🤣 I have failed as a reviewer. Anyway, good catch Chris. I'm preoccupied with some other stuff today; will try to debug when I can later today. Hopefully you'll figure it out soon. 😅 |
I will also try to take a look asap |
Thanks for making all the changes @chrisjkhan! Merging and releasing new version. Upgrade should rollout in ~2 hours. |
This pull request resolves #226
Use content hash for temp video file naming to prevent collisions across