* Convert pinboard actions to use hook-based actions
* Convert action bar actions to use hook-based actions
* Make create interactive task use hook-based actions
* Convert a second cancel-all to use hook-based actions
* Use hook-based actions for creating interactive tasks
* Remove angular $timeout, $apply
* Abstract away retrigger & cancel functions
* Remove thBuildApi entirely
* Remove PushModel.cancelAll and use actions json instead
* Remove usage of actions.yml
ESR52 still uses actions.yml but it is being treated as EOL
(Treeherder's buildbot ingestion has just been switched off).
.exists() will perform the simplest and fastest possible query to check
for existance of results. However if they do exist they're not cached
and another query must be made to retrieve the results.
To resolve the conflicting package versions (due to d3 4.x's broken
dependency structure) that was causing exceptions in the intermittent
failures view ("areas.transition is not a function").
The `resolutions` entry can be removed with the next release of
`metrics-graphics`, which will depend on d3 5.x..
Also fixes#3367.
This will allow these celery queues to drain before we remove the code
that handles them. The runnable jobs task is also buildbot-specific,
since for taskcluster the jobs are calculated via the tasks graph
instead.
The last usage of it was removed in bug 1450039. See:
https://docs.angularjs.org/api/ngResource
Since the DI arguments were already being updated, I've also removed
the configuration of `$logProvider`, since we no longer use `$log`.
CommonMark has made a breaking package change in a minor version
release (0.8.0), so we need to pin to the last working release. See:
https://github.com/rtfd/CommonMark-py/issues/134
Fixes:
```
...
File ".../recommonmark/recommonmark/parser.py", line 9, in <module>
from CommonMark import Parser
ImportError: No module named CommonMark
```
The Travis docs setup step has also been modified to always upgrade
dependencies, which will mean we will catch cases like this on Travis
next time.
This allows us to respect Celery's SoftTimeLimitExceeded to shut down
the current task while also continuing to parse further logs when other
exceptions are raised.