perso/mcp-maildir
4
0 Fork 0
Code Issues 1 Pull Requests 2 Actions 2 Packages Projects Releases Wiki Activity
138 Commits 6 Branches 24 Tags
ba53ae612785415f755a0f347a79699f6c25364e
Commit Graph
5 Commits
Author SHA1 Message Date
jcabillot 1115db82ed Merge pull request 'ci: harden the qdrant integration job (5s client timeout + cold storage)' (#60) from ci/harden-qdrant-integration into main
Main Release / test (push) Successful in 2m54s
Details
Docker Build and Push / integration-test (push) Successful in 3m12s
Details
Main Release / integration-test (push) Successful in 3m17s
Details
Main Release / hadolint (push) Successful in 17s
Details
Docker Build and Push / test (push) Successful in 3m0s
Details
Main Release / build (push) Successful in 21s
Details
Renovate / renovate (push) Successful in 59s
Details
Main Release / tag (push) Successful in 17s
Details
Tag Release / hadolint (push) Successful in 24s
Details
Docker Build and Push / build (push) Successful in 4m25s
Details
Tag Release / test (push) Successful in 2m42s
Details
Tag Release / integration-test (push) Successful in 2m35s
Details
Tag Release / build-push (push) Successful in 3m4s
Details 
Reviewed-on: #60
 2026-10-17 17:42:56 -04:00
Sagent 01d15c486e ci: harden the qdrant integration job
PR Checks / hadolint (pull_request) Successful in 23s
Details
Docker Build and Push / test (pull_request) Successful in 5m19s
Details
PR Checks / build-test (pull_request) Successful in 47s
Details
Docker Build and Push / integration-test (pull_request) Successful in 5m30s
Details
PR Checks / pytest (pull_request) Successful in 3m7s
Details
Docker Build and Push / build (pull_request) Successful in 3m14s
Details 
The integration test job has been failing intermittently on main and on
open pull requests with `httpx.ReadTimeout: timed out` on the first write
to Qdrant, while `GET /collections` and `/healthz` kept answering.

Cause: the qdrant-client default request timeout is 5 seconds, and the job
only waits for `/healthz`, which is served before the storage engine
accepts writes. On a shared runner doing several builds at once, the first
collection creation or indexing exceeds 5s and the whole fixture errors
out.

- pin qdrant/qdrant to v1.19 (the digest `latest` and the cluster already
  run) and let Renovate track the pin in the workflows as well
- wait for a real write round-trip (create + delete a probe collection)
  instead of `/healthz` alone, and dump the container logs if it never
  becomes writable
- make the Qdrant client timeout configurable via QDRANT_TIMEOUT and set
  it to 60s in CI, where there is no latency SLA
 2026-10-17 21:24:18 +00:00
Sagent bc3deb8676 fix: serve MCP over Streamable HTTP instead of legacy SSE
PR Checks / hadolint (pull_request) Successful in 40s
Details
PR Checks / build-test (pull_request) Successful in 3m19s
Details
PR Checks / pytest (pull_request) Successful in 2m47s
Details
Docker Build and Push / test (pull_request) Successful in 3m1s
Details
Docker Build and Push / integration-test (pull_request) Successful in 3m24s
Details
Docker Build and Push / build (pull_request) Successful in 3m4s
Details 
Current MCP clients (OpenCode, Claude, ...) only speak Streamable HTTP: they
POST JSON-RPC to the configured URL, so a legacy SSE endpoint answers
405 Method Not Allowed and not a single tool can be reached.

Run FastMCP's http_app (build_app()) under uvicorn instead of mcp.run(sse):
the MCP endpoint is now /mcp, and the custom GET /health route keeps serving
the Kubernetes probes.

Add transport tests asserting /mcp and /health are exposed and /sse is gone.
 2026-10-17 20:45:26 +00:00
Julien Cabillot 4e45f3e8d9 fix: perms
perso/mcp-maildir/pipeline/head This commit looks good
Details
2026-02-27 10:32:42 -05:00
Julien Cabillot b96277064a feat: init 2026-02-26 16:34:25 -05:00