On my team, we've been implementing error handling in agenda jobs in one of two ways:

1. Catch the error, call job.fail(err); job.save(), return
2. Throw the error

After looking at the job processing code for the run method, I confirmed the two approaches were equivalent.

While

It's not quite clear reading the chronos doc:

https://mesos.github.io/chronos/docs/api.html#adding-a-docker-job

Mesos 0.22.0 added support for forcibly pulling the latest version of your Docker image before launching the task, and this behavior can be enabled in Chronos by adding the forcePullImage boolean to your container configuration.

Chronos will default to not doing a `docker pu

错误信息：
Step 10/16 : RUN pip3 install --upgrade pip
---> Running in 83716c526776

Collecting pip
Downloading https://files.pythonhosted.org/packages/c2/d7/90f34cb0d83a6c5631cf71dfe64cc1054598c843a92b400e55675cc2ac37/pip-18.1-py2.py3-none-any.whl (1.3MB)
Installing collected packages: pip
Found existing installation: pip 10.0.1
Uninstalling pip-10.0.1:
Successfully uninstalled

Summary

Hello,
It looks like there exists a rather convenient API call for getting the plugins list
http://MASTER_SERVER:PORT/api/app/get_categories/get_plugins/v1/?api_key=<>

Would it be possible to have it documented too in future?

I need something like below:

newCronExpression = convert (localCronExpresn,fromLocalTZ, "UTC")

Is it possible using cron-utils?

Let me give an example:

My local timezone is IST i.e. GMT+5.30.

Current local time is: 11:20 AM.

I want a job to run in 45 min of every hour.

So, my cron expression: 45 * * * *

Hence I am expecting my job to run after 25 min ( as starting time

An useful feature is about clicking on the job and seeing the job history. It shows only the previous execution

I believe there is an issue with generating the textual description for CRON expressions that contains hour-range definiton - according to the tutorial and the documentation, the hour-range is inclusive, meaning that if we put an hour definition as 10-14, the cron will also run in 14 hour (or 2PM). However, the textual description generated says between 10:00 AM and 1:00 PM, which is not

ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).

docker/compose#3633