Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
6d149ae2 Merge a8e46bb00485b2565e42ac33c66a42ac980d7e81 into 552303b0f16af3605d34467c92c89ad4bf63e498
by Tom Beckenham
Failed
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
6d149ae2 ci: apply automated fixes
by autofix-ci...
Failed
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
33623ef8 Merge 52376a2a96a9783bdd6b45629c4f4a0d7e6137f9 into 4e9c5d2887dc9a3d64fce6ed424aa68f451e20f6
by Tom Beckenham
Failed
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
33623ef8 fix(e2e): only treat file-source RUN_ERROR as a wire-route failure Aimock can emit RUN_ERROR after a successful file_id mapping. The route's job is to catch mapping/lookup misses, not mock-provider failures.
by Alem Tuzlak
Failed
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
667aea83 fix(e2e): only treat file-source RUN_ERROR as a wire-route failure Aimock can emit RUN_ERROR after a successful file_id mapping. The route's job is to catch mapping/lookup misses, not mock-provider failures.
by Alem Tuzlak
Failed
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
667aea83 fix(e2e): only treat file-source RUN_ERROR as a wire-route failure Aimock can emit RUN_ERROR after a successful file_id mapping. The route's job is to catch mapping/lookup misses, not mock-provider failures.
by Alem Tuzlak
Succeeded
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
3b0ed087 Merge aa8d15dc740fe63520eead938147f68b61bb0ab7 into f7c67a85bb7dabaed4c80fc01ffc8a03fe9375a0
by Tom Beckenham
Succeeded
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
3b0ed087 fix(e2e): only treat file-source RUN_ERROR as a wire-route failure Aimock can emit RUN_ERROR after a successful file_id mapping. The route's job is to catch mapping/lookup misses, not mock-provider failures.
by Alem Tuzlak
Succeeded
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
33b2c3ae fix(e2e): only treat file-source RUN_ERROR as a wire-route failure Aimock can emit RUN_ERROR after a successful file_id mapping. The route's job is to catch mapping/lookup misses, not mock-provider failures.
by Alem Tuzlak
Succeeded
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
33b2c3ae fix(e2e): only treat file-source RUN_ERROR as a wire-route failure Aimock can emit RUN_ERROR after a successful file_id mapping. The route's job is to catch mapping/lookup misses, not mock-provider failures.
by Alem Tuzlak
Succeeded
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
33e02dcf Merge 50237a52cf2988e315f516864ba1f60d3e8867ba into 8bd6f7054248ddf9bda2929bb105a8aa5054b9d2
by Tom Beckenham
Succeeded
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
33e02dcf fix: address review feedback and CI test failures Keep explicit files-adapter API keys last, treat every RUN_ERROR as a wire-route failure, and update tests for PDF document input plus assistant message ids.
by Alem Tuzlak
Succeeded
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
4a0def74 fix(ai): close remaining file-source preflight holes Guard leftover source.value sites, run the fail-closed check on structured-output chat and embed, and preflight generateImage before RUN_STARTED.
by Alem Tuzlak
Failed
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
4a0def74 Merge 1958b14cc68e7d9a34e9aed224d6190e0b9f0be1 into d8b33505da1704807244d246715a8d3421c93a5c
by Tom Beckenham
Failed
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
eb39b736 refactor(files): record-based file references + fail-closed capability preflight Redesigns the `{ type: 'file' }` content source before it ships: - The source now carries a per-provider reference record — `{ type: 'file', reference: { openai: 'file-…', gemini: 'https://…' } }` — instead of a single { value, provider } pair. Each adapter reads only its own entry (`fileReferenceFor`), and a lookup miss throws naming the providers that are present. `fileSourceFromHandle(...handles)` merges handles from several providers into one source that routes to any of them (upload once per provider, replay the same conversation anywhere). - New fail-closed preflight: adapters that can consume file references declare `supportsFileSources`; chat()/generateImage()/generateVideo() reject file sources for every other adapter before a request is built. Adapters written before this feature existed can no longer silently mis-map a reference onto their URL/data branch — the failure class the per-adapter sweep was policing by convention is now structural. (openai-base's supportsFileIdInput gate is folded into the same flag.) - Removing `value` from the file arm also makes fall-through code a compile error — caught two latent OpenRouter paths that would have sent a reference as a URL, now restructured with narrowed sources. - Docs, agent skills, changeset, and all files-source tests updated to the record shape; new preflight unit tests; e2e spec asserts the record round-trip and lookup-miss rejection end-to-end.
by Tom Beckenham
Failed
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
eb39b736 refactor(files): record-based file references + fail-closed capability preflight Redesigns the `{ type: 'file' }` content source before it ships: - The source now carries a per-provider reference record — `{ type: 'file', reference: { openai: 'file-…', gemini: 'https://…' } }` — instead of a single { value, provider } pair. Each adapter reads only its own entry (`fileReferenceFor`), and a lookup miss throws naming the providers that are present. `fileSourceFromHandle(...handles)` merges handles from several providers into one source that routes to any of them (upload once per provider, replay the same conversation anywhere). - New fail-closed preflight: adapters that can consume file references declare `supportsFileSources`; chat()/generateImage()/generateVideo() reject file sources for every other adapter before a request is built. Adapters written before this feature existed can no longer silently mis-map a reference onto their URL/data branch — the failure class the per-adapter sweep was policing by convention is now structural. (openai-base's supportsFileIdInput gate is folded into the same flag.) - Removing `value` from the file arm also makes fall-through code a compile error — caught two latent OpenRouter paths that would have sent a reference as a URL, now restructured with narrowed sources. - Docs, agent skills, changeset, and all files-source tests updated to the record shape; new preflight unit tests; e2e spec asserts the record round-trip and lookup-miss rejection end-to-end.
by Tom Beckenham
Succeeded
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
91646acb refactor(files): record-based file references + fail-closed capability preflight Redesigns the `{ type: 'file' }` content source before it ships: - The source now carries a per-provider reference record — `{ type: 'file', reference: { openai: 'file-…', gemini: 'https://…' } }` — instead of a single { value, provider } pair. Each adapter reads only its own entry (`fileReferenceFor`), and a lookup miss throws naming the providers that are present. `fileSourceFromHandle(...handles)` merges handles from several providers into one source that routes to any of them (upload once per provider, replay the same conversation anywhere). - New fail-closed preflight: adapters that can consume file references declare `supportsFileSources`; chat()/generateImage()/generateVideo() reject file sources for every other adapter before a request is built. Adapters written before this feature existed can no longer silently mis-map a reference onto their URL/data branch — the failure class the per-adapter sweep was policing by convention is now structural. (openai-base's supportsFileIdInput gate is folded into the same flag.) - Removing `value` from the file arm also makes fall-through code a compile error — caught two latent OpenRouter paths that would have sent a reference as a URL, now restructured with narrowed sources. - Docs, agent skills, changeset, and all files-source tests updated to the record shape; new preflight unit tests; e2e spec asserts the record round-trip and lookup-miss rejection end-to-end.
by Tom Beckenham
Succeeded
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
91646acb Merge aaeb09056ea215b0b07ba7fcc713408b09fec0a0 into 059f8bbc61bf70f40000c63db6ff64b692b823b0
by Tom Beckenham
Succeeded
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
062698b1 review: complete the file-source sweep, gate openai-base subclasses, thread provider-literal handle types Post-review completion pass for the Files API PR (rebased onto main): - ai-byteplus (landed on main after this branch): file-source guards in text/image/video adapters + tests — a handle would previously have been sent to Ark as a URL. - Gemini Interactions video path: add the missing assertOwnFileSource guard (the sibling text-interactions adapter already had it) + tests. - openai-base Responses: new `supportsFileIdInput` gate (true only for OpenAI itself) so Grok/Bedrock/compatible subclasses reject file sources instead of inheriting the file_id mapping; chat-completions error copy no longer points non-OpenAI providers at openaiText. Tests for both. - Provider-literal handle types: FileHandle<TProvider>/FilesAdapter<TName> thread each adapter's name literal through uploadFile; getFile/deleteFile accept the handle itself, making cross-provider lifecycle calls compile errors. fileSourceFromHandle + FileHandle now also exported from the browser-safe @tanstack/ai/client entry. - Docs: fix broken openaiText import in multimodal-content.md, document the uploadFile/getFile/deleteFile dispatchers, correct the fal get/delete and explicit-key claims; kiira green. Skills: adapter-configuration §7 + chat-experience/media-generation notes. - Tests: gemini files-source mapping/rejection, OpenAI Responses document- arm behavior, toFileHandle normalizers (openai/gemini/fal), handle-object lifecycle dispatch, and an aimock e2e (file-source-wire) covering the round-trip + cross-provider rejection end-to-end. - Polish: unsupportedFileSourceError detail no longer contradicted by the generic tail, ollama uses this.name, fal expiresIn !== undefined, comment rot fixes; changeset updated (adds ai-byteplus patch).
by Tom Beckenham
Succeeded
909-featai-native-files-api-support-across-providers-upload-adapters-+-file-content-source
062698b1 Merge 7f0f9d54f46a44ca3f49f6e9e3b88ce6154c71fe into 059f8bbc61bf70f40000c63db6ff64b692b823b0
by Tom Beckenham