Skip to content
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.

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

Include reference to block or output introducing error #995

Merged
merged 12 commits into from
Feb 5, 2025

Conversation

grzegorz-roboflow
Copy link
Contributor

Description

Add blocks_syntax_errors and outputs_syntax_errors to WorkflowSyntaxError
Add block_id to StepExecutionError

Type of change

  • New feature (non-breaking change which adds functionality)

How has this change been tested, please provide a testcase or example of how you tested the change?

CI passing
Manually E2E tested

Any specific deployment considerations

N/A

Docs

N/A

@@ -135,6 +135,8 @@ def safe_execute_step(
except Exception as error:
logger.exception(f"Execution of step {step_selector} encountered error.")
raise StepExecutionError(
block_id=step_selector,
block_type=workflow.steps[step_selector.split(".")[-1]].manifest.type,
public_message=f"Error during execution of step: {step_selector}. Details: {error}",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we update the public message to just {error} instead of "Error during execution of step: {step_selector}. Details: {error}" since we are already sending the step_selector data

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Depends how much do we want to maintain preexisting keys to keep backwards compatibility. I agree remaining keys seem redundant in this context.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets change the error message - we send the type of error upstream and we do also provide step selector - putting that inside msg is redundant

Copy link
Collaborator

@PawelPeczek-Roboflow PawelPeczek-Roboflow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM up to minor changes

@grzegorz-roboflow grzegorz-roboflow merged commit 8de2151 into main Feb 5, 2025
35 checks passed
@grzegorz-roboflow grzegorz-roboflow deleted the add-block-id-to-error-payloads branch February 5, 2025 12:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants