Fix Fastly Compute Rust build failures caused by edition2024 dependencies. Use when: (1) cargo build fails with "feature `edition2024` is required", (2) wit-bindgen or wasip2 crates fail to download/parse, (3) Fastly SDK pulls in incompatible transitive dependencies, (4) Build worked before but fails after dependency update. Solves by pinning wit-bindgen, wasip2, and related crates to pre-edition2024 versions.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Fastly Compute Rust projects fail to build with errors about edition2024 being required,
even when using stable Rust. The error appears when transitive dependencies (especially
wit-bindgen 0.51+ and wasip2 1.0.2+) require Rust 1.87+ which isn't stable yet.
feature 'edition2024' is requiredfailed to parse manifest at .../wit-bindgen-0.51.0/Cargo.tomlcargo updatefastly crate) version 0.11.xPin the problematic transitive dependencies in your Cargo.toml:
[dependencies]
# Fastly Compute SDK - pin to specific version
fastly = "=0.11.12"
# Pin these to avoid edition2024 requirement
wit-bindgen = "=0.46.0"
wasip2 = "=1.0.1"
# Also pin these if you use k256 or crypto
k256 = { version = "=0.13.3", features = ["schnorr"] }
base64ct = "=1.6.0"
Also update rust-toolchain.toml to include both WASM targets:
[toolchain]
channel = "1.83.0"
targets = ["wasm32-wasi", "wasm32-wasip1"]
Then:
rm Cargo.lock
rustup target add wasm32-wasip1
cargo build --target wasm32-wasi
Build should complete without edition2024 errors:
cargo build --target wasm32-wasi 2>&1 | grep -i "edition2024"
# Should return nothing (no matches)
Before fix (Cargo.toml):
[dependencies]
fastly = "0.11" # Allows 0.11.x which pulls wit-bindgen 0.51+
After fix (Cargo.toml):
[dependencies]
fastly = "=0.11.12"
wit-bindgen = "=0.46.0"
wasip2 = "=1.0.1"
= prefix in version strings means "exactly this version"wasm32-wasi to wasm32-wasip1 targetwasm32-wasi being renamed to wasm32-wasip1 is expectedまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y". Use when: (1) ExternalSecret shows OutOfSync in ArgoCD but won't sync, (2) ArgoCD application status shows "namespace X is not permitted in project 'infrastructure'", (3) ExternalSecret targets a namespace managed by a different ArgoCD project, (4) Using apps-of-apps pattern with separate infrastructure and application projects.
日本語の概要は準備中です。原文の説明を表示しています。
Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language. After selection, generates AI image prompts and visual briefs section-by-section. Use when the user shares content and needs visual direction, image sourcing, or creative direction for any material.
日本語の概要は準備中です。原文の説明を表示しています。
Fix "Null check operator used on a null value" errors when an object is set to null during an async await. Use when: (1) Object reference is nullified while awaiting, (2) Code accesses object with ! after await returns, (3) Cancel/dispose operations run concurrently with async operations on same object. Solution: capture local reference before await.
日本語の概要は準備中です。原文の説明を表示しています。
Add custom metadata headers (x-amz-meta-*) to AWS v4 signed requests for GCS S3-compatible API. Use when: (1) Adding custom metadata to GCS uploads via S3 API, (2) Getting signature mismatch errors after adding new headers, (3) x-amz-meta-* headers being ignored or causing 403 errors. Custom headers MUST be included in canonical headers and signed headers list.
日本語の概要は準備中です。原文の説明を表示しています。
Fix password/secret authentication failures caused by trailing newlines when creating Google Cloud secrets (or similar) with bash here-strings. Use when: (1) Password authentication fails with correct password, (2) Secret created with `<<< "value"` syntax, (3) Error like "password authentication failed" or "invalid token" despite correct value. Bash here-strings (`<<<`) add a trailing newline that corrupts secrets.
日本語の概要は準備中です。原文の説明を表示しています。
Fix silent video/media processing failures caused by URL extraction code that filters on file extensions (.mp4, .webm, .webp). Use when: (1) Media moderation, transcoding, or analysis silently skips files from Blossom or content-addressed storage servers, (2) URL extraction from Nostr event tags (imeta, r tags) drops URLs without recognized extensions, (3) CDN fallback URLs append .mp4 but the actual server uses extensionless content-addressed paths like /{sha256}. Common in Nostr video events (kind 34236) where different clients use different URL formats.
日本語の概要は準備中です。原文の説明を表示しています。