Skip to content

docs(boundary): the executor sets TASK_ATTEMPT on every production Job - #96

Merged
carolsimone merged 1 commit into
mainfrom
docs/task-attempt-env
Oct 23, 2026
Merged

carolsimone merged 1 commit into
mainfrom
docs/task-attempt-env

Conversation

@carolsimone

Copy link
Copy Markdown
Owner

Summary

  • docs/boundary-contract.md lists TASK_ATTEMPT in the python-node env contract: the 0-based number of the task's attempt (0 on a task's first run, 1 on its first retry). The executor sets it on every production Job, dbt and python alike.
  • The harness does not read it; a node script may. Documentation only: no package changes, no version bump.
  • CHANGELOG.md [Unreleased] carries the entry.

Companion to the continuo change that makes state decide every attempt of a task and execution-controller run exactly one attempt per dispatch (carolsimone/continuo, feat/execution-protocol-switch).

🤖 Generated with Claude Code

The python-node env contract lists TASK_ATTEMPT, the 0-based number of the
task's attempt (0 on the first run, 1 on the first retry). The executor sets
it on dbt and python Jobs alike; the harness does not read it, a node script
may.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Simone Carolini <simonecarolini.sc@gmail.com>
@carolsimone carolsimone self-assigned this Oct 23, 2026
@carolsimone
carolsimone merged commit 6116f8f into main Oct 23, 2026
9 checks passed
@carolsimone
carolsimone deleted the docs/task-attempt-env branch October 23, 2026 08:02
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