I see a lot of fd users that seem to think that they need to add "{}" to all commands. Some users also seem to think that the closing semicolon (which needs to be escaped) \; is required:

fd … -x command "{}" \;

In reality, 90% of the --exec use cases can be written without the "{}" part (which fd adds, if it is ommitted) because the file entry often comes last. The semic

Google suggests enabling gzip compression before transferring files over the network:

In order to receive a gzip-encoded response you must do two things: Set an Accept-Encoding header, and modify your user agent to contain the string gzip. Here is an example of properly formed HTTP headers for enabling gzip compression:

Acc

I am working on adding an ARM64 job in Travis. ARM64 job is failing as docker image chubaofs/cfs-base:1.1 is not available for arm64.

Please check https://travis-ci.org/github/odidev/chubaofs/jobs/713238554 for the same.

I have built ARM64 binaries in ARM64 platform using below steps:

• Removed -Werror flag from rocksdb Makefile as deprecated warnings are being treated as errors.