英雄招募

成为 Doocs 项目维护者

本项目 advanced-java，包括 Doocs 开源组织下的所有项目，都欢迎各位朋友参与完善。

如果你提交的内容有价值，且具备规范性，将有机会提升为项目的维护者，直接参与项目的 review、merge 等维护工作，提交内容时也可以直接 push 到 doocs/advanced-java 主分支 master 下，无须提交 PR 等待 review。

目前 advanced-java 只有 [yanglbme](http

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

See nats-io/nats-server#944. I spent a couple of hours debugging this issue and believe that it probably should be documented in README (if I've understood things correctly).

We use http_server as input and http_client as one of outputs (for a part of message batch). In case when there is some error coming from http_client, benthos starts to retry this error message indefinitely (#415). However most significant, is that it stops accepting other, normal messages.

Here is the log when I first try to send message which causes http_client to get 500 error, and

我看到可以通过Prometheus搭建监控环境，如果有图文，更容易理解．

In commit: celery/kombu@5780f1e
support for queues already defined in Amazon SQS was added.

However, simply by following the instructions at https://docs.celeryproject.org/en/latest/getting-started/brokers/sqs.html and Getting Started page, I must say that I'm still not able to process any message (it's not an issue with credentials or

When the queue workers are restarted (using supervisor), all delayed messages are instantly triggered, regardless of the remaining delay.
This happens when using either rabbitmq_dlx or rabbitmq_delay_plugin delay strategy.

Implemented via laravel-queue with amqp+rabbitmq dsn.

Is your feature request related to a problem? Please describe.
WeEvent在线文档里，现有的注意&注解等部分的内容提醒的不是明显。应该用更明显的格式。
例如：
注意是这样的：

说明是类似这样的：

**Describe the solution you'd like

The operator should deploy a replica set instead of single pods as it's a bad practice to run individual pods in Kubernetes, even singleton pods.

Ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/#working-with-pods

We're currently having issues with some of our builds that still rely on fairly old versions of akka-rabbitmq

sbt.ResolveException: unresolved dependency: com.thenewmotion.akka#akka-rabbitmq_2.11;2.3: not found

even though we have the resolver configured to use the newmotion Nexus in our build.sbts:

resolvers += "New Motion Repository" at "http://nexus.thenewmotion.com/conten