You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if any Error happens in the sub-process, the child process would just exits without passing Error message back to the main process. And, the data pipeline in the main process will continue without proper exit.
In order to achieve this feature, we need to do the following step:
Summary:
Partially fixespytorch#969
### Changes
- Add `ExceptionWrapper` to attach traceback to the Exception
- Reason: traceback is unserializable. So, it has to be passed by string
- In order to provide informative Error message, pass name for each process like `dispatching process` and `worker process <id>`.
- Add tests to validate Error propagation from the dispatching process
- parametrize the tests
- Fix a bug for `round_robin_demux` to return a list of DataPipe rather than a single DataPipe when `num_of_instances` is 1.
Pull Request resolved: pytorch#1036
Reviewed By: NivekT
Differential Revision: D43472709
Pulled By: ejguan
fbshipit-source-id: e5c9e581ca881f523fb568b6f46bf16ecfc243d2
Summary:
Partially fixes#969
### Changes
- Add `ExceptionWrapper` to attach traceback to the Exception
- Reason: traceback is unserializable. So, it has to be passed by string
- In order to provide informative Error message, pass name for each process like `dispatching process` and `worker process <id>`.
- Add tests to validate Error propagation from the dispatching process
- parametrize the tests
- Fix a bug for `round_robin_demux` to return a list of DataPipe rather than a single DataPipe when `num_of_instances` is 1.
Pull Request resolved: #1036
Reviewed By: NivekT
Differential Revision: D43472709
Pulled By: ejguan
fbshipit-source-id: e5c9e581ca881f523fb568b6f46bf16ecfc243d2
🚀 The feature
Currently, if any Error happens in the sub-process, the child process would just exits without passing Error message back to the main process. And, the data pipeline in the main process will continue without proper exit.
In order to achieve this feature, we need to do the following step:
res_queue
Forward worker exceptions and exit with it #1003res_queue
_IterateQueueDataPipes
to differentiate Error from worker or dispatching processMotivation, pitch
Increase reliability of DataLoader with
PrototypeMultiprocessingReadingService
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: