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
fix(logs): gate workflow input inherited from a prior execution
Greptile review: the boundary exemption assumed a non-nested trigger implies an
inbound payload. A re-run with inputFromExecutionId breaks that. It copies the
source run's workflowInput verbatim, and the destination presents whatever
trigger type its caller asked for, so a value resolved inside a custom_block
parent could arrive in a manual run and be exempted. The destination's own
provenance cannot describe the source's secret resolution, so no matcher covers
it.
The read path could not tell an inherited input from a fresh one, so the re-run
now records its source: LoggingSession.setInputSourceExecutionId stamps it into
the existing trigger data channel, and the display projection withholds the
exemption whenever it is present. Nested runs and inherited-input runs share one
predicate - neither is a pre-resolution inbound payload.
Adds setInputSourceExecutionId to the shared @sim/testing LoggingSession mock so
the execute-route suites exercise the real call.
0 commit comments