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搭建监控环境，如果有图文，更容易理解．

The docs for Symfony Bundle should be more explicit about extension tags when using different consume commands. I'm referring to https://php-enqueue.github.io/bundle/consumption_extension/#consumption-extension

When using the "enqueue:transport:consume" command a consumption extension needs to be registered with the tag enqueue.transport.consumption_extension (while docs currently only mentio

The documentation generator at ./docs/generator/ could support the config struct tags introduced in trivago/gollum#143 to:

• Detect undocumented configuration parameters and include them in the documentation
• Detetect and warn about inexistent / mistyped configuration parameters found in the doc comments

Not a very urgent need, but perhaps useful when revising do

following this example
https://github.com/pardahlman/RawRabbit/blob/2.0/docs/operations/publish.md
with RawRabbit.Operations.Publish installed as it says in the 2.0 docs

var message = new BasicMessage { Prop = "Hello, world!" };

await busClient.PublishAsync(message, ctx => ctx
    .UsePublishConfiguration(cfg => cfg
        .OnDeclaredExchange(e => e
            .WithName("my_topic"

mini-toastr has a webpack compile issue that will sometime throw a webpackjasonp is undefined in certain browsers (like internet explorer) see : se-panfilov/mini-toastr#128 there is a temporary solution, but would be nice to make note of in documentation somewhere since it is a suggested package, or offer additional package suggestions.

I can't seem to figure out how to pass it the proper options to get the Delayed Message Plugin to work properly when using servicebus.

My current attempt is as follows:

Consumer:

  const options = {
      ack: true,
      queueOptions: {
        exchangeOptions: {
          type: 'x-delayed-message',
          'x

In the README, since #2298, there has been this wording:

If the above configuration file is being used as a basis, be sure to update it with the hostname of the deployment (this should be the fully qualified domain name of the system).

Yet, in the walk-through for [how to authenticate an agent to communicate with VOLTTRON platform](https://volttron.readthedocs.io/en/develop/devguides/walk

It would be good to run (libFuzzer)[https://llvm.org/docs/LibFuzzer.html] or (AFL)[http://lcamtuf.coredump.cx/afl/] on the NATS parser to make sure that no invalid inputs can cause buffer overflows.

As the documentation states, a MSG has a CR+LF after the payload:
MSG [reply-to] <#bytes>\r\n[payload]\r\n

The handleMSG method only reads the payload and leaves the trailing \r\n in the socket buffer.
I understand that this is not much of a problem, because Connection::wait just ignores such empty lines, but in my case

Hello, I think you should 'utf-8' decode the signature here:

https://github.com/fedora-infra/fedmsg/blob/develop/fedmsg/crypto/gpg.py#L177