Hi folks, sory about my bad english.
I'm trying get up nsq services at containerum, at containerum the public port to services and container are random. With nsqlookupd and nsqadmin it's easy not a big trouble.
But when we try to run nsqd it's registrer ther right broadcast url but the follow ports that nsqd register is that expose in container and not the service port random assigned with the

• This item located in 2.3. 常用设置 and 2.3. Common settings.It would an effect to cause chinese user confused.Please update it.

![image](https://user-images.githubusercontent.com/26212551/68575

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

From: https://boltons.readthedocs.io/en/latest/setutils.html#boltons.setutils.IndexedSet

As you can see, the IndexedSet is almost like a UniqueList, retaining only one copy of a given value, in the order it was first added.

This appears incorrect. Perhaps it is a remnant from an earlier version of the library?

Currently if machinery is misconfigured for the connection to AMQP it will run indefinitely at a exponential backoff. It will be easier for users to detect failure in a production application if the application is allowed to exit out on failures that are not likely going to be recoverable.

Trying to build under ubuntu 16.04 with go 1.10.1, and following the building instructions:

root@builder:~# go get github.com/travisjeffery/jocko
package github.com/travisjeffery/jocko: no Go files in /root/go/src/github.com/travisjeffery/jocko
root@builder:~# cd go/src/github.com/travisjeffery/jocko/
root@builder:~/go/src/github.com/tr

in elif ACL_WINDOWS

lib_acl/src/net/acl_vstream_net.c
line 117

@@ -114,7 +114,7 @@ ACL_VSTREAM *acl_vstream_accept_ex(ACL_VSTREAM *sstream,
                connfd = acl_accept(servfd, buf, sizeof(buf), NULL);
        } else if (sstream->iocp_sock == ACL_SOCKET_INVALID) {
                return NULL;
-       else {
+       } else {
                int   ret;

                co

Ahoy 🚢

The carryoverConcurrencyCount option could use some more verbose documentation. In toying with the package, it's not entirely clear what option value produce what behavior.

Perhaps even an examples directory that covered how this works?

I've read the docs, and it seems you can pass through knex instances, but I didn't see if it supports SQLite3 - could you clarify please?

Right now all the documentation for this library is in README.md. It's getting pretty unwieldy at this point, and should really probably be moved into a hosted page somewhere.

I've used readthedocs.org before, and it works pretty well. We'll have to refactor the README documentation into sphinx documentation first, but that shouldn't be too tricky.

Tasks:

• refactor documentation in

I'm sure many potential plugin users would like to know which browsers we can count on with this plugin before getting hours into implementation. The suggestion of "modern browsers" could mean many things. From reading the source, I can see that you are ruling out old versions of Android, Zune, Kindle and Windows Phone. How does IE fair?

I have error when try delay 30 days in AMQP Interop driver and enqueue/amqp-bunny transport
and rabbit with installed RabbitMQ Delayed Message Plugin. After inspect code and documentation i discover what rabbitmq delayed message plugin max delay is 2^32 milliseconds (~50 days) and bunny have limit for headers 2^31 milliseconds (~25 days)

Architecture as well as workflows tend to be very complex within the appserver.io environment.
We need diagrams for better documentation and overview of architecture and request/response flow.

UAC:

• There MUST be workflow diagrams showing the request/response flow
• Diagrams MUST illustrate the difference in between servlet requests and legacy ones
• There MUST be architectural diagrams
• At lea

As interface shows below：

    /**
     * <p>
     * Send batch messages to server.
     *
     * @param messages messages to be sent.
     */
    void send(List<Message> messages);

This API can lead to multiple behaviors, such as sending to multiple partitions, or the same partition, so how should we define the behavior of this method?

And this issue exists in many places, suc