Skip to content

#75 - FileFetchTask: explicit failure for an unknown storage - #76

Merged
njoubert-cleverage merged 2 commits into
mainfrom
75
Oct 23, 2026
Merged

njoubert-cleverage merged 2 commits into
mainfrom
75

Conversation

@njoubert-cleverage

@njoubert-cleverage njoubert-cleverage commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

Description

Fixes #75.

  • FileFetchTask::initialize() resolves the storages through a new getStorage(): an unknown storage throws UnexpectedValueException('Unknown storage "…" (option "…"), known storages: "…"') instead of Service "…" not found.
  • execute() fails with an explicit message when the storages are not available (process-bundle v5 executes the task after a failed initialization), instead of Typed property FileFetchTask::$sourceFS must not be accessed before initialization.
  • file_fetch_task.md: the note no longer says that the process fails before any task is executed.

Requirements

  • Documentation updates
    • Reference
    • Changelog
  • Unit tests

Breaking changes

None: only the messages of failures change.

🤖 Generated with Claude Code

njoubert-cleverage and others added 2 commits October 22, 2026 17:17
…for an unknown storage, and with an explicit message when the task is executed after a failed initialization instead of an uninitialized property error or the storages of a previous initialization. Update documentation, add tests.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@njoubert-cleverage
njoubert-cleverage merged commit 12e9867 into main Oct 23, 2026
18 checks passed
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.

FileFetchTask: an unknown storage fails with a misleading message, after the previous tasks

1 participant