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

System information

• Have I written custom code (as opposed to using a stock
  example script provided in TensorFlow): Yes

Describe your feature request

It is already possible to give actors a name: https://docs.ray.io/en/master/actors.html#named-actors and to retrieve the actor handle via ray.get_actor("some_name").
It would however be very handy to have some kind of ray.list_named_actors() API method to get a list/dict of all currently available named actors.
It can be useful for:

• Better debugging

The ability to set the language on the user creation form could be something useful on a multi user environment.

Summary

Today in the R package, there are a lot of internal function calls which use only positional arguments. Change them to use keyword arguments for extra safety.

I've added this issue to provide a small, focused contribution opportunity for Hacktoberfest 2020 participants. If you are an experienced open source contributor, please leave this

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

In some cases, the default implementations are very inefficient (e.g. Map.replaceAll and forEach fetching all entries and iterating over them locally). This was improved on member-side as the cluster version is available and in some cases we opted for using entry processors instead.

On the client-side, the cluster version is not available which meant it ends up still using the default versi

Motivation

From following resources, the search space of examples/xgboost_simple.py seems not to be practical.

• https://www.analyticsvidhya.com/blog/2016/03/complete-guide-parameter-tuning-xgboost-with-codes-python/
• https://www.youtube.com/watch?v=VC8Jc9_lNoY
• https://www.amazon.co.jp/dp/B07YTDBC3Z/

Description

Improve the search space of examples/xgboost_simple.py.

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

Currently sum aggregations on numeric columns of type REAL or DOUBLE PRECISION uses a straight forward x + y operation (Double::sum).

SELECT sum(real_column) FROM tbl

There would be the [Kahan summation algorithm](https