Files
mcphub/core/media_error_codes.py
airano-ir f203ca88de
Some checks failed
Release / Test before release (push) Has been cancelled
Release / Publish to PyPI (push) Has been cancelled
Release / Publish to Docker Hub (push) Has been cancelled
Release / Create GitHub Release (push) Has been cancelled
feat(v3.12.0): media pipeline, AI image generation, capability probe, companion v2.9.0
Three-month batch sync from internal repo (~80 commits) covering Tracks F.5a, F.7e, F.8, F.17, F.18, F.X.

WordPress media pipeline
- Pillow-based optimization, AI image generation (OpenAI / Stability / Replicate / Google Nano Banana / OpenRouter), chunked + resumable uploads, bulk delete/reassign, idempotent retries.

Capability discovery (F.7e)
- Per-site credential probe + adapters for WordPress / WooCommerce / Gitea, tier-fit unions granted ∪ roles, capability badge UI with HTMX partial re-check, install hint in every companion-unreachable error.

Companion plugin overhaul
- Renamed wordpress-plugin/airano-mcp-seo-bridge → wordpress-plugin/airano-mcp-bridge.
- Eight new endpoints: /capabilities, /bulk-meta, /export, /cache-purge, /transient-flush, /site-health, /audit-hook, /upload-and-attach.
- wp.org Plugin Check pass: i18n, WP_Filesystem, scheme allowlist on audit-hook URL.

Other
- Gitea ergonomics (F.17): batch files, tree, search, compare, releases, fork.
- Opportunistic bcrypt upgrade for legacy SHA-256 admin keys (F.8).
- n8n refactor: structured errors, capability probe, missing tools backfilled.
- Idempotency-Key dedup for AI media upload retries; WP client fast-fails on unreachable sites.

Docs
- README + CLAUDE.md drop the fixed "633 tools" claim. The total grows with each release; per-plugin approximations + dashboard-surfaced counts replace it.
- Tools/Tests badges removed in favour of "Plugins: 10".

Deployment
- PyPI mirror chain, optional BUILD_HTTP_PROXY, Alpine→Yandex apk mirror, Debian-slim Plan-B Dockerfile, mirror.gcr.io variant.

CI
- Black + Ruff clean on Python 3.12; pytest tests/ green.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-25 16:25:58 +02:00

92 lines
3.2 KiB
Python

"""F.5a.6.2 — Stable error-code taxonomy for media upload tools.
Every :class:`plugins.wordpress.handlers._media_security.UploadError` and
:class:`core.upload_sessions.UploadSessionError` raised inside the media
stack MUST use one of the codes listed here (or match the dynamic
``WP_<status>`` pattern for upstream WordPress REST responses).
The accompanying test ``tests/plugins/wordpress/test_media_error_taxonomy.py``
scans the source files for raise-site literals and asserts each one is in
this set — so the contract stays stable as the code evolves.
The full reference is in ``docs/media-error-codes.md``.
"""
from __future__ import annotations
import re
#: All stable upload/media error codes. Keep alphabetical within groups.
MEDIA_ERROR_CODES: frozenset[str] = frozenset(
{
# --- Input / validation ------------------------------------------
"BAD_BASE64",
"BAD_MODE",
"BAD_ROLE",
"BAD_SIZE",
"BAD_SOURCE",
"EMPTY_FILE",
"MEDIA_NOT_FOUND",
"MIME_REJECTED",
"MISSING_FIELD",
"SSRF",
"TOO_LARGE",
"URL_FETCH_FAILED",
# --- WordPress REST upstream -------------------------------------
"WP_413",
"WP_AUTH",
"WP_BAD_RESPONSE",
# F.X.fix-pass4 — WC sites with consumer_key/consumer_secret
# auth need a separate WP Application Password to upload to
# /wp/v2/media. Surfaced by media_attach.py when the user
# hasn't filled wp_username/wp_app_password in Connection
# Settings.
"WP_CREDENTIALS_MISSING",
# WP_<status> (e.g. WP_500) is also allowed — see MEDIA_ERROR_CODE_RE
# --- Companion plugin upload-chunk route (F.5a.7) ----------------
"COMPANION_BAD_RESPONSE",
# COMPANION_<status> (e.g. COMPANION_500) is also allowed — same
# shape as WP_<status>, see _COMPANION_STATUS_RE.
# --- Chunked upload session --------------------------------------
"BAD_STATE",
"CHECKSUM_MISMATCH",
"CHUNK_CHECKSUM",
"CHUNK_ORDER",
"CHUNK_OVERFLOW",
"EXPIRED",
"INCOMPLETE",
"NO_SESSION",
"QUOTA_EXCEEDED",
"SESSION_TOO_LARGE",
# --- AI generation providers -------------------------------------
"GENERATION_FAILED",
"NO_PROVIDER_KEY",
"PROVIDER_AUTH",
"PROVIDER_BAD_REQUEST",
"PROVIDER_BAD_RESPONSE",
"PROVIDER_QUOTA",
"PROVIDER_TIMEOUT",
"PROVIDER_UNAVAILABLE",
"PROVIDER_UNKNOWN",
# --- Rate / policy -----------------------------------------------
"TOOL_RATE_LIMITED",
# --- Catchall ----------------------------------------------------
"INTERNAL",
}
)
#: Dynamic WP REST status codes (e.g. WP_400, WP_500).
_WP_STATUS_RE = re.compile(r"^WP_\d{3}$")
#: Dynamic companion upload-chunk status codes (e.g. COMPANION_400, COMPANION_500).
_COMPANION_STATUS_RE = re.compile(r"^COMPANION_\d{3}$")
def is_valid_code(code: str) -> bool:
"""Return True if ``code`` is a documented media error code."""
return (
code in MEDIA_ERROR_CODES
or bool(_WP_STATUS_RE.match(code))
or bool(_COMPANION_STATUS_RE.match(code))
)