ELEMENTS-1281: handle errors on bulk action

[RSalem07]

I updated the requirements, This PR depends now on the platform one PR#4606

**Note for the reviewers ** :)

Initially I have used the error event name, Here But I got some errors on the unit tests, mainly on the nuxeo-audit-page-provider.test.js where the two tests below failed:

Should fire an event when an error occurs in the Operation call and Should return an error when occurs in the Operation call as they expect to get the notify event, but it failed. That's the main reason why I have changed the name to failure, before that I have tried different approche to try to fix it by keeping the error event name. Finally I used the failure let me know wdyt

thx

[nuxeojenkins]

View issue in JIRA: ELEMENTS-1281: Add Errors handler for Nuxeo Operation

[RSalem07]

@Gabez0r as asked the WEB-UI pipeline with this Element branch is launched: https://qa.nuxeo.org/jenkins/job/master/job/web-ui-pipeline/349/

[richardsd]

It looks good to me 👍

[nelsonsilva]

thanks @RSalem07 clearly we have a lot of margin for improvement when it comes to error handling but I'm not a big fan of explicitly stopping error propagation on each element so I'd rather we spent some time figuring out a better, more holistic, approach to the problem.
The operation execution does throw error when called programatically, so you can get the error in the catch block. Also we set an error property which you could listen too if you really wanted with on-error-changed so I'm not sure how much of this you really need. Do you have a PR with the consumer of this improvements (ie the bulk action where you'd like to report errors) ?

[RSalem07]

Hey @nelsonsilva :)

For now the one that needs this improvement is mainly the retention add-on. I have opened a PR nuxeo/nuxeo-retention#42

Also we set an error property which you could listen too if you really wanted with on-error-changed so I'm not sure how much of this you really need

ah I see your point, my initial idea was to keep the same logic then the others (start pooling...)

thx

[RSalem07]

@nelsonsilva following our discussion, I have reverted the stop propagation error. I kept the update for a better error handling. please note that this PR is related to the backend one PR#4606. I have also update the retention one to use a simple catch on the promise PR#42.

Thx,

[RSalem07]

new Jenkins build on WEB-UI https://qa.nuxeo.org/jenkins/job/master/job/web-ui-pipeline/354/ -> OK