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

Currently the decorator docstring is good but not the one for the resulting Deployment type.

Should also be able to do Deployment.num_replicas to check current setting and so on. We should document these in the docstring.

Migrate all Python code from old-fashioned format() functions, formatting % operators and simple concatenations (+) to modern f-strings (brief guide). They are known to be the fastest approach and also increase code readability.

![image](https://user-images.githubusercontent.com/25141164/112898582-a

I'm using mxnet to do some work, but there is nothing when I search the mxnet trial and example.

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

issue from vesoft-inc/nebula-java#81

Motivation

Test cases in tests/pruners_tests/*.py can be simpler using should_prune and the ask-and-tell interface. e.g. optuna/optuna#2644

Description

• test_hyperband.py
• test_median.py
• test_nop.py
• test_percentile.py
• test_successive_halving.py

There is no technical difficulty to support includeValue option, looks like we are just missing it on the API level.

See SO question

For classes declared with struct, forward declarations should also use struct. Currently, only struct Message violates this in a few header files (2 or so?).

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

Use case:
Right now one can only use date_trunc() to easily define time buckets. date_trunc() only supports predefine time intervals like 1 minute, 1 hour, etc. . In time-series use cases it is often necessary to define different time bucket sizes like e.g. '5 minutes' or '20 minutes'

a workaround for this is the - error prone - integer division on the timestamp e.g.

S

The getDataObject function is remaining public on RootDataObject that needs to be remove. It can simply be removed.

https://github.com/microsoft/FluidFramework/blob/main/experimental/framework/fluid-static/src/containerCode.ts