Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
fix/1086-interrupt-hydrate-source
cdb2a658 fix(frameworks): keep hydrate queue open if a callback throws A throw from a queued onInterruptStateChange must still mark the client ready, or later live updates stay queued. Also set updatedAt on docs pages that describe the new hydrate source.
by Alem Tuzlak
Succeeded
fix/1086-interrupt-hydrate-source
cdb2a658 Merge b95b9936a012dfc562f5e490e14ae6950435c047 into 570e513218d48f483c75cdc7dea258e7b32c940e
by kolaworld
Succeeded
fix/1086-interrupt-hydrate-source
d9c7b8eb fix(ai-gemini): stop dropping modelOptions on the native image path (#1103) * fix(ai-gemini): stop dropping modelOptions on the native image path GeminiImageModelProviderOptionsByName mapped every image model to the Imagen-shaped GeminiImageProviderOptions, so safetySettings, thinkingConfig, imageConfig and systemInstruction were compile errors on the four Gemini-native models -- even though those models are served by generateContent, whose GenerateContentConfig accepts all four. The adapter compensated by forwarding only `seed` and silently dropping the rest, which its own comment documented as deliberate. Split the map native vs Imagen, mirroring the split that GeminiImageModelSizeByName and GeminiImageModelInputModalitiesByName already use. Both API paths now pick their config fields by name rather than spreading modelOptions wholesale, so neither endpoint can receive a field shaped for the other. responseModalities stays a protected adapter default and is deliberately absent from the new type. Runtime routing moves off a `gemini-` prefix test onto membership in GEMINI_NATIVE_IMAGE_MODELS, so the route and the type-level split cannot drift apart. An unknown id now reaches the Imagen endpoint and fails there instead of taking the native path with Imagen-shaped option types -- the same class of mismatch this change exists to remove. * docs(ai-gemini): describe image routing by model list, not prefix The prose and the changeset still said the adapter routes on a `gemini-` prefix. It routes on membership in GEMINI_NATIVE_IMAGE_MODELS, so an unlisted `gemini-*` id reaches generateImages and fails there. Raised by CodeRabbit on #1103. * test(e2e): cover Gemini native image modelOptions on the wire aimock's handleGemini has no image-response branch and its journal stores a lossy OpenAI-shaped translation that drops safetySettings and generationConfig, so neither fixtures nor /journal can see this path. Mount the endpoint directly instead -- the same escape hatch geminiTTSMount() already uses for the identical {model}:generateContent inlineData shape -- and reject the request if the fields are absent, so a dropped option fails the spec instead of passing silently. Verified revert-proof: with packages/ai-gemini/src reverted to the parent commit, the spec fails with "Missing top-level safetySettings". * fix(ai-gemini): export native image routing helpers and narrow imageConfig Export GEMINI_NATIVE_IMAGE_MODELS and isGeminiNativeImageModel so the docs name is a real import. Narrow native imageConfig to aspectRatio and imageSize so Vertex-only SDK fields cannot type-check and then throw on the Gemini Developer API. --------- Co-authored-by: Alem Tuzlak <t.zlak@hotmail.com>
by Katsuyuki ...
Succeeded
fix/1086-interrupt-hydrate-source
d9c7b8eb Merge f9398a4dca1009be75b8ecb14a7905a150aa6bfb into 4f027898a8e957353c29dcf423e59daa54868aee
by kolaworld