Commit Graph
9 Commits
Author SHA1 Message Date
cloudix_mcp_server 90d40ff482 Add cron.yaml workflow — nightly hadolint→test→build-push 2026-06-13 21:17:21 -04:00
cloudix_mcp_server 733e269d81 Add main.yaml workflow — hadolint→test→build→tag for push to main 2026-06-13 21:17:17 -04:00
cloudix_mcp_server 30ac4ae9ca fix: correct integration test assertions for semantic search
Docker Build and Push / test (pull_request) Successful in 14s
Docker Build and Push / integration-test (pull_request) Successful in 1m44s
Docker Build and Push / build (pull_request) Successful in 1m12s
- test_search_by_content: format_search_result() does not include
  body_text, so check for the expected message_id instead.
- test_search_no_results: vector cosine similarity always returns
  nearest neighbors; use a date filter far in the future to
  guarantee zero results instead.
2026-06-12 08:25:52 -04:00
cloudix_mcp_server d784cd9fba fix: share job container network with Qdrant
Docker Build and Push / test (pull_request) Successful in 13s
Docker Build and Push / integration-test (pull_request) Failing after 1m49s
Docker Build and Push / build (pull_request) Has been skipped
docker run -d publishes ports to the Docker bridge network, but the
job container runs on a different Gitea Actions network. This causes
Connection refused when tests try http://localhost:6333.

Use --network container:$(hostname) so Qdrant shares the job container's
network stack, making localhost reachable.
2026-06-12 08:14:35 -04:00
cloudix_mcp_server 14650619ad fix: replace Gitea services container with manual docker run for Qdrant
Docker Build and Push / test (pull_request) Successful in 1m33s
Docker Build and Push / integration-test (pull_request) Failing after 2m23s
Docker Build and Push / build (pull_request) Has been skipped
The Gitea Actions runner v1.0.8 fails to start the Qdrant service container
with 'exec: ./entrypoint.sh: no such file or directory'. This is a runner bug
with how it handles service container entrypoints/CMD.

Bypass the service container mechanism by starting Qdrant manually with
docker run -d and a health check wait loop.
2026-06-12 08:10:51 -04:00
cloudix_mcp_server 655af15121 fix: replace Gitea services container with manual docker run for Qdrant
The Gitea Actions runner v1.0.8 fails to start the Qdrant service container
with 'exec: ./entrypoint.sh: no such file or directory'. This is a runner bug
with how it handles service container entrypoints/CMD.

Bypass the service container mechanism by starting Qdrant manually with
docker run -d and a health check wait loop.
2026-06-12 08:08:18 -04:00
cloudix_mcp_server 5ba7b567f8 Merge pull request 'chore: pin pip versions in requirements.txt' (#7) from fix/pin-dependencies into main
Docker Build and Push / build (push) Successful in 2m3s
2026-06-10 23:02:44 -04:00
cloudix_mcp_server 2b5eff12c1 Merge pull request 'chore: improve renovate dependency detection' (#4) from chore/renovate into main
Docker Build and Push / build (push) Successful in 2m11s
2026-06-10 22:24:07 -04:00
cloudix_mcp_server 0a31714fa2 chore: add renovate config for docker-compose qdrant image + pin unpinned pip deps
Docker Build and Push / build (pull_request) Successful in 1m54s
2026-06-08 21:41:06 -04:00