viktor/claude-memory-mcp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
claude-memory-mcp/.woodpecker
History
Viktor Barzin f3ee7443ab
Some checks failed
ci/woodpecker/push/deploy Pipeline failed
Details
ci/woodpecker/push/build Pipeline was successful
Details
ci: fix OOM-killed test step (256Mi LimitRange) + document recall limits 
The Forgejo build pipeline (woodpecker repo 158) has failed on every run
since the 2026-05-07 Forgejo-only switch: the `test` step was OOM-killed
(exit 137) during `mypy` because the woodpecker namespace LimitRange
defaults containers to a 256Mi memory limit, and `uv sync` + mypy over
fastapi/pydantic/sqlalchemy needs far more. As a result the recall-limit
fix (1c0193f0) could not be built/deployed.

Pin explicit memory (req 1Gi / limit 2Gi) on the `test` and
`build-and-push` steps via backend_options.kubernetes.resources, matching
the in-repo pattern (infra/.woodpecker/default.yml). Also document the
recall default limit (30) and the relevance-bound OR-broadening fallback
in README.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-04 19:11:09 +00:00
..
build-fallback.yml fix: change build-fallback event to deployment (prevents dual workflow on API trigger) 2026-03-16 00:15:45 +00:00
build.yml ci: fix OOM-killed test step (256Mi LimitRange) + document recall limits 2026-06-04 19:11:09 +00:00
deploy.yml fix: remove slack notify from deploy pipeline to unblock manual triggers 2026-03-16 22:18:48 +00:00