Skip to content

fix(adapter): inject default variable resolver in graphRunnable.Execute#4

Merged
lIang70 merged 1 commit into
mainfrom
fix/adapter-inject-variable-resolver
Apr 14, 2026
Merged

fix(adapter): inject default variable resolver in graphRunnable.Execute#4
lIang70 merged 1 commit into
mainfrom
fix/adapter-inject-variable-resolver

Conversation

@lIang70

@lIang70 lIang70 commented Apr 14, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Bug: adapter.graphRunnable.Execute() did not inject a default variable.NewResolver() like executor.Runner.Run() does, causing ${board.xxx} variable references in node configs to go unresolved when graphs are executed through the workflow adapter.
  • Fix: Pre-populate execOpts with executor.WithResolver(variable.NewResolver()) in graphRunnable.Execute(), matching the behavior of Runner.Run().
  • Callers can still override the resolver via ExtExecutorRunOpts.

Test plan

  • go build ./graph/adapter/... compiles successfully
  • go test ./graph/adapter/... all tests pass
  • Verify that a GraphDefinition containing ${board.xxx} references resolves variables correctly when executed through the adapter path

graphRunnable.Execute did not inject a variable.NewResolver() like
Runner.Run does, causing ${board.xxx} references in node configs to
go unresolved when graphs are executed through the workflow adapter.

Made-with: Cursor
@lIang70
lIang70 merged commit 2fb7b2e into main Apr 14, 2026
8 checks passed
lIang70 added a commit that referenced this pull request Apr 14, 2026
…nnable

Verifies that ${board.xxx} references in node configs are correctly
resolved when executed through the adapter path (covers the fix in #4).

Made-with: Cursor
lIang70 added a commit that referenced this pull request Apr 14, 2026
sdk v0.1.2 includes the adapter variable resolver fix (#4) and its
regression test (#5).

Made-with: Cursor
@lIang70
lIang70 deleted the fix/adapter-inject-variable-resolver branch April 14, 2026 13:14
lIang70 added a commit that referenced this pull request May 21, 2026
Propagate queue Complete/Fail errors, prefer enqueue TurnsSnapshot over
lossy canonical parse, and emit ForgetAll/ExpireRetired telemetry with
AsyncJobsCancelled after trace is populated.

Co-authored-by: Cursor <cursoragent@cursor.com>
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.

1 participant