Error Codes

You have likely reached this page through our DROPLogs!

The following documentation details the ErrorCode enums that we link to common runtime exceptions. Each ErrorCode has debugging tips and suggestions for how you may rectify the error.

Note

This page is most likely to be useful when testing and developing a graph that is a work-in-progress.

class dlg.runtime.error_management.ErrorCode(value)

Enum for Errors that occur during runtime execution on the engine. We use Enum for the auto-incremementer, and because we can use the autodoc feature of Sphinx to generate

DROP_ERROR = 100

An error occured during DROP initialization that was not expected. Please double-check your current graph and attempt to resolve the issue based on the debugging tips for DROP_ERROR codes below.

If none of the fixes address your isse, please consider opening an issue on our GitHub repository here.

INCOMPLETE_DROP_SPEC = 101

The DROP being initalized was not complete. This means that key parameters in the have not been filled. If you are using a PyFuncApp, double-check you have filled in both the func_name parameter if you are filling in the func_code parameter too.

BAD_IMPORT = 102

There was an issue importing the module. Consider:

  • Reviewing the current environment

  • Reviewing the spelling

  • Ensuring there are no missing dependencies

ENCODING_ERROR = 103

There was an issue with reading/writing data in your drop. This is likely caused by using the wrong ‘encoding’ option when configuring your graph in EAGLE. Please ensure that:

  • The OutputPort/InputPort on your Apps are using the same encoding

  • The Encoding matches the Type (e.g. String types are using UTF-8 encoding)

  • The DataDROP matches the right type/encoding (e.g. Using a File for its path is using ‘path’ encoding’).

These changes will need to be added to the EAGLE graph.

PATH_ERROR = 104

There was an issue with the path set for this DROP, which may becaused by the following:

  • The file does not exist and/or you have set check_filepath_exists to be True.

  • The directory does not exist at runtime

  • An environment variable that is being referred to has not been set and cannot be expanded

Please review the DataDROP parameter values for this DROP.

BASH_COMMAND_FAILED = 105

There was an issue running your BashShellApp DROP. This may be caused by:

  • The application cannot find the program you are running (e.g. cannot find the script that is being referred to)

  • The arguments applied to the command line are incorrectly formatted; for example, incorrect flags, or the wrong redirect was used.

OUTPUT_DROPPED_CANCELLED = 106

During the runtime of this DROP, the output DROP was cancelled before it could be written to.

This is likely the result of a distributed session failure in which a graph distributed across multiple nodes has failed during the session. Current known causes of this are:

  • A PyFuncAppDROP failed to be initialised during deployment and the session failed. Please review other FAILED nodes (red) in the graph to see if they report a BAD_IMPORT code.

GRAPH_ERROR = 200

An error has occured during graph execution that was not expected. Please double-check your current graph and attempt to resolve the issue based on the debugging tips for SESSION_ERROR codes below.

If none of the fixes address your isse, please consider opening an issue on our GitHub repository here.

INVALID_GRAPH_CONFIGURATION = 201

The graph has failed to be loaded by the DALiuGE Engine. This can be caused by number of issues:

  • A python module that your graph relies on is not currently accessible in the virtual environment in which DALiuGE is being run.

  • The graph is missing key arguments - please check the JSON is complete.

SESSION_ERROR = 300

An error has occured during your session that was not expected. Please double-check your current graph and attempt to resolve the issue based on the debugging tips for SESSION_ERROR codes below.

If none of the fixes address your isse, please consider opening an issue on our GitHub repository here and attaching the log files.

SESSION_STATE_ERROR = 301

The session has been put in a state is was not expecting. This could be the result of a synchronisation issue between the managers; consider restarting them and re-running your session.

SESSION_MISSING_ERROR = 302

A session was not found that was requested. This typically occurs when restarting the Node Manager(s) when a Data Island Manager is still running.

If a Node Manager was not restarted, please reveiw the logs and if the issue persists, consider opening an issue on our GitHub repository here and attaching the log files.

property doc_url: str