The initial problem was that Storj buckets don't contain ETags, which causes panic while using Transcode API.
I added a unit test, but I'm somewhere on the fence if we should have it or not. @cyberj0g if you have any opinion, let me know. For the context, it does not make sense to have the whole "upload' test for Storj, because files added with AWS SDK to Storj actually includes ETag, only the files which are uploaded using the native Storj CLI (uplink) lack ETags.
fix https://github.com/livepeer/go-tools/issues/9
The initial problem was that Storj buckets don't contain ETags, which causes
panic
while using Transcode API.I added a unit test, but I'm somewhere on the fence if we should have it or not. @cyberj0g if you have any opinion, let me know. For the context, it does not make sense to have the whole "upload' test for Storj, because files added with AWS SDK to Storj actually includes ETag, only the files which are uploaded using the native Storj CLI (
uplink
) lack ETags.