Classic298 acd03b147c fix: treat .ino files as source text so knowledge uploads stop failing (#29673) ... Uploading an Arduino sketch (`.ino`) to a knowledge base failed with `Expecting value: line 1 column 1 (char 0)` whenever the content extraction engine was Tika or Docling. Browsers send `.ino` as `application/octet-stream`, and the extension was missing from the known source extension list, so the file was handed to the extraction server instead of being read as plain text. The server answered with a non-JSON body and the loader crashed while decoding it. `.cpp` and `.h` sketches in the same folder uploaded fine, because those extensions are already on the list. Adding `ino` to that list routes it to the plain text loader, the same way the yaml/toml gap was closed in 710320601a. A sketch is plain C++ text, so there is nothing for a document extraction server to do with it. Verified by dispatch matrix over 35 extensions, 5 content types and all 8 engines against a stub server that reproduces the non-JSON response: the only rows that change are `.ino` under Tika and Docling, which now resolve to the text loader and extract the sketch verbatim. Every other row is unchanged. Fixes #29670		2026-09-04 19:13:04 -04:00
..
loaders	fix: treat .ino files as source text so knowledge uploads stop failing (#29673)	2026-09-04 19:13:04 -04:00
models	fix: repair two broken logging calls, one of which makes VECTOR_DB=opengauss unusable (#27838)	2026-08-10 22:19:41 -06:00
vector	fix: apply the shared metadata size cap to the last four vector DB backends (#29502)	2026-09-04 11:42:20 -04:00
web	refac	2026-08-31 00:40:15 -04:00
external.py	refac	2026-07-27 01:59:17 -04:00
utils.py	refac	2026-08-24 20:34:59 -04:00