unstructured/scripts/chroma-test-helpers/create-and-check-chroma.sh

#!/usr/bin/env bash

set -e

# $1 is the path for chroma to write the contents to. The symbol "&" runs process in background
python "$VIRTUAL_ENV/bin/chroma" run --path "$1" &
feat: add chroma destination connector (#2240) Adds Chroma (also known as ChromaDB) as a vector destination. Currently Chroma is an in-memory single-process oriented library with plans of a hosted and/or more production ready solution -https://docs.trychroma.com/deployment Though they now claim to support multiple Clients hitting the database at once, I found that it was inconsistent. Sometimes multiprocessing worked (maybe 1 out of 3 times) But the other times I would get different errors. So I kept it single process. --------- Co-authored-by: potter-potter <david.potter@gmail.com> 2023-12-19 08:58:23 -08:00			`#!/usr/bin/env bash`

			`set -e`

			`# $1 is the path for chroma to write the contents to. The symbol "&" runs process in background`
chore(file): remove dead code (#3645) Summary Remove dead code in `unstructured.file_utils`. Additional Context These modules were added in 12/2022 and 1/2023 and are not referenced by any code. Removing to reduce unnecessary complexity. These can of course be recovered from Git history if we decide we want them again in future. 2024-09-18 23:45:33 -07:00			`python "$VIRTUAL_ENV/bin/chroma" run --path "$1" &`