upmaru / upstream Goto Github PK

We need some tests for large file uploading

In case upload fails we need to handle resumable upload.

On complete might be a failure, don’t make a call to studio handle the error better. (Tell user to retry? And use resumable feature of fine uploading)

When upstream process is long running the authorization key can expire returning a

HTTP request error: {{{:badmatch, {:error, %Upstream.Error{code: "expired_auth_token", message: "Authorization token has expired", status: 401}}}, [{Studio.Content.Imaging, :"-url_template/2-fun-0-", 1, [file: 'lib/studio/content/imaging.ex', line: 19]}, {Studio.Cache, :handle_call, 3, [file: 'lib/studio/cache/cache.ex', line: 42]}, {:gen_server, :try_handle_call, 4, [file: 'gen_server.erl', line: 636]}, {:gen_server, :handle_msg, 6, [file: 'gen_server.erl', line: 665]}, {:proc_lib, :init_p_do_apply, 3, [file: 'proc_lib.erl', line: 247]}]}, {GenServer, :call, [Studio.Cache, {:cache_with_ttl, "posts", [ttl: 86400], #Function<0.131674544/0 in Studio.Content.Imaging.url_template/2>}, 5000]}}

We need to handle this error and restart upstream in the elixir app, so it can re authorize.

We need to finish the GenServer for the simple file.

Since we might be able to leverage resumable js, see if its possible to take the chunks from resumable js and upload straight to b2

https://app.timber.io/upmaru/logs/console?apps%5B0%5D=2907&id=6407917021882740736&date=2018-05-31T11%3A34%3A28.941154Z

Right now we are streaming once for calculating sha1 and chunk size, we should write the stream to a file while doing the first pass so it doesn't eat up memory, opening up possibility to multiple large file uploading concurrently.

It would be nice to just have mountable endpoints so we can easily use this in a phoenix app.

We need the ability to start Blazay dynamically so https://github.com/upmaru/cumulus can retrieve the configuration dynamically from the node that dispatched the encoding job, to upload to the correct bucket.