Unlike InvalidArgumentError, this error indicates a problem may be fixed if
the system state changes. For example, if a list grows and the operation is
now within the valid range. OutOfRangeError overlaps with
FailedPreconditionError and should be preferred as the more specific error
when iterating or accessing a range.
For example, iterating a TF dataset past the last item in the dataset will
raise this error.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-04-26 UTC."],[],[],null,["# tf.errors.OutOfRangeError\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#L417-L434) |\n\nRaised when an operation iterates past the valid range.\n\nInherits From: [`OpError`](../../tf/errors/OpError)\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.errors.OutOfRangeError`](https://www.tensorflow.org/api_docs/python/tf/errors/OutOfRangeError)\n\n\u003cbr /\u003e\n\n tf.errors.OutOfRangeError(\n node_def, op, message, *args\n )\n\nUnlike `InvalidArgumentError`, this error indicates a problem may be fixed if\nthe system state changes. For example, if a list grows and the operation is\nnow within the valid range. `OutOfRangeError` overlaps with\n`FailedPreconditionError` and should be preferred as the more specific error\nwhen iterating or accessing a range.\n\nFor example, iterating a TF dataset past the last item in the dataset will\nraise this error.\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. |"]]
View source on GitHub