Vectle found the following relevant skills: - Canceling async Redis command leaves connection open, in unsafe state for future commands - Pangea cluster pods (authn, embargo, gateway) never reach running state
This skill responds to RabbitMQ memory alarms that block publishers while consumers keep draining. It covers finding the queues holding memory, draining or purging the backlog, and raising the watermark with alerting. Reach for it when publishes stall and the logs show a memory alarm.
Vectle found the following relevant skills: - Redis "OOM command not allowed when used memory > maxmemory": how to respond - Kubernetes node "MemoryPressure"/"DiskPressure": response checklist
A skill for container image scans killed by out-of-memory: confirm the OOMKilled event, raise the runner's memory limit, cache the vulnerability database between runs, and narrow the scan scope if still tight. Use when trivy or grype dies with exit 137. Triggers: 'image scan OOMKilled', 'trivy out of memory', 'scan ex…
Vectle found the following relevant skills: - k6 error: request timed out during load test - how to tell server slowness from client limits - [agent's flame graph was clean because the slowdown only happens during the nightly backup's I/O storm]…
Vectle found the following relevant skills: - NanoNets create-model.py KeyError: 'model_id' (API key env var on Windows) - openai:error_code=None error_message='Too many inputs for model None. The max number of inputs is 1.
Vectle found the following relevant skills: - solr 'OutOfMemoryError' during a full reindex: how to batch the commits - Zod v4 causes 'JavaScript execution ran out of memory (64 MB)' during push , 5-13x higher per-schema memory allocation
Teaches an agent to bound its crawl frontier so a long-running crawl stops growing memory until it crashes. Covers queue size caps, disk-backed overflow, visited-set compression, and crawl budgets. Use when a crawler's memory climbs for hours until it dies. Not for crawl speed, page parsing, or politeness.
Fixes a C kernel that dies allocating beyond available RAM: the process has no memory guard, so cap allocations or stream the data. Check ulimit and container limits. Not for python-kernel OOMs.
Vectle found the following relevant skills: - neo4j 'OutOfMemoryError: Java heap space' on a traversal: how to bound the query - extraction agent failed on generated graphql types file with out of memory error
Vectle found the following relevant skills: - agent's flame graph was clean because the slowdown only happens during the nightly backup's I/O storm - [agent recommended adding an index that made writes 3x slower -- it only measured read latency]…
Vectle found the following relevant skills: - Concur: receipt image too large" upload error - Fixing the Apple OpenGL driver crash on glBufferSubData uploads larger than 2GB in VTK
Handles Celery workers killed by the OS for memory: sizing tasks, finding the memory hog, and setting limits so one task cannot take down the worker. Use when worker pods or processes die with OOMKilled around task execution. Not for scheduler memory problems.
Vectle found the following relevant skills: - workerd error: fetch event handler crashed after returning response - Airflow backfill tasks stuck in No status: scheduler starves backfill runs
Responds to Redis rejecting writes because memory exceeded maxmemory. Use when write commands fail with the OOM error and the instance is otherwise healthy. Not for Redis being down, replication or persistence failures, or read errors.
Vectle found the following relevant skills: - selenium grid node not registered: how to fix - Selenium 4 Java: random netty read TimeoutException on fast commands (fixed in 4.1.2)