catalyst/mistserver: MOOV failure
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 16
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 1
Description
Mistserver complains about a file that works most of the time but occasionally fails with this:
```
305 [2022-10-18 04:26:36] MistInMP4:catalyst_vod_eefaghda (2632) FAIL : Error getting URI info for 'https://storage.googleapis.com/alex k-dms-upload-test/test-emran/new/10s.mp4.dtsh': 404 Not Found
306 [2022-10-18 04:26:36] MistInMP4:catalyst_vod_eefaghda (2632) FAIL : No MOOV box found; aborting header creation!
307 [2022-10-18 04:26:36] MistInMP4:catalyst_vod_eefaghda (2632) FAIL : Reading header for 's3+https://GOOG1EXCXWNKVLKBEJS62OMGXMQ5C5FH 67YZMQXYGFBQYQRBYXQQJT5OM6L4I:rzM9CFtiunoflGzBwU3c%2FOBw9D5hy0Ntb mmedu6x@storage.googleapis.com/alexk-dms-upload-test/test-emran/n ew/10s.mp4' failed.
```
[moov.log](https://github.com/livepeer/catalyst/files/9806604/moov.log)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached moov.log and the MistInMP4 error sequence, then compare the failing Google Cloud Storage request with a successful request for the same file. The issue names no source file or test, so first locate the code handling the MOOV/header request path. Done means the intermittent failure is reproducible, its cause is identified, and the file is processed without the MOOV error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, google-cloud
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100