Skip to content

description how to terminate o2 #12650

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ktf merged 2 commits into from
Apr 25, 2024
Merged

description how to terminate o2 #12650

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
823516a
description how to terminate o2
justonedev1 Feb 2, 2024
173b644
Update Framework/Core/README.md
ktf Apr 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update Framework/Core/README.md
  • Loading branch information
@ktf
ktf authored Apr 25, 2024
commit 173b6440e9c87ac5c14e78372358f1f41f9f6e04
2 changes: 1 addition & 1 deletion Framework/Core/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -277,7 +277,7 @@ however, no API is provided to explicitly send it. All the created DataChunks ar

When an error happens during processing of some data, the writer of the `process` function should simply throw an exception. By default the exception is caught by the `DataProcessingDevice` and a message is printed (if `std::exeception` derived `what()` method is used, otherwise a generic message is given). Users can provide themselves an error handler by specifying via the `onError` callback specified in `DataProcessorSpec`. This will allow in the future to reinject data into the flow in case of an error.

When the exception is thrown inside processing function it's message and stack trace is printed. However, the application itself is not terminated. If the error encountered is so severe that current workflow cannot continue it is advisable to call `LOG(fatal)` with proper describing message, which makes the application shutdown with non zero error code.
When the exception is thrown inside processing function its message and stack trace is printed. However, the application itself is not terminated. If the error encountered is so severe that current workflow cannot continue it is advisable to call `LOG(fatal)` with proper describing message, which makes the application shutdown with non zero error code.

### Services

Expand Down