Skip to content

Use better exit codes and terminate log writer on exit

Type of change

  • Bug Fix
  • Feature

Does this introduce a change in the core logic?

  • [Yes]

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Updates description?

The segy_indexer DAG sometimes appears to complete with a status message like below: terminate called after throwing an instance of 'pplx::task_canceled' This is most likely caused by incorrect (or no termination at all) termination of the logging process. Ensure the logging is correctly terminated. Also ensure that usage info is always written to std:cout rather than to the log writer.

Edited by Erik Dahl

Merge request reports

Loading