Thanks for maintaining Celery!

I had a hard time getting my CELERY_BROKER_URL to work, and finally realized I had entered an invalid password. This has also been addressed here in the Google group.

The password I had entered was `#qahrKscbW#3!HkMJg#jFcyaOR7HtK%j08

In the v1 source code, the result of the previous task in the task chain will continue to be executed as the parameter of the next task. I tried it and it really did.
The part of the document about Task chain is exactly the opposite.

In the source code

// taskSucceeded updates the task state and triggers succes

*For better global communication, please give priority to using English description, thx! *

Describe the bug
Some words are wrong and inconsistent:

1. In http://dolphinscheduler.incubator.apache.org/en-us/, "Rich Scanerios" should be "Widely Scenarios" or "Rich Scenarios"
2. In http://dolphinscheduler.incubator.apache.org/en-us/docs/user_doc/subscribe.html, http://dolphinscheduler.incub

if i create pipeline as below and try to run it:

pipe = actor.message_with_options(delay=60_000) | actor.message()
pipe.run()

the pipe will be executed immediately though.
I think, pipeline should respect message delays, so e.g. if both first message delay and pipe depay specified, they should summarize.

GM Folks,

Small favor/minor request -

For those of us running containerized processes via docker, kubernetes, etc. can we have the
.run() function added as an example to the readme.

I found myself looking through the code for this and think it may be helpful for those coming through later.

For example, see bottom of code snippet

from redis import Redis
from rq import Queue

Weave / Project Picasso focuses on CPU-bound tasks, i.e. those are non-blocking and you can throw more CPU at it to have your result faster.

For IO-bound tasks the idea was to defer to specialized libraries like asyncdispatch and Chronos that use OS primitives (epoll/IOCP/kqueue) to handle IO efficiently

Currently Activity heartbeat can only be called from Activity thread. This is quite inconvenient if people want to spawn timers and offload the heartbeat logic to the timer thread, etc.

Since heartbeat is asynchronous anyways, it does make sense to relax this requirement. So that heartbeat can be called from any thread. The caveat is that caller needs to specify other information like domainID,

I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/Coderty/runnerty/blob/master/CONTRIBUTING.

Introduce new command that read/tail error/info log

Possible read commands:

• leprechaun error-log
• leprechaun info-log

Possible tail commands:

• leprechaun tail-error-log
• leprechaun tail-info-log

These commands will try to read global error and info logs if they are specified as global. Every service can have it's own error and info log so we should include default commands in age