-
-
Notifications
You must be signed in to change notification settings - Fork 320
Open
Labels
possible bugunconfirmed bug reportunconfirmed bug report
Description
How are you running VectorAdmin?
Docker (local)
What happened?
I deployed vector-admin
by docker compose here.
I connected to chroma (installed by docker compose with API token authencation) and got error in container when Sysnc database:
2025-06-27 16:13:44.152 | setupFunctions success! 200
2025-06-27 16:13:44.152 | Background workers listening on port 3355
2025-06-27 16:13:44.152 | [Developer Notice] Run npx inngest-cli@latest dev -u http://127.0.0.1:3355/background-workers to debug events for workers or visit http://127.0.0.1:3355/background-workers
2025-06-27 16:13:50.920 | [09:13:50.919] INF apps synced, disabling auto-discovery
2025-06-27 16:14:02.746 | [TELEMETRY SENT] { event: 'job_queued', properties: { name: 'chroma/sync' } }
2025-06-27 16:14:02.758 | [09:14:02.757] INF publishing event caller=api event_name=chroma/sync internal_id=01JYRAMNM5J41242M7GK3AME9K external_id=01JYRAMNM5J41242M7GK3AME9K event="{Name:chroma/sync Data:map[connector:map[createdAt:2025-06-27T07:29:05.601Z id:1 lastUpdatedAt:2025-06-27T07:29:05.601Z organization_id:1 settings:{\"instanceURL\":\"http://host.docker.internal:8000\",\"authTokenHeader\":\"X-Chroma-Token\",\"authToken\":\"tét-token\"} type:chroma] jobId:8 organization:map[createdAt:2025-06-25T03:39:31.239Z id:1 lastUpdatedAt:2025-06-25T03:39:31.239Z name:iTech slug:itech uuid:org-WWFGPRQ-79Q42FG-GSH20CE-EVTMHBS]] User:map[] ID:01JYRAMNM5J41242M7GK3AME9K Timestamp:1751015642752 Version:}"
2025-06-27 16:14:02.763 | [09:14:02.762] INF received event event=chroma/sync event_id=01JYRAMNM5J41242M7GK3AME9K internal_id=01JYRAMNM5J41242M7GK3AME9K
2025-06-27 16:14:02.766 | [09:14:02.765] INF initializing fn event=chroma/sync event_id=01JYRAMNM5J41242M7GK3AME9K internal_id=01JYRAMNM5J41242M7GK3AME9K function="Sync Chroma Instance" function_id=b18e188e-46bb-583f-ba97-0400ab7d4017
2025-06-27 16:14:03.117 | prisma:info Starting a postgresql pool with 13 connections.
2025-06-27 16:14:03.288 | panic: runtime error: invalid memory address or nil pointer dereference
2025-06-27 16:14:03.288 | [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x17060c7]
2025-06-27 16:14:03.288 |
2025-06-27 16:14:03.288 | goroutine 1053 [running]:
2025-06-27 16:14:03.288 | github.com/inngest/inngest/pkg/execution/state.(*DriverResponse).GetFunctionOutput(0x3ca6a60?)
2025-06-27 16:14:03.288 | /home/runner/work/inngest/inngest/pkg/execution/state/driver_response.go:368 +0x207
2025-06-27 16:14:03.288 | github.com/inngest/inngest/pkg/tracing.WithDriverResponseAttrs(0xc00259b520, 0x0)
2025-06-27 16:14:03.288 | /home/runner/work/inngest/inngest/pkg/tracing/util.go:129 +0x23a
2025-06-27 16:14:03.288 | github.com/inngest/inngest/pkg/execution/executor.(*executor).Execute.func1({0x3c82090, 0xc000d26930})
2025-06-27 16:14:03.288 | /home/runner/work/inngest/inngest/pkg/execution/executor/executor.go:1061 +0xcf
2025-06-27 16:14:03.288 | github.com/inngest/inngest/pkg/util.CritT[...].func2()
2025-06-27 16:14:03.288 | /home/runner/work/inngest/inngest/pkg/util/critctx.go:86 +0x49
2025-06-27 16:14:03.288 | created by github.com/inngest/inngest/pkg/util.CritT[...] in goroutine 318
2025-06-27 16:14:03.288 | /home/runner/work/inngest/inngest/pkg/util/critctx.go:85 +0x4e5
2025-06-27 16:14:03.309 | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2025-06-27 16:14:03.309 | error Command failed with exit code 2.
Are there known steps to reproduce?
Deploy chroma lastest (v1.0.13) with API token authencation here.
Deploy vector-admin
with docker compose here.
Login vector-admin
and then connect to chromadb with below info:
- Host: http://host.docker.internal:8000
- API Header: <$CHROMA_AUTH_TOKEN_TRANSPORT_HEADER in .env>
- API Key: <$CHROMA_SERVER_AUTHN_CREDENTIALS in .env>
Finally, press button Sysnc database and log on vector-admin
container to see error as above!
Metadata
Metadata
Assignees
Labels
possible bugunconfirmed bug reportunconfirmed bug report