CalvinBackup/DeepFaceLab_MacOS
1
0
Fork 0
Code Issues 21 Pull Requests 8 Actions Packages Projects Releases 2 Wiki Activity

Bump tensorflow from 2.6.0 to 2.6.1 #53

Merged
dependabot[bot] merged 1 commits from dependabot-pip-tensorflow-2.7.0 into master 2021-11-12 00:17:33 +01:00
Conversation 2 Commits 1 Files Changed 3
+3 -3
dependabot[bot] commented 2021-11-10 23:01:48 +01:00 (Migrated from github.com)
Copy Link
Copy Source

Bumps tensorflow from 2.6.0 to 2.7.0.

Release notes

Sourced from tensorflow's releases.

TensorFlow 2.7.0

Release 2.7.0

Breaking Changes

  • tf.keras:

    • The methods Model.fit(), Model.predict(), and Model.evaluate() will no longer uprank input data of shape (batch_size,) to become (batch_size, 1). This enables Model subclasses to process scalar data in their train_step()/test_step()/predict_step() methods.
      Note that this change may break certain subclassed models. You can revert back to the previous behavior by adding upranking yourself in the train_step()/test_step()/predict_step() methods, e.g. if x.shape.rank == 1: x = tf.expand_dims(x, axis=-1). Functional models as well as Sequential models built with an explicit input shape are not affected.
    • The methods Model.to_yaml() and keras.models.model_from_yaml have been replaced to raise a RuntimeError as they can be abused to cause arbitrary code execution. It is recommended to use JSON serialization instead of YAML, or, a better alternative, serialize to H5.
    • LinearModel and WideDeepModel are moved to the tf.compat.v1.keras.models. namespace (tf.compat.v1.keras.models.LinearModel and tf.compat.v1.keras.models.WideDeepModel), and their experimental endpoints (tf.keras.experimental.models.LinearModel and tf.keras.experimental.models.WideDeepModel) are being deprecated.
    • RNG behavior change for all tf.keras.initializers classes. For any class constructed with a fixed seed, it will no longer generate same value when invoked multiple times. Instead, it will return different value, but a determinisitic sequence. This change will make the initialize behavior align between v1 and v2.

  • tf.lite:

    • Rename fields SignatureDef table in schema to maximize the parity with TF SavedModel's Signature concept.
    • Deprecate Makefile builds. Makefile users need to migrate their builds to CMake or Bazel. Please refer to the Build TensorFlow Lite with CMake and Build TensorFlow Lite for ARM boards for the migration.
    • Deprecate tflite::OpResolver::GetDelegates. The list returned by TfLite's BuiltinOpResolver::GetDelegates is now always empty. Instead, recommend using new method tflite::OpResolver::GetDelegateCreators in order to achieve lazy initialization on TfLite delegate instances.

  • TF Core:

    • tf.Graph.get_name_scope() now always returns a string, as documented. Previously, when called within name_scope("") or name_scope(None) contexts, it returned None; now it returns the empty string.
    • tensorflow/core/ir/ contains a new MLIR-based Graph dialect that is isomorphic to GraphDef and will be used to replace GraphDef-based (e.g., Grappler) optimizations.
    • Deprecated and removed attrs() function in shape inference. All attributes should be queried by name now (rather than range returned) to enable changing the underlying storage there.
    • The following Python symbols were accidentally added in earlier versions of TensorFlow and now are removed. Each symbol has a replacement that should be used instead, but note the replacement's argument names are different.
      • tf.quantize_and_dequantize_v4 (accidentally introduced in TensorFlow 2.4): Use tf.quantization.quantize_and_dequantize_v2 instead.
      • tf.batch_mat_mul_v3 (accidentally introduced in TensorFlow 2.6): Use tf.linalg.matmul instead.
      • tf.sparse_segment_sum_grad (accidentally introduced in TensorFlow 2.6): Use tf.raw_ops.SparseSegmentSumGrad instead. Directly calling this op is typically not necessary, as it is automatically used when computing the gradient of tf.sparse.segment_sum.
    • Renaming of tensorflow::int64 to int_64_t in numerous places (the former is an alias for the latter) which could result in needing to regenerate selective op registration headers else execution would fail with unregistered kernels error.

  • Modular File System Migration:

    • Support for S3 and HDFS file systems has been migrated to a modular file systems based approach and is now available in https://github.com/tensorflow/io. The tensorflow-io python package should be installed for S3 and HDFS support with tensorflow.

Major Features and Improvements

  • Improvements to the TensorFlow debugging experience:

    • Previously, TensorFlow error stack traces involved many internal frames, which could be challenging to read through, while not being actionable for end users. As of TF 2.7, TensorFlow filters internal frames in most errors that it raises, to keep stack traces short, readable, and focused on what's actionable for end users (their own code).

      This behavior can be disabled by calling tf.debugging.disable_traceback_filtering(), and can be re-enabled via tf.debugging.enable_traceback_filtering(). If you are debugging a TensorFlow-internal issue (e.g. to prepare a TensorFlow PR), make sure to disable traceback filtering. You can check whether this feature is currently enabled by calling tf.debugging.is_traceback_filtering_enabled().

      Note that this feature is only available with Python 3.7 or higher.

    • Improve the informativeness of error messages raised by Keras Layer.__call__(), by adding the full list of argument values passed to the layer in every exception.

  • Introduce the tf.compat.v1.keras.utils.track_tf1_style_variables decorator, which enables using large classes of tf1-style variable_scope, get_variable, and compat.v1.layer-based components from within TF2 models running with TF2 behavior enabled.

  • tf.data:

    • tf.data service now supports auto-sharding. Users specify the sharding policy with tf.data.experimental.service.ShardingPolicy enum. It can be one of OFF (equivalent to today's "parallel_epochs" mode), DYNAMIC (equivalent to today's "distributed_epoch" mode), or one of the static sharding policies: FILE, DATA, FILE_OR_DATA, or HINT (corresponding to values of tf.data.experimental.AutoShardPolicy).

      Static sharding (auto-sharding) requires the number of tf.data service workers be fixed. Users need to specify the worker addresses in tensorflow.data.experimental.DispatcherConfig.

    • tf.data.experimental.service.register_dataset now accepts optional compression argument.

  • Keras:

... (truncated)

Changelog

Sourced from tensorflow's changelog.

Release 2.7.0

Breaking Changes

  • tf.keras:

    • The methods Model.fit(), Model.predict(), and Model.evaluate() will no longer uprank input data of shape (batch_size,) to become (batch_size, 1). This enables Model subclasses to process scalar data in their train_step()/test_step()/predict_step() methods.
      Note that this change may break certain subclassed models. You can revert back to the previous behavior by adding upranking yourself in the train_step()/test_step()/predict_step() methods, e.g. if x.shape.rank == 1: x = tf.expand_dims(x, axis=-1). Functional models as well as Sequential models built with an explicit input shape are not affected.
    • The methods Model.to_yaml() and keras.models.model_from_yaml have been replaced to raise a RuntimeError as they can be abused to cause arbitrary code execution. It is recommended to use JSON serialization instead of YAML, or, a better alternative, serialize to H5.
    • LinearModel and WideDeepModel are moved to the tf.compat.v1.keras.models. namespace (tf.compat.v1.keras.models.LinearModel and tf.compat.v1.keras.models.WideDeepModel), and their experimental endpoints (tf.keras.experimental.models.LinearModel and tf.keras.experimental.models.WideDeepModel) are being deprecated.
    • RNG behavior change for all tf.keras.initializers classes. For any class constructed with a fixed seed, it will no longer generate same value when invoked multiple times. Instead, it will return different value, but a determinisitic sequence. This change will make the initialize behavior align between v1 and v2.

  • tf.lite:

    • Rename fields SignatureDef table in schema to maximize the parity with TF SavedModel's Signature concept.
    • Deprecate Makefile builds. Makefile users need to migrate their builds to CMake or Bazel. Please refer to the Build TensorFlow Lite with CMake and Build TensorFlow Lite for ARM boards for the migration.
    • Deprecate tflite::OpResolver::GetDelegates. The list returned by TfLite's BuiltinOpResolver::GetDelegates is now always empty. Instead, recommend using new method tflite::OpResolver::GetDelegateCreators in order to achieve lazy initialization on TfLite delegate instances.

  • TF Core:

    • tf.Graph.get_name_scope() now always returns a string, as documented. Previously, when called within name_scope("") or name_scope(None) contexts, it returned None; now it returns the empty string.
    • tensorflow/core/ir/ contains a new MLIR-based Graph dialect that is isomorphic to GraphDef and will be used to replace GraphDef-based (e.g., Grappler) optimizations.
    • Deprecated and removed attrs() function in shape inference. All attributes should be queried by name now (rather than range returned) to enable changing the underlying storage there.
    • The following Python symbols were accidentally added in earlier versions of TensorFlow and now are removed. Each symbol has a replacement that should be used instead, but note the replacement's argument names are different.
      • tf.quantize_and_dequantize_v4 (accidentally introduced in TensorFlow 2.4): Use tf.quantization.quantize_and_dequantize_v2 instead.
      • tf.batch_mat_mul_v3 (accidentally introduced in TensorFlow 2.6): Use tf.linalg.matmul instead.
      • tf.sparse_segment_sum_grad (accidentally introduced in TensorFlow 2.6): Use tf.raw_ops.SparseSegmentSumGrad instead. Directly calling this op is typically not necessary, as it is automatically used when computing the gradient of tf.sparse.segment_sum.
    • Renaming of tensorflow::int64 to int_64_t in numerous places (the former is an alias for the latter) which could result in needing to regenerate selective op registration headers else execution would fail with unregistered kernels error.

  • Modular File System Migration:

    • Support for S3 and HDFS file systems has been migrated to a modular file systems based approach and is now available in https://github.com/tensorflow/io. The tensorflow-io python package should be installed for S3 and HDFS support with tensorflow.

Major Features and Improvements

  • Improvements to the TensorFlow debugging experience:

    • Previously, TensorFlow error stack traces involved many internal frames, which could be challenging to read through, while not being actionable for end users. As of TF 2.7, TensorFlow filters internal frames in most errors that it raises, to keep stack traces short, readable, and focused on what's actionable for end users (their own code).

      This behavior can be disabled by calling tf.debugging.disable_traceback_filtering(), and can be re-enabled via tf.debugging.enable_traceback_filtering(). If you are debugging a TensorFlow-internal issue (e.g. to prepare a TensorFlow PR), make sure to disable traceback filtering. You can check whether this feature is currently enabled by calling tf.debugging.is_traceback_filtering_enabled().

      Note that this feature is only available with Python 3.7 or higher.

    • Improve the informativeness of error messages raised by Keras Layer.__call__(), by adding the full list of argument values passed to the layer in every exception.

  • Introduce the tf.compat.v1.keras.utils.track_tf1_style_variables decorator, which enables using large classes of tf1-style variable_scope, get_variable, and compat.v1.layer-based components from within TF2 models running with TF2 behavior enabled.

  • tf.data:

    • tf.data service now supports auto-sharding. Users specify the sharding policy with tf.data.experimental.service.ShardingPolicy enum. It can be one of OFF (equivalent to today's "parallel_epochs" mode), DYNAMIC (equivalent to today's "distributed_epoch" mode), or one of the static sharding policies: FILE, DATA, FILE_OR_DATA, or HINT (corresponding to values of tf.data.experimental.AutoShardPolicy).

      Static sharding (auto-sharding) requires the number of tf.data service workers be fixed. Users need to specify the worker addresses in tensorflow.data.experimental.DispatcherConfig.

    • tf.data.experimental.service.register_dataset now accepts optional compression argument.

  • Keras:

    • tf.keras.layers.Conv now includes a public convolution_op method. This method can be used to simplify the implementation of Conv subclasses. There are two primary ways to use this new method. The first is to use the method directly in your own call method:

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps [tensorflow](https://github.com/tensorflow/tensorflow) from 2.6.0 to 2.7.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tensorflow/tensorflow/releases">tensorflow's releases</a>.</em></p> <blockquote> <h2>TensorFlow 2.7.0</h2> <h1>Release 2.7.0</h1> <h2>Breaking Changes</h2> <ul> <li> <p><code>tf.keras</code>:</p> <ul> <li>The methods <code>Model.fit()</code>, <code>Model.predict()</code>, and <code>Model.evaluate()</code> will no longer uprank input data of shape <code>(batch_size,)</code> to become <code>(batch_size, 1)</code>. This enables <code>Model</code> subclasses to process scalar data in their <code>train_step()</code>/<code>test_step()</code>/<code>predict_step()</code> methods.<br /> Note that this change may break certain subclassed models. You can revert back to the previous behavior by adding upranking yourself in the <code>train_step()</code>/<code>test_step()</code>/<code>predict_step()</code> methods, e.g. <code>if x.shape.rank == 1: x = tf.expand_dims(x, axis=-1)</code>. Functional models as well as Sequential models built with an explicit input shape are not affected.</li> <li>The methods <code>Model.to_yaml()</code> and <code>keras.models.model_from_yaml</code> have been replaced to raise a <code>RuntimeError</code> as they can be abused to cause arbitrary code execution. It is recommended to use JSON serialization instead of YAML, or, a better alternative, serialize to H5.</li> <li><code>LinearModel</code> and <code>WideDeepModel</code> are moved to the <code>tf.compat.v1.keras.models.</code> namespace (<code>tf.compat.v1.keras.models.LinearModel</code> and <code>tf.compat.v1.keras.models.WideDeepModel</code>), and their <code>experimental</code> endpoints (<code>tf.keras.experimental.models.LinearModel</code> and <code>tf.keras.experimental.models.WideDeepModel</code>) are being deprecated.</li> <li>RNG behavior change for all <code>tf.keras.initializers</code> classes. For any class constructed with a fixed seed, it will no longer generate same value when invoked multiple times. Instead, it will return different value, but a determinisitic sequence. This change will make the initialize behavior align between v1 and v2.</li> </ul> </li> <li> <p><code>tf.lite</code>:</p> <ul> <li>Rename fields <code>SignatureDef</code> table in schema to maximize the parity with TF SavedModel's Signature concept.</li> <li>Deprecate Makefile builds. Makefile users need to migrate their builds to CMake or Bazel. Please refer to the <a href="https://www.tensorflow.org/lite/guide/build_cmake">Build TensorFlow Lite with CMake</a> and <a href="https://www.tensorflow.org/lite/guide/build_arm">Build TensorFlow Lite for ARM boards</a> for the migration.</li> <li>Deprecate <code>tflite::OpResolver::GetDelegates</code>. The list returned by TfLite's <code>BuiltinOpResolver::GetDelegates</code> is now always empty. Instead, recommend using new method <code>tflite::OpResolver::GetDelegateCreators</code> in order to achieve lazy initialization on TfLite delegate instances.</li> </ul> </li> <li> <p>TF Core:</p> <ul> <li><code>tf.Graph.get_name_scope()</code> now always returns a string, as documented. Previously, when called within <code>name_scope(&quot;&quot;)</code> or <code>name_scope(None)</code> contexts, it returned <code>None</code>; now it returns the empty string.</li> <li><code>tensorflow/core/ir/</code> contains a new MLIR-based Graph dialect that is isomorphic to GraphDef and will be used to replace GraphDef-based (e.g., Grappler) optimizations.</li> <li>Deprecated and removed <code>attrs()</code> function in shape inference. All attributes should be queried by name now (rather than range returned) to enable changing the underlying storage there.</li> <li>The following Python symbols were accidentally added in earlier versions of TensorFlow and now are removed. Each symbol has a replacement that should be used instead, but note the replacement's argument names are different. <ul> <li><code>tf.quantize_and_dequantize_v4</code> (accidentally introduced in TensorFlow 2.4): Use <code>tf.quantization.quantize_and_dequantize_v2</code> instead.</li> <li><code>tf.batch_mat_mul_v3</code> (accidentally introduced in TensorFlow 2.6): Use <code>tf.linalg.matmul</code> instead.</li> <li><code>tf.sparse_segment_sum_grad</code> (accidentally introduced in TensorFlow 2.6): Use <code>tf.raw_ops.SparseSegmentSumGrad</code> instead. Directly calling this op is typically not necessary, as it is automatically used when computing the gradient of <code>tf.sparse.segment_sum</code>.</li> </ul> </li> <li>Renaming of tensorflow::int64 to int_64_t in numerous places (the former is an alias for the latter) which could result in needing to regenerate selective op registration headers else execution would fail with unregistered kernels error.</li> </ul> </li> <li> <p>Modular File System Migration:</p> <ul> <li>Support for S3 and HDFS file systems has been migrated to a modular file systems based approach and is now available in <a href="https://github.com/tensorflow/io">https://github.com/tensorflow/io</a>. The <code>tensorflow-io</code> python package should be installed for S3 and HDFS support with tensorflow.</li> </ul> </li> </ul> <h2>Major Features and Improvements</h2> <ul> <li> <p>Improvements to the TensorFlow debugging experience:</p> <ul> <li> <p>Previously, TensorFlow error stack traces involved many internal frames, which could be challenging to read through, while not being actionable for end users. As of TF 2.7, TensorFlow filters internal frames in most errors that it raises, to keep stack traces short, readable, and focused on what's actionable for end users (their own code).</p> <p>This behavior can be disabled by calling <code>tf.debugging.disable_traceback_filtering()</code>, and can be re-enabled via <code>tf.debugging.enable_traceback_filtering()</code>. If you are debugging a TensorFlow-internal issue (e.g. to prepare a TensorFlow PR), make sure to disable traceback filtering. You can check whether this feature is currently enabled by calling <code>tf.debugging.is_traceback_filtering_enabled()</code>.</p> <p>Note that this feature is only available with Python 3.7 or higher.</p> </li> <li> <p>Improve the informativeness of error messages raised by Keras <code>Layer.__call__()</code>, by adding the full list of argument values passed to the layer in every exception.</p> </li> </ul> </li> <li> <p>Introduce the <code>tf.compat.v1.keras.utils.track_tf1_style_variables</code> decorator, which enables using large classes of tf1-style variable_scope, <code>get_variable</code>, and <code>compat.v1.layer</code>-based components from within TF2 models running with TF2 behavior enabled.</p> </li> <li> <p><code>tf.data</code>:</p> <ul> <li> <p>tf.data service now supports auto-sharding. Users specify the sharding policy with <code>tf.data.experimental.service.ShardingPolicy</code> enum. It can be one of <code>OFF</code> (equivalent to today's <code>&quot;parallel_epochs&quot;</code> mode), <code>DYNAMIC</code> (equivalent to today's <code>&quot;distributed_epoch&quot;</code> mode), or one of the static sharding policies: <code>FILE</code>, <code>DATA</code>, <code>FILE_OR_DATA</code>, or <code>HINT</code> (corresponding to values of <code>tf.data.experimental.AutoShardPolicy</code>).</p> <p>Static sharding (auto-sharding) requires the number of tf.data service workers be fixed. Users need to specify the worker addresses in <code>tensorflow.data.experimental.DispatcherConfig</code>.</p> </li> <li> <p><code>tf.data.experimental.service.register_dataset</code> now accepts optional <code>compression</code> argument.</p> </li> </ul> </li> <li> <p>Keras:</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/tensorflow/tensorflow/blob/master/RELEASE.md">tensorflow's changelog</a>.</em></p> <blockquote> <h1>Release 2.7.0</h1> <h2>Breaking Changes</h2> <ul> <li> <p><code>tf.keras</code>:</p> <ul> <li>The methods <code>Model.fit()</code>, <code>Model.predict()</code>, and <code>Model.evaluate()</code> will no longer uprank input data of shape <code>(batch_size,)</code> to become <code>(batch_size, 1)</code>. This enables <code>Model</code> subclasses to process scalar data in their <code>train_step()</code>/<code>test_step()</code>/<code>predict_step()</code> methods.<br /> Note that this change may break certain subclassed models. You can revert back to the previous behavior by adding upranking yourself in the <code>train_step()</code>/<code>test_step()</code>/<code>predict_step()</code> methods, e.g. <code>if x.shape.rank == 1: x = tf.expand_dims(x, axis=-1)</code>. Functional models as well as Sequential models built with an explicit input shape are not affected.</li> <li>The methods <code>Model.to_yaml()</code> and <code>keras.models.model_from_yaml</code> have been replaced to raise a <code>RuntimeError</code> as they can be abused to cause arbitrary code execution. It is recommended to use JSON serialization instead of YAML, or, a better alternative, serialize to H5.</li> <li><code>LinearModel</code> and <code>WideDeepModel</code> are moved to the <code>tf.compat.v1.keras.models.</code> namespace (<code>tf.compat.v1.keras.models.LinearModel</code> and <code>tf.compat.v1.keras.models.WideDeepModel</code>), and their <code>experimental</code> endpoints (<code>tf.keras.experimental.models.LinearModel</code> and <code>tf.keras.experimental.models.WideDeepModel</code>) are being deprecated.</li> <li>RNG behavior change for all <code>tf.keras.initializers</code> classes. For any class constructed with a fixed seed, it will no longer generate same value when invoked multiple times. Instead, it will return different value, but a determinisitic sequence. This change will make the initialize behavior align between v1 and v2.</li> </ul> </li> <li> <p><code>tf.lite</code>:</p> <ul> <li>Rename fields <code>SignatureDef</code> table in schema to maximize the parity with TF SavedModel's Signature concept.</li> <li>Deprecate Makefile builds. Makefile users need to migrate their builds to CMake or Bazel. Please refer to the <a href="https://www.tensorflow.org/lite/guide/build_cmake">Build TensorFlow Lite with CMake</a> and <a href="https://www.tensorflow.org/lite/guide/build_arm">Build TensorFlow Lite for ARM boards</a> for the migration.</li> <li>Deprecate <code>tflite::OpResolver::GetDelegates</code>. The list returned by TfLite's <code>BuiltinOpResolver::GetDelegates</code> is now always empty. Instead, recommend using new method <code>tflite::OpResolver::GetDelegateCreators</code> in order to achieve lazy initialization on TfLite delegate instances.</li> </ul> </li> <li> <p>TF Core:</p> <ul> <li><code>tf.Graph.get_name_scope()</code> now always returns a string, as documented. Previously, when called within <code>name_scope(&quot;&quot;)</code> or <code>name_scope(None)</code> contexts, it returned <code>None</code>; now it returns the empty string.</li> <li><code>tensorflow/core/ir/</code> contains a new MLIR-based Graph dialect that is isomorphic to GraphDef and will be used to replace GraphDef-based (e.g., Grappler) optimizations.</li> <li>Deprecated and removed <code>attrs()</code> function in shape inference. All attributes should be queried by name now (rather than range returned) to enable changing the underlying storage there.</li> <li>The following Python symbols were accidentally added in earlier versions of TensorFlow and now are removed. Each symbol has a replacement that should be used instead, but note the replacement's argument names are different. <ul> <li><code>tf.quantize_and_dequantize_v4</code> (accidentally introduced in TensorFlow 2.4): Use <code>tf.quantization.quantize_and_dequantize_v2</code> instead.</li> <li><code>tf.batch_mat_mul_v3</code> (accidentally introduced in TensorFlow 2.6): Use <code>tf.linalg.matmul</code> instead.</li> <li><code>tf.sparse_segment_sum_grad</code> (accidentally introduced in TensorFlow 2.6): Use <code>tf.raw_ops.SparseSegmentSumGrad</code> instead. Directly calling this op is typically not necessary, as it is automatically used when computing the gradient of <code>tf.sparse.segment_sum</code>.</li> </ul> </li> <li>Renaming of tensorflow::int64 to int_64_t in numerous places (the former is an alias for the latter) which could result in needing to regenerate selective op registration headers else execution would fail with unregistered kernels error.</li> </ul> </li> <li> <p>Modular File System Migration:</p> <ul> <li>Support for S3 and HDFS file systems has been migrated to a modular file systems based approach and is now available in <a href="https://github.com/tensorflow/io">https://github.com/tensorflow/io</a>. The <code>tensorflow-io</code> python package should be installed for S3 and HDFS support with tensorflow.</li> </ul> </li> </ul> <h2>Major Features and Improvements</h2> <ul> <li> <p>Improvements to the TensorFlow debugging experience:</p> <ul> <li> <p>Previously, TensorFlow error stack traces involved many internal frames, which could be challenging to read through, while not being actionable for end users. As of TF 2.7, TensorFlow filters internal frames in most errors that it raises, to keep stack traces short, readable, and focused on what's actionable for end users (their own code).</p> <p>This behavior can be disabled by calling <code>tf.debugging.disable_traceback_filtering()</code>, and can be re-enabled via <code>tf.debugging.enable_traceback_filtering()</code>. If you are debugging a TensorFlow-internal issue (e.g. to prepare a TensorFlow PR), make sure to disable traceback filtering. You can check whether this feature is currently enabled by calling <code>tf.debugging.is_traceback_filtering_enabled()</code>.</p> <p>Note that this feature is only available with Python 3.7 or higher.</p> </li> <li> <p>Improve the informativeness of error messages raised by Keras <code>Layer.__call__()</code>, by adding the full list of argument values passed to the layer in every exception.</p> </li> </ul> </li> <li> <p>Introduce the <code>tf.compat.v1.keras.utils.track_tf1_style_variables</code> decorator, which enables using large classes of tf1-style variable_scope, <code>get_variable</code>, and <code>compat.v1.layer</code>-based components from within TF2 models running with TF2 behavior enabled.</p> </li> <li> <p><code>tf.data</code>:</p> <ul> <li> <p>tf.data service now supports auto-sharding. Users specify the sharding policy with <code>tf.data.experimental.service.ShardingPolicy</code> enum. It can be one of <code>OFF</code> (equivalent to today's <code>&quot;parallel_epochs&quot;</code> mode), <code>DYNAMIC</code> (equivalent to today's <code>&quot;distributed_epoch&quot;</code> mode), or one of the static sharding policies: <code>FILE</code>, <code>DATA</code>, <code>FILE_OR_DATA</code>, or <code>HINT</code> (corresponding to values of <code>tf.data.experimental.AutoShardPolicy</code>).</p> <p>Static sharding (auto-sharding) requires the number of tf.data service workers be fixed. Users need to specify the worker addresses in <code>tensorflow.data.experimental.DispatcherConfig</code>.</p> </li> <li> <p><code>tf.data.experimental.service.register_dataset</code> now accepts optional <code>compression</code> argument.</p> </li> </ul> </li> <li> <p>Keras:</p> <ul> <li><code>tf.keras.layers.Conv</code> now includes a public <code>convolution_op</code> method. This method can be used to simplify the implementation of Conv subclasses. There are two primary ways to use this new method. The first is to use the method directly in your own <code>call</code> method:</li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tensorflow/tensorflow/commit/c256c071bb26e1e13b4666d1b3e229e110bc914a"><code>c256c07</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/tensorflow/tensorflow/issues/52891">#52891</a> from tensorflow/mm-update-relnotes</li> <li><a href="https://github.com/tensorflow/tensorflow/commit/8cca7723416ad323545853593034bdaa8965fae0"><code>8cca772</code></a> Add security updates to relnotes</li> <li><a href="https://github.com/tensorflow/tensorflow/commit/4124c12377fa793cf5176d9c0b8838d6d8c8300c"><code>4124c12</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/tensorflow/tensorflow/issues/52868">#52868</a> from tensorflow-jenkins/version-numbers-2.7.0-29671</li> <li><a href="https://github.com/tensorflow/tensorflow/commit/9bd96c9bf407c5422d54c2e6d85748bb7b81634f"><code>9bd96c9</code></a> Update version numbers to 2.7.0</li> <li><a href="https://github.com/tensorflow/tensorflow/commit/2a68316f7adfb9162bff47b2062d091d137fa483"><code>2a68316</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/tensorflow/tensorflow/issues/52840">#52840</a> from tensorflow/mm-cp-pr-on-r2.7</li> <li><a href="https://github.com/tensorflow/tensorflow/commit/2aebcb8b0d507e12f68b2ced258643859a44847e"><code>2aebcb8</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/tensorflow/tensorflow/issues/51733">#51733</a> from yongtang:46888-tf.math.segment_</li> <li><a href="https://github.com/tensorflow/tensorflow/commit/1a3174c123c39d1d163c5b21d062118d5a56a412"><code>1a3174c</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/tensorflow/tensorflow/issues/52835">#52835</a> from tensorflow/mm-cp-6-on-r2.7</li> <li><a href="https://github.com/tensorflow/tensorflow/commit/f43a11cd809d12db4866a46a68b459e86adfca86"><code>f43a11c</code></a> Fix segfault on OOM in Conv2D.</li> <li><a href="https://github.com/tensorflow/tensorflow/commit/4413827b0de630666c1942bc33327aae9bd7212f"><code>4413827</code></a> Fix segfault in pools on empty shapes when certain dimension were very large.</li> <li><a href="https://github.com/tensorflow/tensorflow/commit/5800f01ba4e8fbb359a3c372fc220fcbe038e80b"><code>5800f01</code></a> Roll forward <a href="https://github.com/tensorflow/tensorflow/commit/ab0ca4bbc66a476a">https://github.com/tensorflow/tensorflow/commit/ab0ca4bbc66a476a</a>...</li> <li>Additional commits viewable in <a href="https://github.com/tensorflow/tensorflow/compare/v2.6.0...v2.7.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tensorflow&package-manager=pip&previous-version=2.6.0&new-version=2.7.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
chychkan commented 2021-11-11 23:49:47 +01:00 (Migrated from github.com)
Copy Link
Copy Source

@dependabot rebase

@dependabot rebase
👍 1
chychkan (Migrated from github.com) approved these changes 2021-11-12 00:17:27 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
chychkan
Labels
Clear labels
bug
Something isn't working
 dependencies
Pull requests that update a dependency file
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 placeholder
Keeping open for more changes
 question
Further information is requested
 stale issue
No activity in 30 days
 wontfix
This will not be worked on
No Label dependencies
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
CalvinBackup (Calvin Backup)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: CalvinBackup/DeepFaceLab_MacOS#53
Delete Branch "dependabot-pip-tensorflow-2.7.0"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?