Please make sure that this is a documentation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:doc_template

System information

• TensorFlow version: 1.13.1
• Doc Link: https://www.tensorflow.org/api_docs/python/tf/cus

What is the problem?

(base) ray/python % serve start --http-host 0.0.0.
File descriptor limit 256 is too low for production servers and may result in connection errors. At least 8192 is recommended. --- Fix with 'ulimit -n 8192'
2020-12-10 18:50:14,006 INFO worker.py:653 -- Connecting to existi

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

How you are using LightGBM?

LightGBM component: R package

Environment info

Operating System: macOS 10.14

C++ compiler version: gcc 8.1.0

CMake version: 3.17.3

R version: 4.0.2

LightGBM version or commit hash: https://github.com/microsoft/LightGBM/tree/c07644d1d71540204a9b56f26667e8180bd009e2

Reproducible example(s)

Thanks to @Laurae2 for sharing this with m

What would you like to be added: As title

Why is this needed: All pruning schedule except AGPPruner only support level, L1, L2. While there are FPGM, APoZ, MeanActivation and Taylor, it would be much better if we can choose any pruner with any pruning schedule.

**Without this feature, how does current nni

• Support multi vid_ref_expression in from clause.
• Support uuid in where clause.

issue from vesoft-inc/nebula-java#81

Forking ipfs/js-ipfs#3252 (comment) into separate issue.

Looks like some of our API calls return values that refer to same ArrayBuffer, which in turn causes one of the encoder functions https://github.com/ipfs/js-ipfs/tree/master/packages/ipfs-message-port-protocol/src to add it to the transfer list twice and error on postMessage.

We have added default serializers to the 4.2 series here:
hazelcast/hazelcast#17934

There is a problem with backward compatibility. If a user had CustomSerializer for optional in 4.1, in 4.2 there is no way to use their serializers, and Hazelcast will throw java.lang.IllegalArgumentException: [class java.util.Optional] serializer cannot be overridden

Users can basi

See optuna/optuna#1913.

Some type hints are not complying to the latest mypy == 0.790 and should be addressed.

In osx/updater/updater.go, we're referencing an ancient Go package, which has moved to a new location. Right now, the updater doesn't build (should we test this on travis?).

I've noticed that some files have conflicting license statements. For instance the header of file scripts/ZoneMinder/lib/ZoneMinder/Trigger/Channel.pm claims GPL-2+ but in the end of the same file I found the following statement:

This library is free

We should remove Guava as a dependency from the server module.

Most of the functionality we used from Guava are provided by the JDK by now.
The stuff that is missing from the JDK has mostly been added in the utilities we inherited from Elasticsearch, due to their decision to remove Guava completely.
Any functionality that we use which isn't present in the JDK can be co