Skip to content

Raise TypeError when a task is called without a context - #1098

Open
Hugohong258 wants to merge 1 commit into
pyinvoke:2.2from
Hugohong258:fix-missing-task-context-error
Open

Hugohong258 wants to merge 1 commit into
pyinvoke:2.2from
Hugohong258:fix-missing-task-context-error

Conversation

@Hugohong258

Copy link
Copy Markdown

Calling a valid task with no arguments currently indexes args[0] before checking the required Context, leaking IndexError: tuple index out of range. Check for an empty argument tuple first so the existing TypeError guard handles the call. The regression also verifies that the task's call counter stays unchanged.

Validation: the new regression fails with IndexError on the base. On WSL Linux/Python 3.14.4, 109 related task/executor tests pass and 1 is skipped. Windows/Python 3.12.3 and Linux/Python 3.14.4 checks verify the error and a subsequent valid call. Black 22.8, Flake8 4 with an external host entry-point API adapter, and mypy 0.971 over all 48 source files pass. The adapter excludes unrelated host plugins and preserves normal noqa handling. The full unit suite, integrations and older-runtime CI matrix were not run. Based on the 2.2 release line per the contribution guide.

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