Usually, TensorFlow will raise a more specific subclass of OpError from the
tf.errors module.
Args
node_def
The node_def_pb2.NodeDef proto representing the op that
failed, if known; otherwise None.
op
The ops.Operation that failed, if known; otherwise None. During
eager execution, this field is always None.
message
The message string describing the failure.
error_code
The error_codes_pb2.Code describing the error.
*args
If not empty, it should contain a dictionary describing details
about the error. This argument is inspired by Abseil payloads:
https://github.com/abseil/abseil-cpp/blob/master/absl/status/status.h
Attributes
error_code
The integer error code that describes the error.
experimental_payloads
A dictionary describing the details of the error.
message
The error message that describes the error.
node_def
The NodeDef proto representing the op that failed.
[null,null,["Last updated 2024-04-26 UTC."],[],[],null,["# tf.errors.OpError\n\n\u003cbr /\u003e\n\n|------------------------------------------------------------------------------------------------------------------------------------|\n| [View source on GitHub](https://github.com/tensorflow/tensorflow/blob/v2.16.1/tensorflow/python/framework/errors_impl.py#L57-L183) |\n\nThe base class for TensorFlow exceptions.\n\n#### View aliases\n\n\n**Compat aliases for migration**\n\nSee\n[Migration guide](https://www.tensorflow.org/guide/migrate) for\nmore details.\n\n[`tf.compat.v1.OpError`](https://www.tensorflow.org/api_docs/python/tf/errors/OpError), [`tf.compat.v1.errors.OpError`](https://www.tensorflow.org/api_docs/python/tf/errors/OpError)\n\n\u003cbr /\u003e\n\n tf.errors.OpError(\n node_def, op, message, error_code, *args\n )\n\nUsually, TensorFlow will raise a more specific subclass of `OpError` from the\n[`tf.errors`](../../tf/errors) module.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n| Args ---- ||\n|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `node_def` | The `node_def_pb2.NodeDef` proto representing the op that failed, if known; otherwise None. |\n| `op` | The `ops.Operation` that failed, if known; otherwise None. During eager execution, this field is always `None`. |\n| `message` | The message string describing the failure. |\n| `error_code` | The `error_codes_pb2.Code` describing the error. |\n| `*args` | If not empty, it should contain a dictionary describing details about the error. This argument is inspired by Abseil payloads: https://github.com/abseil/abseil-cpp/blob/master/absl/status/status.h |\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n| Attributes ---------- ||\n|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `error_code` | The integer error code that describes the error. |\n| `experimental_payloads` | A dictionary describing the details of the error. |\n| `message` | The error message that describes the error. |\n| `node_def` | The `NodeDef` proto representing the op that failed. |\n| `op` | The operation that failed, if known. \u003cbr /\u003e | **Note:** If the failed op was synthesized at runtime, e.g. a `Send` or `Recv` op, there will be no corresponding [`tf.Operation`](../../tf/Operation) object. In that case, this will return `None`, and you should instead use the [`tf.errors.OpError.node_def`](../../tf/errors/OpError#node_def) to discover information about the op. |"]]