You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Contexts should give better stack trace information for subprocesses #7
Resolved for the current supported Execute-backed Dispatch path by merged PR #66 (merge 9cece32): bounded raw worker tracebacks are shown by default for generic RemoteExecutionError and CoreExecutionError, with raw_traceback=False available for sensitive work. This supersedes the old Context/subprocess diagnostic gap rather than claiming every retired Context route has been separately retested. Reopen if a supported failure path still loses its worker stack or if the old Context API itself remains in scope.
Activity
fix(review): harden shared requirement diagnostics
fix(managed): preserve explicit execution config and declaration owne…
krafczyk commentedon Oct 6, 2026
Resolved for the current supported Execute-backed Dispatch path by merged PR #66 (merge 9cece32): bounded raw worker tracebacks are shown by default for generic RemoteExecutionError and CoreExecutionError, with raw_traceback=False available for sensitive work. This supersedes the old Context/subprocess diagnostic gap rather than claiming every retired Context route has been separately retested. Reopen if a supported failure path still loses its worker stack or if the old Context API itself remains in scope.