- Service load balancers no longer exclude nodes marked unschedulable from the candidate nodes. The service load balancer exclusion label should be used instead.
  

            "description": "NodeTaintsPolicy indicates how we will treat node taints when calculating pod topology spread skew. Options are: - Honor: nodes without taints, along with tainted nodes for which the incoming pod has a toleration, are included. - Ignore: node taints are ignored. All nodes are included.\n\nIf this value is nil, the behavior is equivalent to the Ignore policy. This is a beta-level feature default enabled by the NodeInclusionPolicyInPodTopologySpread...

                                  properties:
                                    minimumRingSize:
                                      description: The minimum number of virtual nodes
                                        to use for the hash ring.
                                      minimum: 0
                                      type: integer
                                  type: object

                                  properties:
                                    minimumRingSize:
                                      description: The minimum number of virtual nodes
                                        to use for the hash ring.
                                      type: integer
                                  type: object
                                useSourceIp:

                                  properties:
                                    minimumRingSize:
                                      description: The minimum number of virtual nodes
                                        to use for the hash ring.
                                      minimum: 0
                                      type: integer
                                  type: object

*   `tf.saved_model.SaveOptions`

    * `SaveOptions` now takes a new argument called
      `experimental_debug_stripper`. When enabled, this strips the debug nodes
      from both the node defs and the function defs of the graph. Note that
      this currently only strips the `Assert` nodes from the graph and
      converts them into `NoOp`s instead.

*   `tf.data`

    * `tf.data` now has an `autotune_options.initial_parallelism` option to

        local_name: "trace_0"
      }
    }
    nodes {
      children {
        node_id: 4
        local_name: "serving_default"
      }
      user_object {
        identifier: "signature_map"
        version {
          producer: 1
          min_consumer: 1
        }
      }
    }
    nodes {
      children {
        node_id: 5
        local_name: "capture_0"

              }
            ],
            "description": "Only nodes matching the selector will be considered by the scheduler when trying to find a Node that fits a Pod when that Pod uses a ResourceClaim that has not been allocated yet.\n\nSetting this field is optional. If null, all nodes are candidates."
          }
        },
        "required": [
          "driverName"
        ],

usage, the input tensor comes directly from the user computation only when
graph_debug_mode is FULL_TENSOR (see protobuf/debug_event.proto for a
list of all the possible values of graph_debug_mode). For the other debug modes,
the input tensor should be produced by an additional op or subgraph that
computes summary information about one or more tensors.
  }];

  let arguments = (ins

		{"Timex.Errcnt", Field, 0},
		{"Timex.Esterror", Field, 0},
		{"Timex.Freq", Field, 0},
		{"Timex.Jitcnt", Field, 0},
		{"Timex.Jitter", Field, 0},
		{"Timex.Maxerror", Field, 0},
		{"Timex.Modes", Field, 0},
		{"Timex.Offset", Field, 0},
		{"Timex.Pad_cgo_0", Field, 0},
		{"Timex.Pad_cgo_1", Field, 0},
		{"Timex.Pad_cgo_2", Field, 0},
		{"Timex.Pad_cgo_3", Field, 0},