coanor

I do it like this: ```golang // setup prompt with a live prompt p := prompt.New(myRun, myCompleter, prompt.OptionLivePrefix(myLivePrompt), ... /* other options */) ... var multiLines []string // cache multi-lines...

To clarify the bug: If you press some ctrl+x (include left/right arrow) too faster, the bug reproduced. I have create a PR for that bug: https://github.com/c-bata/go-prompt/pull/214#issue-538907825

Maybe you have not review all the code(no enought time ;) I have [removed](https://github.com/c-bata/go-prompt/pull/214/files#diff-f1133d393010c233851b04df672ac482d6690521e0ed36a95c72b4be019f2041L23) `syscall.SetNonblock()` on `/dev/tty`, and [set the `bufCh` blocking](https://github.com/c-bata/go-prompt/pull/214/files#diff-b7a1648303c8484409e3686e87e2fceca1f254805b9c467125a84a301772c4c6R58). No cpu 100%, I have tested it on...

We haven't build datakit within docker before, this may need some debugging. BTW, while runner under docker, we recommend do not using the installer to install datakit, current installer will...

datakit 自身带了 HTTP 服务，具体配置在 conf.d/datakit.conf 中。此处只是注册了路由。

技术上现在是可以支持 otel-> Jaeger (HTTP)-> datakit 的，不过我们自己还未测试这一块。 在 datakit 上，只需要开启对应的采集器即可，不用配置 HTTP。 后续我们会直接支持 otel 打过来的数据（无需借助 zipkin/jaeger 等）。 希望能帮到您。

so, this still a bug?

Need the feature for large document repository. JSON is pretty，current output format hard to parse using simple grep/sed/awk skills. The following shell would extract 404 errors, but not precisely get...

> 容器日志级别调整到debug，还是看不到更多信息  默认情况下，日志是输出到容器内部的 */var/log/datakit/log* 中。

> datakit debug --prom-conf prom.conf 从截图看，采集器已经可以采集到数据了，可以用 `datakit monitor -V` 看下，它会展示更多的可观测数据以定位具体问题。