I am trying to deploy the app with the given ./sbt clean dist command but I got this error:

Downloading sbt launcher for 1.3.8:
  From  https://repo.scala-sbt.org/scalasbt/maven-releases/org/scala-sbt/sbt-launch/1.3.8/sbt-launch-1.3.8.jar
    To  /root/.sbt/launchers/1.3.8/sbt-launch.jar
Downloading sbt launcher 1.3.8 md5 hash:
  From  https://repo.scala-sbt.org/scalasbt/maven-releas

The sarama package documentation doesn't clarify when Broker.Close is expected to be called, and usage in the code doesn't make it clear either.

For example, here's a Client method in the code that sometimes closes the returned broker

The official Widgets Development Guide only contains the most basic widget types as example.

There is no functional example for a Flot chart in there right now. Or is it?

Since this is one of the most useful and probably used (at leat to me) widgets it would be very helpful to extend that docum

Bug report

General Information

• Cilium version: 1.7.2
• Kernel version: 5.6.6
• Orchestration system version: Kubernetes 1.18.2

I'm using terraform to spool and deploy kubeadm on AWS.

How to reproduce the issue

The issues is that if the Cloud Controller Manager is not brought up before Cilium the node is brought, and the operator starts running ENIs will be attached t

Checklist

• I have included information about relevant versions
• I have verified that the issue persists when using the master branch of Faust.

Steps to reproduce

Given one Faust Table, two topic Agents:

partition_no = 4

topic_1 = app.topic('topic_1', partitions=partition_no, internal=True)
topic_2 = app.topic('topic_1', key_type=str, value_type=InfoDetai

Description

I'd like to be able to use negative lookaheads within the topic blacklist regex.

I looked into the librdkafka source, and it seems the header-only regex library that is bundled (from https://github.com/ccxvii/minilibs ) supports negative lookaheads (see [0]) , but during the build process, librdkafka first checks if libc's regex support exists and uses that instead of t

  File "/root/miniconda3/bin/pipeline", line 11, in <module>
    sys.exit(_main())
  File "/root/miniconda3/lib/python3.7/site-packages/cli_pipeline/cli_pipeline.py", line 5734, in _main
    _fire.Fire()
  File "/root/miniconda3/lib/python3.7/site-packages/fire/core.py", line 127, in Fire
    component_trace = _Fire(component, args, context, name)
  Fil

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

The namedtuples in kafka.struct package need to be documented, as they are the parameters or return values of some Apis.

如下：

databaseChangeLog:
  - changeSet: # 对应一个 ChangeSet 对象
      id: 0 # ChangeSet 编号
      author: calm # 作者
      comment: 空 # 备注

评论的属性是 comment，而不是comments，虽然表DATABASECHANGELOG 中相应的字段叫COMMENTS，正常的记录效果如下：

Is your feature request related to a problem? Please describe.

If I have a schema that is in schema registry but is not under the correct subject name, I cannot specify my KSQL stream to use that topic with AVRO format.

Describe the solution you'd like
We should support specifying AVRO_SCHEMA_ID in the WITH clause of create statements.

**Describe alternatives you've consider

Whether the input is Go code and the output is Swagger Spec
Or whether the input is Swagger Spec and the output is Go Code

API documentation should be locked with the API implementation so that the documentation never goes stale.

Code was added in #277, but the README wasn't updated to document the new functionality.

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

Currently, you are not able to use middleware per handler in "clean way" (you can still manually wrap the handler function, or have separated router).

It would be nice to be able to add middleware per handler.

As a good reference point, you can use chi router: https://github.com/go-chi/chi

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.

Compacted topics require keys when producing. If you forget to specify a key, the Kafka CLI tool kafka-console-producer returns a helpful error within a few seconds:

CorruptRecordException: This message has failed its CRC checksum, exceeds the valid size, has a null key for a compacted topic, or is otherwise corrupt.

If you forget to specify a key with POST /topics/(string:topic_name), tho