Comment 1 Susan McCourt 2011-11-24 11:36:48 EST

assigning to Gosia while she reviews progress API.  
The original bug was about adding more progress indication to tasks, and this question is really a separate question.

Comment 2 Malgorzata Janczarska 2011-11-24 11:55:19 EST

I'll look at it tomorrow.

Comment 3 Malgorzata Janczarska 2011-11-25 07:30:00 EST

You found an important issue that needs to be rethought and I think unified.
Task can now fail in two ways:
1. Task is scheduled, returning 201 and then one of the responses from progress service contains "error" indicating that task failed. But still the responose has status===200
2. Task is not scheduled, but we get the result straight away. This means we can also get an error (status !== 200 && status !==201)
Good that you made a fix in commit 0f965d7f230d4004a0eb9af3fdf93258f114e5f7 (new file and new folder operations could use progress indicator, add errback to progress handler), because case "2" was until now swallowed. But I think we still need to return it in somehow.
Look at merge command in gitCommands.js it tried to solve this problem. But I think this should be somehow unified, so that we don't have to add double error handling like in merge command.

Comment 4 Szymon Brandys 2011-12-12 09:19:57 EST

The answer for this question is part of bug 344012 work.

Comment 5 Malgorzata Janczarska 2014-09-12 08:11:13 EDT

Looks like this problem was solved.