Skip to content

Fix graph not detecting errors when GraphExecutor::run fails#110

Merged
oathdruid merged 1 commit intobaidu:mainfrom
skyan:main
Nov 9, 2025
Merged

Fix graph not detecting errors when GraphExecutor::run fails#110
oathdruid merged 1 commit intobaidu:mainfrom
skyan:main

Conversation

@skyan
Copy link
Contributor

@skyan skyan commented Nov 9, 2025

  • In extreme cases such as when the thread pool is full, GraphExecutor::run may return an error. Previously, the graph did not detect these errors, which could cause other nodes to not execute without reporting any error.
  • Also update .gitignore to exclude bazel build artifacts and module files

* In extreme cases such as when the thread pool is full, GraphExecutor::run
may return an error. Previously, the graph did not detect these errors,
which could cause other nodes to not execute without reporting any error.
* Also update .gitignore to exclude bazel build artifacts and module files
@coveralls
Copy link
Collaborator

Coverage Status

coverage: 85.273% (+0.1%) from 85.178%
when pulling d7f1a2a on skyan:main
into 628270a on baidu:main.

@oathdruid oathdruid merged commit c230b4f into baidu:main Nov 9, 2025
28 checks passed
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