You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Skipped: no live Chroma endpoint/API token is available in this scheduled automation run; unit tests mock Chroma REST responses and verify fixed endpoint construction/auth headers.
[P1] packages/tools/chromaVectorStore/package.json:12 - pnpm test exits 1 when this plugin is validated as a submodule in the registry checkout. The repository has tests at index.test.ts, src/client.test.ts, and src/schemas.test.ts, but no plugin-local Vitest config, so Vitest walks up to the parent registry config and reports No test files found for tests/**/*.test.ts. Add a plugin-local Vitest config or update the test script so the checked-in tests run from packages/tools/chromaVectorStore.
Evidence
registry/submodule: pnpm run validate -- --base origin/main --head HEAD passed with changedPluginIds: ["chromaVectorStore"]; .gitmodules points at the source repo; submodule HEAD matched registry commit 720844267afd04a0f50c340697418029a9d9611b; source repo is public MIT.
install/build/check/pack: pnpm install --frozen-lockfile --ignore-workspace passed; pnpm test failed with No test files found, exiting with code 1; pnpm type-check, pnpm build, pnpm check, and pnpm run pack passed.
policy scan: no hardcoded private keys/tokens, child_process, shell command construction, or destructive filesystem removal found. Network access is through the Chroma endpoint secret, with http(s) URL validation, no embedded credentials, HTTPS except localhost, and a selector required for delete.
Blocked. Not merged in scheduled run 20260708T061907Z because the plugin-review verdict is fail. GitHub reports the PR as non-draft, mergeable, and current status checks are successful; this blocker is inside the plugin test configuration/script and is not eligible for metadata-only conflict remediation.
Fixed the plugin-local test blocker reported in the review.
Changes:
Added a plugin-local vitest.config.ts so pnpm test uses the checked-in **/*.test.ts files instead of inheriting the registry root tests/**/*.test.ts include pattern.
Updated the registry submodule gitlink and plugins.json.commit to source commit 5a03f94bf207287882ab8cee7e903d56f04aafca.
Verification run:
In packages/tools/chromaVectorStore: pnpm install --ignore-workspace, pnpm run type-check, pnpm test, pnpm build, pnpm check, pnpm run pack all passed.
In the registry PR branch: pnpm validate, pnpm test, pnpm type-check, and git submodule status --recursive all passed.
registry/submodule: reviewed PR head 369f50fc0a1357f34463126fd2d988eb4ccb76a2; pnpm run validate -- --base origin/main --head HEAD passed with changedPluginIds: ["chromaVectorStore"]; submodule HEAD matched registry commit 5a03f94bf207287882ab8cee7e903d56f04aafca; root pnpm test passed 8 test files / 34 tests and pnpm run type-check passed.
install/build/check/pack: plugin-local pnpm install --frozen-lockfile --ignore-workspace, pnpm test (3 test files / 7 tests), pnpm run type-check, pnpm run build, pnpm run check, and pnpm run pack all passed.
policy scan: no hardcoded private keys/tokens, child_process, shell command construction, or destructive filesystem removal found; MIT license present; no catalog: or workspace: dependency specifiers. Network access is through a normalized Chroma endpoint secret with embedded credentials rejected and HTTPS required except localhost; delete requires a selector.
metadata remediation: resolved mechanical conflicts caused by prior plugin PRs and publish metadata landing first; conflict resolution touched .gitmodules, plugins.json, generated event metadata from main, and submodule metadata only relative to current origin/main; plugin implementation code was unchanged. Contributor action was not needed for that conflict.
Merged in scheduled run 20260708T084158Z. Squash merge used reviewed head 369f50fc0a1357f34463126fd2d988eb4ccb76a2 and produced merge commit 87385a19f66d862231543591f38a1549830bb2f5 at 2026-07-08T09:10:17Z; post-merge publish metadata was observed on origin/main at 9afa843.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
chromaVectorStorecommunity plugin as a submodulequeryCollection,addRecords,getRecords, anddeleteRecords5a03f94bf207287882ab8cee7e903d56f04aafcaVerification
Plugin source (
/home/openclaw/projects/fastgpt-plugin-chromaVectorStore):pnpm install --ignore-workspacepnpm run type-checkpnpm test(7 tests passed)pnpm buildpnpm checkpnpm run packRegistry (
/home/openclaw/projects/fastgpt-community-plugins):pnpm validatepnpm test(34 tests passed)pnpm type-checkgit submodule status --recursiveRemote dev debug
Skipped: no live Chroma endpoint/API token is available in this scheduled automation run; unit tests mock Chroma REST responses and verify fixed endpoint construction/auth headers.