It would be beneficial to write a design document on INT8 DNNL implementation and put it into
FluidDoc next to other Design documents:
https://github.com/PaddlePaddle/FluidDoc/tree/develop/doc/fluid/design/mkldnn

There is a document on the subject, but it's lacking in a few ways:

• It does not state what exactly the default placement strategy is.
• It does not state whether one can override the default strategy for all grains.
• It does not explain how each of the built-in strategies work ([random, prefer local,

Based on feedback we collected Centrifugo docs are not complete and hard to understand for beginner developers.

I think it's obvious that we need to improve things here. Since I wrote it myself my vision is a bit blurred and I want to understand what are the main weak points of current docs. Will appreciate help with this.

In the Cloud-native K8S environment, the logging architecture almost always assumes that all needed logs are sent to the stdout. It works as a unified source of logs where different tools read them, re-organize if needed, and route to the destinations like Analytics Dashboards etc.

Hazelcast Diagnostics are very useful when troubleshooting the performance and stability issues but currently, it

Describe the bug
vmagent with sd_k8s

To Reproduce
Start vmagent with config:

    - job_name: 'kubernetes-pods'
      kubernetes_sd_configs:
      - role: pod

on a cluster with many pods.

Please add pod name to error log.

It's hard to find them in a big cluster. In a message like this it's not clear what was the pod.

2020-04-15T22:32:32.512Z	error	Victor

Adding links to guides like Node best practices or from RisingStack blog to README seems like a good way to recommend what works well with the app architecture.

Currently understanding what's going on when using the first time the framework is quite complex (at least from my point of view ;)).

Would it be possible to add some debug/trace logging during the configuration/bootstrap phase of Axon in order to get insight on what was configured and instantiated.

For example I added a TrackingEventProcessor in my configuration but it was never started

The readme features basic documentation for Sockends, and doesn't give a complete example for how and why it works. Therefore we need more detailed documentation in the readme. Certain things like simple security mechanisms via respondsTo and broadcasts configurations should also be taken into account.

Context 🕵️‍♀️

I came across a website that had the timeline of their Twitter account embedded, and I think that's something we could have too in our website. After a bit of search, I came across this React component to do exactly that.

What

Add a new section where we show both, the tweets posted by Tuist, as well as the mentions that

Not sure if it's worth adding to the documentation but I found I had to add the following to the end of the fstab command otherwise the system would not boot cleanly.

,x-systemd.mount-timeout=30,_netdev

The line in fstab now looks like

mfsmount /mnt/mymnt fuse mfssubfolder=mydir,allow_other,x-systemd.mount-timeout=30,_netdev

I think it was trying to mount mooseFS before it had fini

there are a lot of work need to about the documentation.

需求描述：

1. 我们要找到yiqi。
2. 按照教程跑通 https://github.com/AElfProject/aelf-boilerplate/tree/hello-world
3. 跑通后和yiqi一天喝八杯可乐。
4. 成为yiqi的朋友。

奖励：

奖励 58.88个 ELF 【不同的issue的奖励不一样，最后以和团队确认为准】

Apologies for probably opening this issue in the wrong repo.

https://vertx.io/docs/vertx-pg-client/kotlin/#_handling_arrays

Shows this example query:

client.preparedQuery("SELECT address, (address).city FROM address_book WHERE id=\$$1", Tuple.of(3), { ar ->
....

The \$$1 is not valid Postgres SQL and will throw an Exception. The Java version correctly uses $1.

After rewriting a 4000 word manual for Porter v4 I didn't really feel like writing about FetchExceptionHandlers. This feature will seldom be required, and for those whom do need it, if they can't figure it out for themselves, the docblocks in the file should probably suffice. Nevertheless, we should document the interface properly at some point.

The button "Suggest improvements" on the webpage https://www.reactivemanifesto.org/cz wrongly navigates to https://github.com/reactivemanifesto/reactivemanifesto/blob/master/README.cz.md instead of https://github.com/reactivemanifesto/reactivemanifesto/blob/master/README.cs.md

Suggested fix:

• change cz to cs

infinit user pull       
Remotely deleted identity for user "bushbaby123".

not sure if it actually deleted the user, but this does not sound correct

v0.8.0

In the API HTML documentation: The example urls currently have the .erl suffix. This needs to change to a .json suffix and example request/response data should be added below.

The Quickstart (in HTML/Markdown) needs to be updated, the Java tutorial, and possibly the FAQ.

The file src/service_api/README.markdown needs to be updated.