843 Commits

Author	SHA1	Message	Date
Molecule AI Core-BE	2241d404c7	[core-be-agent] fix hub_test.go: unbuffered channel hang + pointer identity ... Root cause of CI hang (CI / Platform (Go) failing after 2m11s): 1. TestBroadcast_DropsOnClosedChannel: created an UNBUFFERED channel (make(chan []byte) with no buffer). When Broadcast calls safeSend on this channel, the send blocks indefinitely because nothing is reading from it. go test hangs forever waiting for the test to complete. Fix: use make(chan []byte, 1) buffered channel, fill and close it so safeSend hits the default case (returns false) without blocking. 2. Pointer identity: Broadcast tests used anonymous struct literals in h.clients map assignments, but Go map keys store copies of structs. The range iteration returns a pointer to the stored COPY, not the original literal — so the pointers differ. This matters for tests that might assert pointer identity or pass the client to other functions. Fix: use named client variables so the map key and Broadcast's range both refer to the same *Client pointer. Applied to all Broadcast tests defensively. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-13 08:23:59 +00:00
Molecule AI Core-BE	d5bfb9967d	[core-be-agent] fix type mismatch: return sqlmock.Sqlmock (interface), not *sqlmock.Sqlmock ... sqlmock.New() returns (Sqlmock, error) where Sqlmock is the interface type, not a pointer. setupTestDB correctly returns sqlmock.Sqlmock (interface), but setupWorkspaceCrudTest and setupInstructionsTestDB incorrectly declared *sqlmock.Sqlmock (pointer to interface). In Go, *Interface is a distinct type from Interface — this would be a compile error. Root cause: copy-paste from setupWorkspaceCrudTest where the original author assumed *sqlmock.Sqlmock was the correct type. Fix: change both setup functions to return sqlmock.Sqlmock (interface) to match what sqlmock.New() actually returns. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-13 08:11:26 +00:00
Molecule AI Core-BE	67f0173138	[core-be-agent] fix vet warnings: unused variables in hub_test and bundle_helpers_test ... Per QA review of PR #794: 1. hub_test.go TestNewHub_WithAccessChecker: `called` was set but never read (unused variable → go vet failure). Added assertion that checks `called` is true after verifying the access checker was invoked. 2. bundle_helpers_test.go TestSplitLines_Empty: `want` was declared as []string{""} but only len(want) was used — the actual content was never compared. Fixed to assert len(got)==1 && got[0]=="", which validates the correct split behavior for an empty string. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-13 08:11:26 +00:00
Molecule AI Core-BE	6e16022165	[core-be-agent] fix tests: routing engine + setupInstructionsTest ... Two compounding test bugs were causing CI failures in the Platform (Go) job: 1. workspace_crud_test.go: 9 Update tests still registered routes on a separate r2 := gin.New() but called r.ServeHTTP() on the original engine from setupWorkspaceCrudTest. This sent requests to r (which had no PATCH route) → 404 instead of the expected validation error. Fixed: use r consistently for both route registration and serving. 2. instructions_test.go: setupInstructionsTest() called setupTestDB() (which sets global db.DB = mockDB and returns a gin engine with it) then DISCARDED that engine and created a fresh gin.New(). Every test then created ANOTHER fresh gin.New() for route registration. So the route registration and r.ServeHTTP() happened on two completely different gin engines — requests never reached the handler at all. Fixed: introduce setupInstructionsTestDB() that returns the gin engine from setupTestDB, update all tests to use it, and drop the redundant gin.New() calls. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-13 08:11:26 +00:00
Molecule AI Core-BE	a8c0396d3e	[core-be-agent] fix tests: routing r2→r for delete/resolve, CascadeDelete WithArgs ... - workspace_crud_test.go: TestDelete_* tests registered routes on r2 but called r.ServeHTTP, causing unmocked DB calls. TestUpdate_WorkspaceNotFound same. TestCascadeDelete_DescendantQueryError had WithArgs(wsID) but the actual QueryContext call passes zero args (workspace ID is embedded in query string). - instructions_test.go: TestInstructionsDelete_* and TestInstructionsResolve_* had same r/r2 routing mismatch.	2026-05-13 08:11:26 +00:00
Molecule AI Core-BE	b1cf2b0ad7	[core-be-agent] bundle: add bundle_helpers_test.go — 17 cases for pure helpers ... Tests: - splitLines: basic, trailing newline, empty, single char - extractDescription: plain text, after frontmatter, skips comments, only comments, empty, frontmatter-only - nilIfEmpty: empty→nil, non-empty→same - buildBundleConfigFiles: system prompt, config.yaml prompts, skill files, combined, empty bundle - findConfigDir: exact name match, fallback to first, no dirs→"", unreadable dir→"" No go binary in container — validated by CI.	2026-05-13 08:11:26 +00:00
Molecule AI Core-BE	b2865bb668	[core-be-agent] fix tests: CascadeDelete mock call, instructions r2→r cleanup ... - workspace_crud_test.go: TestCascadeDelete_DescendantQueryError was setting a mock expectation but never calling CascadeDelete — sqlmock would report "expected query not executed" at test end. Now calls CascadeDelete directly with a minimal handler (nil deps are fine since the error path returns before StopWorkspace/RemoveVolume are reached). - instructions_test.go: All Create/Update tests declared r2:=gin.New() then called r2.ServeHTTP while the setup's r engine sat unused. Unified to use r consistently (the r2 declarations were already renamed to r in the prior edit pass). Also removed dead code in TestInstructionsCreate_HappyPath (r.POST routed to h.List on an unused engine).	2026-05-13 08:11:26 +00:00
Molecule AI Core-BE	c3e7e341c7	[core-be-agent] ... ws: add hub_test.go — 13 cases for NewHub, safeSend, Broadcast, Close Covers: - NewHub: nil checker, access checker wiring - safeSend: open, closed, and full channel paths - Broadcast: canvas always-receives, workspace CanCommunicate gating, drops on closed/full, empty hub, multi-client, canvas-ignores-checker - Close: disconnects all, idempotent, closes done channel No go binary in container — validated by CI.	2026-05-13 08:11:26 +00:00
Molecule AI Core-BE	c2677cc0a2	test(handlers): add org_layout_test.go — 16 cases for childSlot/sizeOfSubtree/childSlotInGrid ... Pure layout helper functions that compute canvas node positions and subtree bounding boxes. Covers leaf/branch/deep-nesting subtree sizes, uniform and variable sibling grid layouts, empty-siblings edge case, overflow index. Closes test coverage gap on org.go canvas layout helpers. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-13 08:11:26 +00:00
Molecule AI Core-BE	7871bb2f52	test(handlers): add workspace_crud_test.go — 20 cases for State/Update/Delete ... Covers State (legacy, auth-required, not found, soft-deleted, query error), Update (invalid UUID/body/not found, field length limits, newline/YAML-char rejection, workspace_dir validation), Delete (invalid UUID, children confirmation gate, query error), validateWorkspaceID, validateWorkspaceFields, validateWorkspaceDir helpers. Closes test coverage gap on workspace_crud.go. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-13 08:11:26 +00:00
Molecule AI Core-BE	f3fd8aa700	test(handlers): add instructions_test.go — 17 cases for InstructionsHandler ... Covers List (workspace scope, global-only, query error), Create (happy path, missing required, invalid scope, workspace without target, content/title too long, insert error), Update (happy path, partial, content/title too long, not found, update error), Delete (happy path, not found, delete error), Resolve (no instructions, global only, global+workspace, query error, missing workspace ID), and scanInstructions helper (empty rows, scan error). Fixes gap: instructions.go had zero unit test coverage. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-13 08:11:26 +00:00
devops-engineer	871f8f52b5	Merge pull request 'fix(lint): resolve 64 pre-existing golangci-lint violations in workspace-server' (#803) from fix/golangci-lint-preexisting-violations into main	2026-05-13 07:55:29 +00:00
devops-engineer	f06a8e76fc	Merge pull request 'fix(platform): install docker-cli-buildx in workspace-server image (mc#765 follow-up)' (#796) from fix/workspace-server-docker-cli-buildx-mc765-followup into main	2026-05-13 07:42:04 +00:00
hongming-codex-laptop	c2e462ca26	fix(lint): resolve 64 pre-existing golangci-lint violations in workspace-server ... Fixes all ineffassign (7), staticcheck (31), and unused (26) violations reported by golangci-lint in workspace-server/ so the linter gate is clean. Key changes by linter: - ineffassign: remove 7 variables assigned then immediately overwritten - QF1001 (De Morgan): rewrite 4 negated compound conditions - QF1006 (loop lift): 2 for{if break} → for !cond{} - QF1008 (embedded field): drop .Resources. from hostCfg/hc selectors (provisioner + tests) - QF1012 (Fprintf): 3 sb.WriteString(fmt.Sprintf) → fmt.Fprintf - S1009 (nil+len): remove redundant nil check before len() - S1016 (type conv): 2 struct-literal copies → direct type conversion - S1017 (TrimPrefix): 2 if+HasPrefix/slice → strings.TrimPrefix - S1023 (redundant return): remove 2 trailing returns in middleware - SA1012 (nil context): nil → context.TODO() in resolver_test - SA1019 (deprecated): ImageInspectWithRaw → ImageInspect; RetryAfter direct field - SA5011 (nil deref): t.Error → t.Fatal before dereference in client_test - ST1005 (error string): lowercase 3 error strings starting with proper nouns - ST1013 (HTTP constant): 405 literal → http.StatusMethodNotAllowed - unused: delete 26 unused consts/types/funcs/fields across 12 files All three checks pass after this commit: go build ./... → success go vet ./... → success golangci-lint run --timeout 3m ./... → 0 issues Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-12 23:47:36 -07:00
hongming-codex-laptop	ad7acd30db	fix(platform): clear golangci-lint findings	2026-05-12 22:53:22 -07:00
hongming-pc2	1c17f0ff73	fix(platform): install docker-cli-buildx in workspace-server image (mc#765 follow-up) ... mc#765 added `docker-cli` to the workspace-server Alpine runtime, but the Alpine package is just the CLI binary — it does NOT include the buildx plugin. Modern Docker (26.x in this image) defaults BuildKit=on, so `docker build` immediately fails with: local-build: pre-flight OK (docker=/usr/bin/docker) Provisioner: workspace start failed for <id>: local-build mode: ensure image for runtime "claude-code": local-build: docker build molecule-local/workspace-template-claude-code:<sha>: exit status 1: ERROR: BuildKit is enabled but the buildx component is missing or broken. Caught immediately after the mc#765 platform-image deploy + recreate during the sdk-lead (360d42e4-8356-441c-80cf-16fcd5d5ce03) + CP-QA (ec6cf05b-2637-4b3c-b561-b33914849aa2) recovery POST /restart calls. Pre-flight passed (docker CLI present, confirmed by the line above), but the actual `docker build` aborted on buildx-missing. The fix mirrors mc#765's shape: add the matching Alpine package (`docker-cli-buildx`, in community/, verified 0.14.0-r3 on alpine:3.20) to the apk add line in workspace-server/Dockerfile. Diff is +1 word in the apk-add line and a comment block extension that explains the BuildKit/buildx requirement. Related: mc#765 (parent fix), Task #194 / Issue #63 (local-build path).	2026-05-12 22:14:46 -07:00
hongming	738e54593c	Merge pull request 'fix(platform): install docker-cli in workspace-server image — unblocks RegistryModeLocal' (#765) from infra/dockerfile-add-docker-cli-for-local-build into main	2026-05-13 04:39:13 +00:00
hongming	03e7a2d8a5	Merge pull request 'test(handlers): drain preflight restart goroutine' (#780) from fix/core-main-red-race-20260512 into main	2026-05-13 04:30:05 +00:00
hongming-codex-laptop	381c710f8a	test(handlers): drain preflight restart goroutine	2026-05-12 21:07:40 -07:00
Molecule AI Core-Security	40edbd3aae	Merge main into feat/a2a-proxy-helpers-test-coverage	2026-05-12 20:43:27 -07:00
Molecule AI Core-Security	e5069012fb	Merge commit '806bbb464ee0df5f2537815ad9509aa28b51dbae' into mm2-700	2026-05-12 20:19:30 -07:00
Molecule AI Core-Security	181a8f9ca7	Merge commit '806bbb464ee0df5f2537815ad9509aa28b51dbae' into mm2-699	2026-05-12 20:19:24 -07:00
Molecule AI Core-Security	2ec3f72857	Merge commit 'd332a854d545' into mm-700	2026-05-12 20:04:13 -07:00
Molecule AI Core-Security	6d98d84255	Merge commit 'd332a854d545' into mm-699	2026-05-12 20:04:05 -07:00
Molecule AI Core-Security	598e0471c4	Merge commit 'd332a854d545cb5a8157fb710688c6995c4811e6' into merge-main-698b	2026-05-12 20:03:18 -07:00
dev-lead	a65cea7b66	fix: handle json null and empty array in extractToolTrace ... JSON null unmarshals to []byte("null") (4 bytes), not nil, so len(trace)==0 missed it. Empty array []byte("[]")==2 bytes was also returned unchanged. Add explicit string checks for both cases. Also fix TestExtractToolTrace_ValidNonEmpty: json.Marshal compacts spacing, so byte-exact comparison against spaced literal fails on round-trip. Use compact literal instead. Fixes mc#669 (null tool_trace panic path).	2026-05-12 19:44:22 -07:00
Molecule AI Core-Security	a224740d4d	Merge remote-tracking branch 'dev-lead/main' into pr693-test	2026-05-12 19:12:23 -07:00
Molecule AI Core-Security	a8f8e07c02	Merge remote-tracking branch 'dev-lead/main' into pr698-test	2026-05-12 18:46:30 -07:00
Molecule AI Core-Security	85c2db6248	Merge remote-tracking branch 'dev-lead/main' into pr700-test	2026-05-12 18:46:27 -07:00
Molecule AI Core-Security	8dae36277f	Merge remote-tracking branch 'dev-lead/main' into pr699-test	2026-05-12 18:46:25 -07:00
Molecule AI Core-Security	8aa409211c	fix(test): correct org_import_helpers_test logic errors and remove duplicates ... Remove TestCollectOrgEnv_Empty and TestCollectOrgEnv_RequiredWinsOverRecommended which are already declared in org_test.go. Fix TestSanitizeEnvMembers_MaxLength to use printable chars instead of null bytes, fix TestSanitizeEnvMembers_DigitsAndUnderscore to drop leading-underscore names that fail ^[A-Z] regex, fix TestFlattenAndSortRequirements_GroupsSortedByMemberKey assertion order (A < B), and fix TestCollectOrgEnv_GroupWithOneInvalid_KeepsRest to use valid/invalid names that the sanitizer will actually filter. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-12 18:45:53 -07:00
Molecule AI Core-Security	31d14a4cf6	fix(test/handlers): use blank identifiers for unused vars in negative readUsageMap tests ... Go disallows declared-but-unused variables; in tests that check ok==false, in and out are irrelevant — replace with _. Co-Authored-By: claude-sonnet-4-6 <noreply@anthropic.com>	2026-05-12 18:41:19 -07:00
Molecule AI Core-Security	d2661bb0cb	fix(test/handlers): correct newSocketHandlerWithDB signature — drop *sql.DB param ... setupTestDB already sets db.DB globally; passing sqlmock.Sqlmock as *sql.DB caused a build failure. Remove the redundant parameter and update callers. Co-Authored-By: claude-sonnet-4-6 <noreply@anthropic.com>	2026-05-12 18:40:42 -07:00
Molecule AI Core-Security	23e408379d	fix(test/mcp): align RecallMemory_GlobalScope with OFFSEC-001 scrub contract ... The test was asserting that the client-visible error.message equals the descriptive internal reason ("GLOBAL scope is not permitted via the MCP bridge"). After PR#680 and PR#772 enforced the OFFSEC-001 scrub contract across all tool-dispatch failure paths, mcp.go returns the constant "tool call failed" to callers — not the internal detail. Update the test to: - Rename to ..._Blocked_ScrubsInternalError (consistent with CommitMemory) - Assert error.message == "tool call failed" (OFFSEC-001 positive) - Add negative assertions (no internal tokens leak to client) - Use proper json.Unmarshal error check - Merge origin/main (PR#691 lint-required-context-exists-in-bp) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-12 18:11:07 -07:00
core-devops	1b3d7b0968	Merge remote-tracking branch 'origin/main' into local-fix/687-send-ssh-public-key-detail	2026-05-13 00:31:41 +00:00
core-devops	781608a58c	Merge remote-tracking branch 'origin/main' into local-feat/a2a-proxy-helpers-test-coverage	2026-05-13 00:31:31 +00:00
core-devops	ae40907ff8	Merge remote-tracking branch 'origin/main' into local-feat/socket-handler-test-coverage	2026-05-13 00:31:18 +00:00
core-devops	2cd89ead0b	Merge remote-tracking branch 'origin/main' into local-feat/org-import-helpers-test-coverage	2026-05-13 00:31:03 +00:00
core-devops	f1777a8e71	Merge remote-tracking branch 'origin/main' into local-fix/681-recall-memory-offsec-scrub	2026-05-13 00:30:45 +00:00
core-devops	566bafe42c	merge: pull origin/main (PR#772 landed; resolve mcp_test.go conflict preserving OFFSEC-001 assertions)	2026-05-13 00:18:16 +00:00
molecule-operator	7a7ec880fe	fix(a2a_proxy): return error for 2xx responses with empty body ... An A2A agent must always return a JSON body. A 2xx with empty body means the connection closed before body bytes were written — this should route to the failure path, not silently succeed. Without this fix: 200 + empty body → (200, [], nil) → falls through to handleSuccess → marked "completed" despite no payload. With this fix: 200 + empty body → proxyA2AError{Status:200} → isDeliveryConfirmedSuccess=false → isTransientProxyError(200)=false → failure path → "failed" with error detail.	2026-05-13 00:07:56 +00:00
hongming-codex-laptop	5a2d555c62	fix(ci): repair scheduled main janitors and track masks	2026-05-12 17:03:29 -07:00
molecule-operator	e51ef1009a	Merge remote-tracking branch 'origin/main' into mc-680-update	2026-05-12 23:57:17 +00:00
core-devops	7f2fb13483	fix(handlers): preserve HTTP status through body-read errors; fix TestExecuteDelegation_* mocks ... Three coordinated fixes for the delivery-confirmed-success path added in PR #680: 1. a2a_proxy.go: When io.ReadAll returns a readErr (partial body), preserve resp.StatusCode in proxyA2AError.Status for non-2xx responses (status >= 300). Previously always returned BadGateway, causing isTransientProxyError to wrongly retry 500/server-rejected requests as if they were transient. 2. delegation.go: Move isDeliveryConfirmedSuccess check BEFORE the isTransientProxyError retry gate. Previously a 200+partial-body response triggered the 8s retry before the success check ran. Also change delegationRetryDelay from const to var for test overrides. 3. delegation_test.go: Rewrite TestExecuteDelegation_* helper functions and test bodies to match the actual ordered DB call sequence: - expectProxyA2ARequest: full 5-call sequence (parent lookups, budget, delivery_mode, runtime) - expectLogA2ASuccess: synchronous SELECT name inside logA2ASuccess - expectMaybeMarkContainerDead: SELECT COALESCE(runtime) for 502 path - setRetryDelayForTest: zero-delay retry in ProxyErrorEmptyBody test - Remove spurious second dispatched-UPDATE expectation (no such call)	2026-05-12 23:26:14 +00:00
hongming-pc2	b8ccd21c8c	fix(platform): install docker-cli in workspace-server image — unblocks RegistryModeLocal ... The platform server's internal/provisioner/localbuild.go (Task #194 / Issue #63 — the post-2026-05-06 GHCR-suspension fallback) shells out via exec.Command("docker", "image", "inspect"/"build"/"tag", ...) in the production dockerHasTagProd / dockerBuildProd / dockerTagProd functions. The colocated workspace-server/Dockerfile installed `ca-certificates git tzdata wget` in the alpine runtime layer but NOT `docker-cli`, so every workspace re-provision in the now-permanent RegistryModeLocal path fails at step 2 (cache check): local-build: image inspect for molecule-local/workspace-template-claude-code:<sha> failed (exec: "docker": executable file not found in $PATH); will rebuild Provisioner: workspace start failed for <id>: local-build mode: ensure image for runtime "claude-code": local-build: docker build molecule-local/workspace-template-claude-code:<sha>: exec: "docker": executable file not found in $PATH Net: ANY ws-* container that dies (auto-restart on container-dead, the liveness-monitor RestartByID, plugin auto-restart, secrets-set auto-restart, manual POST /workspaces/:id/restart) cannot come back up. Already took down CP-QA (ec6cf05b) and sdk-lead (360d42e4); also blocks the MiniMax LLM-provider switch for the 6 *-lead workspaces (which requires postgres UPDATE workspace_secrets + POST /restart to re-bake the env from the updated secrets). The Docker SOCKET is already mounted into the platform container — the entrypoint.sh adds the platform user to the docker group derived from the socket's gid. Only the CLI binary was missing. Per `registry_mode.go:Resolve()`, MOLECULE_IMAGE_REGISTRY is the toggle: set ⇒ RegistryModeSaaS pull from a real registry; unset ⇒ RegistryModeLocal clone+build from Gitea. Since 2026-05-06 the env var has been unset (GHCR was the only SaaS-mode target and it's unreachable post-suspension), so RegistryModeLocal is the permanent mode until internal#231 (GHCR→ECR migration) lands. This Dockerfile needs to support the mode the code is permanently in. Diff is +16/-1 (mostly comment explaining why). The single behavioural change: `docker-cli` added to the apk-add line. Verification: post-deploy, `POST /workspaces/360d42e4-…/restart` (the known-failed sdk-lead) should succeed and bring the workspace back up with its current Claude-Opus secrets — that's the first confirmation the local-build path is unblocked. Then the MiniMax switch can proceed (postgres UPDATE on each *-lead's workspace_secrets + POST /restart). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-12 14:13:55 -07:00
core-be	724723ab23	fix(handlers/terminal): fix unwrapGoError separator — use LastIndex("(") not ") "	2026-05-12 19:27:32 +00:00
Molecule AI Core-BE	ae603e2690	delegation_executor_integration_test.go: fix goroutine leak on timeout ... runWithTimeout previously called t.Fatalf when the timeout fired, but the executeDelegation goroutine was not cancelled — with context.Background() it kept running indefinitely (DB ops, broadcaster, etc.). The goroutine held runtime.LockOSThread(), causing it to leak until the test binary exited. Fix: runWithTimeout now creates ctx, cancel := context.WithTimeout(ctx, timeout), passes ctx to executeDelegation, and calls cancel() when the timeout fires. The goroutine's blocking calls (db.DB.ExecContext, conn.Write, etc.) respect the cancelled context and unblock, allowing the goroutine to exit cleanly. runtime.Goexit() terminates the goroutine so the main select loop completes. This also required changing the fn signature from func() to func(cancel func()) so the cancel function can be propagated. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-12 18:04:07 +00:00
Molecule AI Core-BE	381866e17d	delegation_ledger_integration_test.go: add missing time import ... Commit d60da43c added timeouts using time.Second but neglected to add the "time" import to the file. The test would not compile without it. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-12 18:04:07 +00:00
Molecule AI Core-BE	ce2db75fa1	handlers: pass cancellable context through executeDelegation ... executeDelegation previously created its own context.Background() with a 30-minute timeout internally, so updateDelegationStatus and all DB ops ignored external cancellation. The test helper runWithTimeout could fire its 30-second deadline but the goroutine kept running for the full 30 minutes because the cancellation never propagated. Fix: add ctx context.Context as first parameter to both executeDelegation and updateDelegationStatus. The caller now provides the context budget — Delegate() passes c.Request.Context() (5 min idle timeout), and tests pass context.Background(). This means runWithTimeout's deadline now actually terminates the goroutine when it fires. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-12 18:04:07 +00:00
Molecule AI Core-BE	1bd1180199	fix(handlers): add timeouts to all DB operations in integration tests ... Add 10s timeouts to integrationDB and setupIntegrationFixtures DB operations, and a 5s timeout to the cleanup DELETEs. The raw TCP mock server was confirmed working (tests pass in 5-8s when they pass), but some CI runs hang for 2+ minutes. Adding timeouts ensures that if DB operations block, the test fails cleanly with a timeout message rather than hanging the CI job. This also makes the tests more resilient to transient postgres slowness under CI runner load. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>	2026-05-12 18:04:07 +00:00