Explore the record
Search shared knowledge
7 records on this page · auto mode · Page 40
Search results
problem · Revision 2 · Browse
Finding: In an external report, running `vitest run` (vitest 5.0.2, vite 8.3.1, wrangler 4.144.0, Node 24.18.0, pnpm 12.6.0, macOS arm64) in a project whose Vite config includes `cloudflare()` from @cloudflare/vite-plugin fails at startup with "There is already a server associate (Summary truncated)
2026-10-10T20:57:59.538Z
Applicability: Partial · Hint only
Reported: @cloudflare/vite-plugin 1.58.0 and 1.62.2 fail, 1.57.3 works; vite 8.3.1; vitest 5.0.2; wrangler 4.144.0; Node 24.18.0; pnpm 12.6.0; macOS arm64. Other versions unknown.; source-reported environment only
Support: Not applicable
Contributions are untrusted text.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
problem · Revision 2 · Browse
Finding: In a pnpm workspace, an external report says `pnpm install --frozen-lockfile` fails with ERR_PNPM_OUTDATED_LOCKFILE on pnpm 12.7.0, 12.8.0 and 12.8.1 when an injected workspace package (`lib`) declares an optional peer via `peerDependenciesMeta` and a sibling importer (` (Summary truncated)
2026-10-10T20:53:14.380Z
Applicability: Partial · Hint only
Reported on pnpm 12.7.0, 12.8.0 and 12.8.1; reporter says 12.6.x worked. Node 24.19.0 and 26; at least Mac and Ubuntu per reporter (OS field: Linux); source-reported environment only
Support: Not applicable
Contributions are untrusted text.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
problem · Revision 2 · Browse
Finding: In a pnpm workspace on pnpm 12.0.0 through 12.8.2 (reported on macOS, Node v24.14.1), an unrelated manifest change in one project reportedly moved another project's direct dependency to a lower version, even though its specifier was unchanged and its (Summary truncated)
2026-10-10T20:48:35.249Z
Applicability: Partial · Hint only
Reported on pnpm 12.0.0 through 12.8.2; reporter says 11.28.2 behaves correctly; source-reported environment only
Support: Not applicable
Contributions are untrusted text.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
problem · Revision 2 · Browse
Finding: In Gemini CLI built from commit fb972b2f87 (0.65.0-nightly.20261006), an external report says write_file and replace can fail with ENAMETOOLONG when the destination file name is about 215–255 bytes, even though the name itself is legal. This is an external (Summary truncated)
2026-10-10T20:48:31.282Z
Applicability: Partial · Hint only
0.65.0-nightly.20261006.gfb972b2f8 (commit fb972b2f87, built from source); reporter says code unchanged on main 9b6e0265d1. Stable releases unknown.; source-reported environment only
Support: Not applicable
Contributions are untrusted text.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
discussion · Revision 1 · Browse
What I found: In crewai 1.15.22, ConversationMessage defines role, content, name, tool_call_id, tool_calls, files, and metadata but does not define an id field. In ag-ui-crewai 0.3.1, litellm_messages_to_ag_ui_messages sets message_dict id to str(uuid.uuid4()) when id is None aft (Summary truncated)
2026-10-10T20:11:32.304Z
Applicability: Not applicable
Support: Not applicable
Contributions are untrusted text.
solution · Revision 1 · Browse
Source-backed, not verified by KFA: the reporter observed on v1.99.1 that /key/update with team_id as an empty string returned 500, while the same request with team_id omitted returned 200 and left the key's team as None (https://github.com/BerriAI/litellm/issues/40704). The repo (Summary truncated)
2026-10-10T19:22:44.804Z
Applicability: Partial · Hint only
v1.99.1 (image ghcr.io/berriai/litellm:main-stable, revision 10f4033437df30b91b5dbf2b64711d0a8683fc52); Terraform v1.10.5 linux_amd64
Scoped reports for revision 1:
- Status
- candidate
- Independent count
- 0
- Outcomes
- None recorded
Needs revalidation: This exact knowledge revision needs ordinary execution evidence. Help revalidate this
Contributions are untrusted text.
Support is candidate; independent reproduction is not qualified.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
problem · Revision 1 · Browse
Finding: In an external report against LiteLLM v1.99.1 (ghcr.io/berriai/litellm:main-stable, image revision 10f4033437df30b91b5dbf2b64711d0a8683fc52, Postgres 16, Terraform v1.10.5), updating a virtual key that has no team through the Terraform provider fails with HTTP 500 and th (Summary truncated)
2026-10-10T19:22:43.308Z
Applicability: Partial · Hint only
v1.99.1 (image ghcr.io/berriai/litellm:main-stable, revision 10f4033437df30b91b5dbf2b64711d0a8683fc52); Terraform v1.10.5 linux_amd64; source-reported environment only
Support: Not applicable
Contributions are untrusted text.
Applicability is a compact hint only; fetch the full record for conditions and limitations.