Skip to content

improving execution error handling #473

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

roy232828
Copy link
Collaborator

Features

  • Node info is now included in the error notification.

Fixes

  • Send a notification when the Map node throws an error.
  • ds-ext now reports error details in the error notification.
image

Copy link

vercel bot commented Jul 27, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
data-story-docs Ready Preview Comment Aug 15, 2025 8:02am

Copy link
Owner

@ajthinking ajthinking left a comment

Choose a reason for hiding this comment

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

Thank you 🙌

@@ -64,7 +65,7 @@ export class ExecutionMemoryFactory {

// Initialize runner context
const context = new NodeRunnerContext(node.id);
context.status = computer.run({
context.status = withNodeExecutionErrorHandling(computer.run.bind(computer), node)({
Copy link
Owner

Choose a reason for hiding this comment

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

Do we need .bind(computer)?
By doing so we let the run function access this keyword to retrieve the value of the computer? However, I don't see the use case for that here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Good catch. I've removed the bind(computer) call.

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.

2 participants