runner: humanize max resolution errors from mediaconvert pipeline

[emranemran]

No description provided.

[codecov]

Codecov Report

Merging #150 (2172abf) into main (af4b3e0) will increase coverage by 0.04338%.
The diff coverage is 100.00000%.

@@                 Coverage Diff                 @@
##                main        #150         +/-   ##
===================================================
+ Coverage   11.41597%   11.45935%   +0.04338%     
===================================================
  Files             14          14                 
  Lines           2041        2042          +1     
===================================================
+ Hits             233         234          +1     
  Misses          1791        1791                 
  Partials          17          17                 

Impacted Files	Coverage Δ
task/runner.go	18.18182% <100.00000%> (+0.19117%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update af4b3e0...2172abf. Read the comment docs.

Impacted Files	Coverage Δ
task/runner.go	18.18182% <100.00000%> (+0.19117%)	⬆️

[thomshutt]

This is a good humanization of the error, but should we be smarter in our code that generates the output profiles? Assuming this big resolution is because we're matching a high-resolution source, we could set maximums there and not match beyond a defined maximum (probably 4K)

[emranemran]

This is a good humanization of the error, but should we be smarter in our code that generates the output profiles? Assuming this big resolution is because we're matching a high-resolution source, we could set maximums there and not match beyond a defined maximum (probably 4K)

Yeah we should. Filed livepeer/catalyst-api#468 to follow up. I'll go ahead and merge this so that we categorize these correctly for now until the Livepeer pipeline is fully in effect.