Implemented import status

[noisecapella]

Fixes #111

[giocalitri]

what if some call fails?

[noisecapella]

The code above attaches handlers for the success case of deferred but doesn't actually resolve or reject the initial promise until this line. We need to resolve the initial promise so that it can start evaluating the other success callbacks. To illustrate:

deferred -> task1 -> task2 -> task3

deferred is always resolved. It doesn't do anything but we need to attach the task chain to something we have control of. Then task1 is evaluted. It returns a promise that's either rejected or resolved depending on how the AJAX request went. If task1 succeeded task2's success handler is then executed.

If task1 failed it would try to execute task2's failure handler, or task3, or whatever the next in line with a failure handler is. None of them have failure handlers so we just stop executing the chain in the event of a AJAX failure.

[giocalitri]

ok, got it

[giocalitri]

The UI does not look great:

@pdpinch ?

[giocalitri]

There is no way to dismiss the message:

[giocalitri]

Only two comments about the UI and one minor in the code.

[pdpinch]

Hi George. How close is this to being done? All things being equal I'd like to include it in the next release, but it's not critical if it's still need a lot of work.

[noisecapella]

@giocalitri uncovered an edge case where the imports in progress wouldn't disappear properly if the Celery server had stopped the worker. He also wanted changes to the UI as mentioned above. I don't think there's a lot of work left but it's not quite there yet